You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/05/07 12:32:37 UTC

[GitHub] [pulsar] shiv4289 opened a new issue #3954: [pulsar-flink] Use Map as pulsar native client configs

shiv4289 opened a new issue #3954: [pulsar-flink] Use Map<String, Object> as pulsar native client configs
URL: https://github.com/apache/pulsar/issues/3954
 
 
   **Is your feature request related to a problem? Please describe.**
   The current implementation of pulsar-flink takes serviceUrl and topic as params and initialises pulsar client from these params. It is not possible to pass other pulsar client params to pulsar-flink connector.
   
   **Describe the solution you'd like**
   pulsar-flink should accept all the params pulsar-client accepts. This should also be extensible so future pulsar-client params can be sent without any modifications to the pulsar-flink module. The idea is to accept pulsar-client params as Map<String, Object> and pass this map to the pulsar-client builder.
   
   This would sit well with the future additions in pulsar-client in future too.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services