Skip to content

Cast nulls as lists or intervals to avoid ambiguities#49

Open
antvaset wants to merge 1 commit intocqframework:mainfrom
antvaset:ambiguous-tests
Open

Cast nulls as lists or intervals to avoid ambiguities#49
antvaset wants to merge 1 commit intocqframework:mainfrom
antvaset:ambiguous-tests

Conversation

@antvaset
Copy link
Contributor

There are a few test cases in which nulls technically can be resolved as either Lists or Intervals. For example, null contains 5 can be interpreted as either Contains(List<Integer>, Integer) or Contains(Interval<Integer>, Integer).

This PR adds explicit casts to the cases with such ambiguities.

Copy link
Member

@brynrhodes brynrhodes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left this comment on the related PR in the Java CQL engine as well, but I don't understand why we would need to cast the null in the list operator cases? Shouldn't it resolve to a list since one of the arguments is known to be list-valued?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants