You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by David Capwell <dc...@apple.com> on 2025/03/19 18:36:17 UTC

Re: Meaningless emptiness and filtering

Been expanding the current AST Harry tests to include collections and UDTs and been finding even more fun with <empty> vs null… what Cassandra returns is a product of the schema and what you do with the table; and these types can act differently than other types.

> On Feb 13, 2025, at 4:45 AM, Mick Semb Wever <mc...@apache.org> wrote:
> 
>    
> 
> On Tue, 11 Feb 2025 at 19:56, Caleb Rackliffe <calebrackliffe@gmail.com <ma...@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).
>