-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESQL: Explain IN #119514
ESQL: Explain IN #119514
Conversation
Adds javadoc to IN to explain it's three-valued null logic and why it isn't using the standard code generators.
Pinging @elastic/es-analytical-engine (Team:Analytics) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, wait, the behavior here is that, if the set to match contains a null, we return true
if the value to test matches one of the non-null values, and null
if it does not? If that's the intent, I think we should be explicit about it, I had to read those rules three times to understand this was how it worked.
.../src/main/java/org/elasticsearch/xpack/esql/expression/predicate/operator/comparison/In.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The examples help a lot. Thanks for updating this.
Oh shoot. I didn't auto-backport. I'll do it by hand. |
* ESQL: Explain IN Adds javadoc to IN to explain it's three-valued null logic and why it isn't using the standard code generators. * Paste more examples
backport: #119514 |
Adds javadoc to IN to explain it's three-valued null logic and why it isn't using the standard code generators.
Relates to #119480