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
SQL: add utility functions for IP fields #34799
Labels
Comments
Pinging @elastic/es-search-aggs |
matriv
added a commit
to matriv/elasticsearch
that referenced
this issue
Oct 28, 2018
This allows comparison between IP fields and STRING input from the user where automatic conversion is not yet supported (e.g.: for IN) Closes: elastic#34799
matriv
pushed a commit
that referenced
this issue
Oct 29, 2018
This allows comparison between IP fields and STRING input from the user where automatic conversion is not yet supported (e.g.: for IN) Closes: #34799
matriv
pushed a commit
that referenced
this issue
Oct 29, 2018
This allows comparison between IP fields and STRING input from the user where automatic conversion is not yet supported (e.g.: for IN) Closes: #34799
matriv
pushed a commit
that referenced
this issue
Oct 29, 2018
This allows comparison between IP fields and STRING input from the user where automatic conversion is not yet supported (e.g.: for IN) Closes: #34799
kcm
pushed a commit
that referenced
this issue
Oct 30, 2018
This allows comparison between IP fields and STRING input from the user where automatic conversion is not yet supported (e.g.: for IN) Closes: #34799
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the support of IP fields, it becomes necessary to allow casting and parsing of various strings into IP fields. As IP fields are not supported by SQL itself it might be worth extending
CAST
to allow ES specific types:CAST (foo AS IP)
.Alternatively we could add a parsing function however the above seems much more simpler and intuitive.
The text was updated successfully, but these errors were encountered: