[GitHub] [pulsar] eolivelli commented on pull request #14102: PIP-144: Making SchemaRegistry implementation configurable

[GitBox <gi...@apache.org>]

eolivelli commented on pull request #14102:
URL: https://github.com/apache/pulsar/pull/14102#issuecomment-1073701863


   > @eolivelli Are you suggesting this from a runtime class conflict perspective? Schema storage in Pulsar is already pluggable (aside from the registry itself becoming pluggable in this PR) through this flag: `schemaRegistryStorageClassName`. Users are probably already making use of this and one way to avoid conflicts introduced by third party libs is that they end up using fat/shaded jars.
   
   Exactly. It is quite hard to deal with these problems, "fat/shaded jars" are a good trick, but I wonder if it is possible to address this problem the same way we are doing for many other components (Protocol Handlers, Additional Servlets, Package Management).
   Probably `schemaRegistryStorageClassName` was implemented when Pulsar didn't think much about extensibility problems.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org