You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Cursor returned by QueryableIndexStorageAdapter, the DimensionSelectors created from the Cursor have different null handling behavior for multi-value and single-value dimensions.
In the implementation of DimensionSelector.lookupName(id):
For multi-value dimensions, Strings.nullToEmpty() is called on the value before it is returned or passed to the extractionFn.
For single-value dimensions, there is no null->empty str conversion.
DimensionSelectors originating from an IncrementalIndex do not perform the null->empty str conversion either.
The text was updated successfully, but these errors were encountered:
@jon-wei@gianm can we put together a larger issue to aggregate all the null issues you've been seeing lately? It might make sense to have a more comprehensive view of all the issues to help figure out what needs to be done.
In the Cursor returned by QueryableIndexStorageAdapter, the DimensionSelectors created from the Cursor have different null handling behavior for multi-value and single-value dimensions.
In the implementation of DimensionSelector.lookupName(id):
DimensionSelectors originating from an IncrementalIndex do not perform the null->empty str conversion either.
The text was updated successfully, but these errors were encountered: