# Ingest pipeline rename not working **URL:** \ **Category:** Kibana\ **Tags:** ingest-pipeline\ **Created:** [May 18, 2021, 6:14am UTC](https://discuss.elastic.co/t/ingest-pipeline-rename-not-working/273234 "2021-05-18T06:14:15Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![anjana1](https://avatars.discourse-cdn.com/v4/letter/a/22d042/32.png) [@anjana1](https://discuss.elastic.co/u/anjana1)\ **Post date:** [May 18, 2021, 6:14am UTC](https://discuss.elastic.co/t/ingest-pipeline-rename-not-working/273234/1 "2021-05-18T06:14:15Z")
Kibana version : 7.10.2 Elasticsearch version : 7.10.2 APM Server version : 7.10.2 APM Agent language and version : java 1.8 Fresh install or upgraded from other version? fresh install Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc. :-no I have created ingest node pipelines for my APM index. When I test the pipeline by adding a document, it successfully get executed. Its a rename pipeline. But when i index the document the rename is not happening. I see my pipeline is registered at APM server logs. But after indexing when I discover the index pattern I don't see the field getting renamed. the test pipeline shows a status :success. But after the events are triggered to APM server I don't see any changes at index level ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [May 20, 2021, 10:36pm UTC](https://discuss.elastic.co/t/ingest-pipeline-rename-not-working/273234/2 "2021-05-20T22:36:57Z")
Do you see any similarities with this logged issue here? > > > This bug was found when checking this issue https://github.com/elastic/kibana/is…sues/57843. > > Currently, the bug can be reproduced on the master branch https://github.com/elastic/kibana/commit/66e1d32db659a067f35502f5ebcaf0a976edf651 > > \*\*Describe the bug:\*\* > When a pipeline is created with % character in the name, the detail panel has an undefined and there are errors in the console. > > \*\*Steps to reproduce:\*\* > 1. Navigate to Elasticsearch -\> Ingest Node Pipelines > 2. Click button "create a pipeline" on the top of pipelines list, type in a name with % character, e.g. \`test%\` and some description. > 3. Click button "Create pipeline" on the bottom. > > After creating the pipeline, the navigation will return to the pipelines list with the created pipeline opened in the detail panel. The panel's title is \`undefined\` and the panel's body displays "A pipeline not found". > > If there is already an existing pipeline with % character in the list, clicking on the pipeline has the same effect. > > \*\*Expected behavior:\*\* > Detail panel is displayed without errors with information about the pipeline. > > \*\*Screenshots (if relevant):\*\* > \Screenshot 2020-05-12 at 14 57 13 > > \*\*Errors in browser console (if relevant):\*\* > angular.js:15570 URIError: URI malformed > at decodeURIComponent (\) > at areHashesDifferentButDecodedHashesEquals (sub\_url\_hooks\_utils.ts:36) > at sub\_url\_hooks.js:62 > at Scope.$broadcast (angular.js:19723) > at angular.js:15334 > at Scope.$digest (angular.js:19115) > at angular.js:15350 > at angular.js:6711 > at forEach (angular.js:387) > at fireStateOrUrlChange (angular.js:6710) > (anonymous) @ angular.js:15570 > (anonymous) @ angular.js:11849 > $broadcast @ angular.js:19725 > (anonymous) @ angular.js:15334 > $digest @ angular.js:19115 > (anonymous) @ angular.js:15350 > (anonymous) @ angular.js:6711 > forEach @ angular.js:387 > fireStateOrUrlChange @ angular.js:6710 > cacheStateAndFireUrlChange @ angular.js:6681 > dispatch @ jquery.js:5429 > elemData.handle @ jquery.js:5233 > > \*\*Any additional context:\*\* > The bug is only reproducible with % sign but not other "special" characters. Thanks Bhavya ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 17, 2021, 10:37pm UTC](https://discuss.elastic.co/t/ingest-pipeline-rename-not-working/273234/3 "2021-06-17T22:37:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.