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

Add support for parameters to the script ingest processor #20136

Merged
merged 1 commit into from
Aug 25, 2016

Conversation

imotov
Copy link
Contributor

@imotov imotov commented Aug 24, 2016

The script processor should support params to be consistent with all other script consumers.

@imotov imotov added >enhancement review :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP v5.0.0-beta1 labels Aug 24, 2016
@talevy
Copy link
Contributor

talevy commented Aug 24, 2016

LGTM

CompiledScript compiledScript = scriptService.compile(script, ScriptContext.Standard.INGEST, emptyMap());
ExecutableScript executableScript = scriptService.executable(compiledScript, vars);
ExecutableScript executableScript = scriptService.executable(script, ScriptContext.Standard.INGEST, emptyMap());
executableScript.setNextVar("ctx", document.getSourceAndMetadata());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks new. I like this update!

The script processor should support `params` to be consistent with all other script consumers.
@imotov imotov force-pushed the enable-params-in-script-processor branch from 304f797 to b36fbc4 Compare August 25, 2016 01:08
@imotov imotov merged commit b36fbc4 into elastic:master Aug 25, 2016
@imotov imotov deleted the enable-params-in-script-processor branch May 1, 2020 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement v5.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants