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

Python Plugin: Allow to use python for scripts #418

Closed
kimchy opened this issue Oct 9, 2010 · 1 comment
Closed

Python Plugin: Allow to use python for scripts #418

kimchy opened this issue Oct 9, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Oct 9, 2010

Allow to use python as scripts (lang set to python). doc, _fields, and _source are dicts.

@kimchy
Copy link
Member Author

kimchy commented Oct 9, 2010

Python Plugin: Allow to use python for scripts, closed by a754eba.

medcl pushed a commit to medcl/elasticsearch that referenced this issue Jul 1, 2011
medcl pushed a commit to medcl/elasticsearch that referenced this issue Jul 1, 2011
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…312021 (pull request elastic#418)

[MPC-4411] - Whiteboard files expiration rule for public rooms

* whiteboard files expirtaion rule for public rooms

* resolve nits from review


Approved-by: fabien
Approved-by: Anton Sapozhnikov
Approved-by: Can Yildiz
costin pushed a commit that referenced this issue Dec 6, 2022
Fixes #418

Renames in `project` require a small conceptual change in the local
execution planning: So far, the layout always contained one entry per
block and there was a 1:1 mapping from attributes to blocks/channels.
This assumption no longer holds as the same block might be mapped to
multiple attribute ids. E.g. the query `from test | project x = count, y
= count` creates a project operator that drops all blocks except `count`
and is associated with the mapping `Id(x) -> 0, Id(y) -> 0`.
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
This commit adds the race configurations for the geopointshape
benchmarks as discussed in elastic/night-rally#129 (comment)

These will be run on the new group-3 (ref: elastic/elasticsearch-benchmarks#401).

The necessary visualizations, as well the Jenkins job to trigger these
will come as a separate PR.

Relates elastic#129
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
This commit adds group-3 to the default scripts created by the
Vagrantfile that help testing nightly/release benchmarks.

This was missing from elastic#418.
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