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

Search: Sending a request that fails to parse can cause file leaks #270

Closed
kimchy opened this issue Jul 21, 2010 · 1 comment
Closed

Search: Sending a request that fails to parse can cause file leaks #270

kimchy opened this issue Jul 21, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Jul 21, 2010

The search context is being released, but too late in the game and the file leaks are aggregated. The context should be when the failure happens.

@kimchy
Copy link
Member Author

kimchy commented Jul 21, 2010

Search: Sending a request that fails to parse can cause file leaks, closed by 8ec7ee6.

mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
Updates for miro webpage

* Updates for miro webpage

* remove no-referrer policy else miro anon boards will not work


Approved-by: Gideon Avida
Approved-by: Alan Nuchnoi
Approved-by: Can Yildiz
costin pushed a commit that referenced this issue Dec 6, 2022
Integrates the compute engine with the ESQL frontend.

This PR adds physical plan nodes, as well as mappers to turn logical into physical plan nodes and optimize the physical plan to determine where data should be extracted and how parallelism is to be introduced. It further compiles down a physical plan to a set of drivers (containing operators) that can then be executed.

All this is integrated into the _esql REST endpoint, which now allows to run tests such as `from test | eval x = count + 7 | sort x | limit 1` and `from test | stats avg_count = avg(count) | eval x = avg_count + 7`.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant