Splitting rows/documents by ALT allele will reduce this, but we will have cases where an INFO field has multiple values per row. We should have a test case (which we could engineer into the mGAP demo VCF), and i think the desired behavior is for the client to be able to do normal numeric search, and return that row if any of the values matches.

Example:

FIELD1=1,2,30

search: "FIELD1 > 20"
result: row is returned
same for "FIELD1 < 2" or "FIELD1 == 2"