bemoore34 opened a new issue #11525: URL: https://github.com/apache/pulsar/issues/11525
**Is your enhancement request related to a problem? Please describe.** It is not possible to specify an Elasticsearch ingest pipeline when using the built-in Puslar Elasticsearch Sink Connector. It is common to use Elasticsearch ingest pipelines to perform additional processing on documents prior to being indexed, like geo-ip enrichment, date formatting, etc. **Describe the solution you'd like** It would be very useful to have the pipeline name be added as an optional configuration item, if possible, It appears that the Java High Level REST Client appears to support specifying an optional pipeline. **Describe alternatives you've considered** I have considered writing a Pulsar Function to do the job but would prefer to avoid reinventing the wheel. I am using a Python Pulsar Client consumer to get events from a topic and send them to Elasticsearch, providing the ingest pipeline. I would prefer to use the Puslar function (connectors) to do this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
