Skip to content
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

[ES|QL] Improvements on appendWhereClauseToESQLQuery #184726

Open
stratoula opened this issue Jun 4, 2024 · 3 comments
Open

[ES|QL] Improvements on appendWhereClauseToESQLQuery #184726

stratoula opened this issue Jun 4, 2024 · 3 comments
Labels
enhancement New value added to drive a business result Feature:ES|QL ES|QL related features in Kibana impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ESQL ES|QL related features in Kibana

Comments

@stratoula
Copy link
Contributor

Describe the feature:

  • Now that the ES team supports more casting naturally the ::string operator is not needed in the majority of the cases. We need to check where it is not needed and dont append it

  • Improve the variables wrapping in backquotes, we can check if the name needs to be quoted and add them conditionally

@stratoula stratoula added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Feature:ES|QL ES|QL related features in Kibana Team:ESQL ES|QL related features in Kibana labels Jun 4, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-esql (Team:ESQL)

@stratoula stratoula added the enhancement New value added to drive a business result label Jun 4, 2024
@drewdaemon
Copy link
Contributor

drewdaemon commented Jun 4, 2024

Now that the ES team supports more casting naturally the ::string operator is not needed in the majority of the cases. We need to check where it is not needed and dont append it

It's true that they do some implicit casting, but there may be inconsistencies (I have discovered them in the past). I guess we should think about which is the priority: help the ES team be more consistent or make sure the queries are always correct.

If we want to help the ES team be consistent, we could remove the explicit string casting, but there may be bugs that need to be reported and fixed.

I kind of like that route since it makes everyone better, but I'm just pointing out a potential cost.

@stratoula
Copy link
Contributor Author

stratoula commented Jun 4, 2024

Yes this why it is a priority low Drew now, I agree with you ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:ES|QL ES|QL related features in Kibana impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ESQL ES|QL related features in Kibana
Projects
None yet
Development

No branches or pull requests

3 participants