# Setting the pipeline in Fluentd **URL:** \ **Category:** Elasticsearch\ **Created:** [June 5, 2019, 2:09pm UTC](https://discuss.elastic.co/t/setting-the-pipeline-in-fluentd/184379 "2019-06-05T14:09:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![nicks1993](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicks1993/32/84627_2.png) [@nicks1993](https://discuss.elastic.co/u/nicks1993)\ **Post date:** [June 5, 2019, 2:09pm UTC](https://discuss.elastic.co/t/setting-the-pipeline-in-fluentd/184379/1 "2019-06-05T14:09:12Z")
Hello, this is part of a long running discussion I've been having here with the most recent post being [How to use pipelines and processors](https://discuss.elastic.co/t/how-to-use-pipelines-and-processors/183719/10) I'm having a hard time finding where to add the pipeline in fluentd so that the data will flow through there at ingest. Thanks ---
**Author:** ![BenTrent](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bentrent/32/33915_2.png) [@BenTrent](https://discuss.elastic.co/u/BenTrent)\ **Post date:** [June 5, 2019, 4:05pm UTC](https://discuss.elastic.co/t/setting-the-pipeline-in-fluentd/184379/2 "2019-06-05T16:05:14Z")
Hey @nicks1993, We are definitely not experts on fluentd since it is not part of the Elastic stack. However, looking at the docs: [https://github.com/uken/fluent-plugin-elasticsearch#pipeline](https://github.com/uken/fluent-plugin-elasticsearch#pipeline) It seems like adding `pipeline ` as a config setting should work. The official docs seem outdated [https://docs.fluentd.org/output/elasticsearch#parameters](https://docs.fluentd.org/output/elasticsearch#parameters) ---
**Author:** ![nicks1993](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicks1993/32/84627_2.png) [@nicks1993](https://discuss.elastic.co/u/nicks1993)\ **Post date:** [June 6, 2019, 11:44am UTC](https://discuss.elastic.co/t/setting-the-pipeline-in-fluentd/184379/3 "2019-06-06T11:44:52Z")
Thanks I believe I figured it out. But now I'm getting a conflict on the duration field because I created a duration field manually earlier and now the pipeline is trying to create or store the wrong values in it. What is the best way to fix this? Can I remove fields? ---
**Author:** ![BenTrent](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bentrent/32/33915_2.png) [@BenTrent](https://discuss.elastic.co/u/BenTrent)\ **Post date:** [June 6, 2019, 11:58am UTC](https://discuss.elastic.co/t/setting-the-pipeline-in-fluentd/184379/4 "2019-06-06T11:58:38Z")
Depends on what you mean by "wrong values". > created a duration field manually If this was done inside the index mapping, then either update the mapping, or change the pipeline so that it creates a field that can be indexed according to that mapping. If this was done upstream, I am not 100% sure what the issue is. The pipeline should be able to overwrite fields without any issues. But if you just want to drop the previous duration field: [Remove processor | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/remove-processor.html) should work. ---
**Author:** ![nicks1993](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicks1993/32/84627_2.png) [@nicks1993](https://discuss.elastic.co/u/nicks1993)\ **Post date:** [June 6, 2019, 12:14pm UTC](https://discuss.elastic.co/t/setting-the-pipeline-in-fluentd/184379/5 "2019-06-06T12:14:48Z")
It seems I have 3 types in one field **Field Type Conflict:** The type of this field changes across indices. It is unavailable for many analysis functions. The indices per type are as follows: field types: text, integer, long ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 4, 2019, 12:14pm UTC](https://discuss.elastic.co/t/setting-the-pipeline-in-fluentd/184379/6 "2019-07-04T12:14:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.