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

Incorrect parameter names es.update.params and es.update.params.json in config examples #430

Closed
ppf2 opened this issue Apr 22, 2015 · 1 comment

Comments

@ppf2
Copy link
Member

ppf2 commented Apr 22, 2015

http://www.elastic.co/guide/en/elasticsearch/hadoop/current/configuration.html#_update_settings

es.update.script.params (default none)
Script parameters (if any). The document (currently read) field/property who’s value is used. To specify a constant, use the format. Multiple values can be specified through commas (,)
For example:

specifying 2 parameters, one extracting the value from field 'number', the other containing the value '123':
es.update.params = param1:number,param2:<123>

es.update.script.params.json
Script parameters specified in raw, JSON format. The specified value is passed as is, without any further processing or filtering. Typically used for migrating existing update scripts.
For example:
es.update.params.json = {"param1":1, "param2":2}

The doc specifies es.update.script.params and es.update.script.params.json as configuration options. But in their respective examples, it references es.update.params and es.update.params.json instead of the correct parameter names ( es.update.script.params and es.update.script.params.json)

@ppf2 ppf2 added the doc label Apr 22, 2015
costin added a commit that referenced this issue Apr 24, 2015
costin added a commit that referenced this issue Apr 24, 2015
relates #430

(cherry picked from commit 35ece7f)
@costin
Copy link
Member

costin commented Apr 24, 2015

Thanks, fixed the docs in master and 2.x

@costin costin closed this as completed Apr 24, 2015
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

2 participants