-
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: Add UNSUPPORTED type in unit tests #119639
Conversation
Pinging @elastic/es-analytical-engine (Team:Analytics) |
850f6cb
to
5e27838
Compare
5e27838
to
96ed2f0
Compare
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.
LGTM, although surely there are more tests than just union-types.csv-spec that use this?
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.
Thanks @GalLalouche ! I agree with this change, as it makes the expected results more correct.
Unsupported type is a very specific column type caused by unresolved unions. Or at least, no other unit tests failed due to this change ¯\_(ツ)_/¯. |
Small addition to tests, aligning their types better with production code.
96ed2f0
to
005d90a
Compare
I think there's other examples, although we likely just don't have unit tests for them. E.g. nested and flattened fields aren't supported and should produce this column type - c.f. here. |
💚 Backport successful
|
Small addition to tests, aligning their types better with production code.
Small addition to tests, aligning their types better with production code.
Small addition to tests, aligning their types better with production code.
Small addition to tests, aligning their types better with production code.