On Tue, 11 Feb 2025 at 19:56, Caleb Rackliffe <calebrackli...@gmail.com>
wrote:

> When we add IS [NOT] NULL support, that would preferably NOT match EMPTY
> values for the types where empty means something, like strings. For
> everything else, EMPTY could be equivalent to null and match IS NULL.
>


Makes sense to me to say this is what we intend in advance of IS NULL
landing.

i.e. `isEmptyValueMeaningless=true and v=EMPTY_BYTE_BUFFER` is for now
equivalent to what will be `IS NULL`, so isEmptyValueMeaningless
effectively (temporarily?) means isEmptyValueTreatedAsNull

And in the meantime just say that SAI currently does not support such NULL
values (and just leave it as-is wrong in 2i and SASI – they're legacy –
despite making CQL statements inconsistent depending on the index impl).

Reply via email to