Performance issue in our Invoice search API about killbill HOT 1 CLOSED

Given our API, we don't really know which column to search for so we have to do all 3:

• If the input looks like a currency (3 char string, or we could even check against our Currency enum), we could optimize and simply do this query. This is similar to what we do for the invoiceNumber. However, we might need an index for currency, which we don't have today.
• If the input looks like a UUID, we could implement a UNION between both accountId and invoiceId columns and remove the OR - we already have the index for both accountId and invoiceId.

Note that for Invoice, the search is an exact search, i.e we have not implemented like clause, the way we do for Account search.

from killbill.