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 2018/12/21 20:28:45 UTC

[GitHub] rdhabalia commented on issue #3228: Provide separate module with Pulsar v1 client API wrapper

rdhabalia commented on issue #3228: Provide separate module with Pulsar v1 client API wrapper
URL: https://github.com/apache/pulsar/pull/3228#issuecomment-449490693
 
 
   It raises few questions for the clients who are using V1 api and not ready to move V2 yet but still want to use new features.
   1. are we going to maintain this V1 api artifact with the new configuration changes?
   2. it will enforce client app to change artifact dependency else their existing app will fail.
   
   So, instead can't we keep this api into the same pulsar-client artifact because anyway it doesn't have many classes and it will be easy to maintain if we have everything under one location.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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