-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[FEATURE] add processors: set: copy_from #4672
Comments
Are you suggesting we implement Please feel free to contribute an implementation without looking at/copying any code from Elasticseach. |
i am asking to implement something that allows compatibility with pipelines created for elasticsearch 7.11 and newer and use i'm not asking to copy their implementation of that field . happy to help in any way, but i am not a software developer unfortunately so i wouldn't know where to start |
I arrived here searching how to properly rename a field on a ingest pipeline using ingest processors. Previously on Elasticsearch I used to apply rename processor but it seems like it is not available on Opensearch. Then I tried to find another approach and landed here. Does it exist a supported "out of the box" solution to rename a field on Opensearch? Please tell me there is a better solution than this:
|
OMG the dev tools suggest me to use "rename": I dit not even tried to use that because It does not appear on the official doc section. It seems like it worked! :) maybe it should be added to the documentation? |
If it's missing, please do at least open an issue in the doc repo (or just fix it!). |
It looks like a PR already exists |
Describe the bug
With Elasticsearch 7.11 (i.e. the version immediately after OpenSearch fork), "copy_from" option for the "set" processor has been introduced, here - https://www.elastic.co/guide/en/elasticsearch/reference/7.11/set-processor.html
this breaks a lot of pipelines, registering pipelines will throw the following error:
a workaround is available and requires to change
to
The text was updated successfully, but these errors were encountered: