Is it intended that `,` in advanced queries behaves differently from `&`?

[corneliusroemer]

Not thinking much, I used an advanced query G2782T , T111C.

Looking at the nucleotide mutations within things matched by that query, I noticed that T111C is only present in 20%.

So it seems that the notation G2782T , T111C means maybe(G2782T) AND maybe(T111C) whereas G2782T & T111C means G2782T AND T111C. Is that right? And is it intended?

https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?variantQuery=G2782T+%26+T111C&

https://cov-spectrum.org/explore/World/AllSamples/Past6M/variants?variantQuery=G2782T+%2C+T111C&

[chaoran-chen]

Oh, that sounds like a bug! I wasn't aware that we , is allowed and don't know what it is doing.

[fengelniederhammer]

Looks like a bug in LAPIS 2. When switching to "Open", which still runs on LAPIS 1, you get a "malformed variant query":

[fengelniederhammer]

@chaoran-chen Should we actually allow or forbid sending multiple variant queries in a single request?

• Forbidding it would yield quite specific error messages
• Multiple values would be treated as "and" (as for any other sequence filter). Allowing it would implicitly make , on CoV Spectrum be interpreted as &, since comma separated values in query strings are decoded as arrays.

[fengelniederhammer]

As discussed: If the variantQuery is set, we expect exactly one value.

Providing multiple values for other filters mean "or", which would be weird for variant queries.