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 QL Grand Refactor #106679
Labels
:Analytics/ES|QL
AKA ESQL
>enhancement
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Comments
Pinging @elastic/es-analytical-engine (Team:Analytics) |
elasticsearchmachine
added
the
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
label
Mar 22, 2024
The rest of Elasticsearch doesn't really use special exceptions for a project. I think it'd be worth seeing if we should standardize on the assortment of exceptions the rest of Elasticsearch uses. Not sure we'd actually do it, but worth checking. |
This was referenced Apr 29, 2024
elasticsearchmachine
pushed a commit
that referenced
this issue
May 16, 2024
…108609) Part of #106679 Add tests for our query translators for binary comparisons and ranges. Turns out, our query translators, which we use whenever we push down filters to Lucene, have only partial test coverage in some of the LocalPhysicalOptimzerTests. We need to expand test coverage, so this sets up the necessary plumbing and adds the first query translator spec tests.
nicktindall
pushed a commit
to nicktindall/elasticsearch
that referenced
this issue
May 17, 2024
…lastic#108609) Part of elastic#106679 Add tests for our query translators for binary comparisons and ranges. Turns out, our query translators, which we use whenever we push down filters to Lucene, have only partial test coverage in some of the LocalPhysicalOptimzerTests. We need to expand test coverage, so this sets up the necessary plumbing and adds the first query translator spec tests.
parkertimmins
pushed a commit
to parkertimmins/elasticsearch
that referenced
this issue
May 17, 2024
…lastic#108609) Part of elastic#106679 Add tests for our query translators for binary comparisons and ranges. Turns out, our query translators, which we use whenever we push down filters to Lucene, have only partial test coverage in some of the LocalPhysicalOptimzerTests. We need to expand test coverage, so this sets up the necessary plumbing and adds the first query translator spec tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Analytics/ES|QL
AKA ESQL
>enhancement
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Description
When we built ESQL we built it on top of QL's core, which itself was refactored fairly quickly out of SQL. It's what we had time for and it had a lot of goodies. But it brought a lot of baggage. SQL and EQL live on top of _search and ESQL doesn't, for example.
Expression
treeDataTypes
andEsqlDataTypes
)TypeResolutions
andEsqlTypeResolutions
)EvalMapper
with calls toEvaluatorMapper#toEvaluator
ExpressionTranslators
EvaluatorMapper
to ESQL'sExpression
superclassEsqlClientException
, and not onlyQlClientException
)The text was updated successfully, but these errors were encountered: