# Renaming of auto-generated field names (created by Postgres connector) **URL:** \ **Category:** Elasticsearch\ **Tags:** docker, connectors\ **Created:** [August 8, 2024, 2:18pm UTC](https://discuss.elastic.co/t/renaming-of-auto-generated-field-names-created-by-postgres-connector/364612 "2024-08-08T14:18:47Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![andrej.peplinski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrej.peplinski/32/40293_2.png) [@andrej.peplinski](https://discuss.elastic.co/u/andrej.peplinski)\ **Post date:** [August 8, 2024, 2:18pm UTC](https://discuss.elastic.co/t/renaming-of-auto-generated-field-names-created-by-postgres-connector/364612/1 "2024-08-08T14:18:47Z")
Dear Elastic team, I am currently using an Elasticsearch docker cluster with a Postgres connector and Kibana using a **basic** license. I am able to synchronize my data but find the default field names that are being generated _unfortunate_ since I am only synchronizing a single table. Appearently the following naming scheme is being use `schema_table_field` - but this leads to very long field names. I assume that I need to use a custom pipeline but in Kibana I see the following message: > Custom pipelines require a Platinum license or higher and are not available to Standard license self-managed deployments. You need to upgrade to use this feature. > > Did you know that custom pipelines are available with a Standard Elastic Cloud license? Elastic Cloud gives you the flexibility to run where you want. Deploy our managed service on Google Cloud, Microsoft Azure, or Amazon Web Services, and we'll handle the maintenance and upkeep for you. So my question is: **Which options do I have to rename the field names?** Thanks in advance 🌻 ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [August 8, 2024, 2:26pm UTC](https://discuss.elastic.co/t/renaming-of-auto-generated-field-names-created-by-postgres-connector/364612/2 "2024-08-08T14:26:33Z")
> [@andrej.peplinski](#): > > Custom pipelines require a Platinum license or higher and are not available to Standard license self-managed deployments. You need to upgrade to use this feature. Can you share exactly where you did saw this message? I'm using the basic license and a I can create custom ingest pipelines, so not sure where this is coming from. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [August 8, 2024, 2:32pm UTC](https://discuss.elastic.co/t/renaming-of-auto-generated-field-names-created-by-postgres-connector/364612/3 "2024-08-08T14:32:54Z")
Oh, sorry, my mistake. I thought you were talking about Elastic Agent integrations, but this is related to Enterprise Search. I just found where this message shows up. I do not use Enterprise Search, but looking at it, it seems to use a managed ingest pipeline named `ent-search-generic-ingestion`, while it is not recommended you could try to add a `pipeline` processor in this managed ingest pipeline to call another pipeline with your renames. I'm not sure this will work as it does not make much sense to require a License to use a custom ingest pipeline, but at the same time being able to edit the managed ingest pipeline to add processors. Maybe someone from Elastic has a better explanation. ---
**Author:** ![Jedr\_Blaszyk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jedr_blaszyk/32/127637_2.png) [@Jedr\_Blaszyk](https://discuss.elastic.co/u/Jedr_Blaszyk)\ **Post date:** [August 23, 2024, 9:54am UTC](https://discuss.elastic.co/t/renaming-of-auto-generated-field-names-created-by-postgres-connector/364612/4 "2024-08-23T09:54:28Z")
Hey @andrej.peplinski Looking at the documentation, yes for index-level cusom pipelines for connectors basic license is not sufficient: [Ingest pipelines in Search | Elasticsearch Guide [8.14] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.14/ingest-pipeline-search.html#ingest-pipeline-search-details-specific) Perhaps you can create a new ingest pipeline, and directly attach it to the index to which connector syncs data, I think you can set the default pipeline for your index: [Ingest pipelines | Elasticsearch Guide [8.15] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html#set-default-pipeline). It should work, but it might be a bit more of a hassle to manage. Alternatively, if you are running [postgresql connector](https://www.elastic.co/guide/en/enterprise-search/current/connectors-postgresql.html) as a self-managed connector, you can customize the connector source code to achieve the desired result. See: [connectors/connectors/sources/postgresql.py at main · elastic/connectors · GitHub](https://github.com/elastic/connectors/blob/main/connectors/sources/postgresql.py#L687) Hope this helps!