apupier commented on issue #430: URL: https://github.com/apache/camel-kafka-connector/issues/430#issuecomment-692693787
> To summarize to see if I have understood correctly, you are proposing to create a new camel catalog specific for camel-kafka-connector containing all the information you mentioned? > > As has been said that would be more or less a mapping of the original camel catalog with some prefixes for now... at the moment the other info you are listing (converters, transformers, aggregation strategies) are not present. not exactly, i'm proposing to create the Catalog for everything that is not coming from the original Camel catalog. Currently, we cannot provide anything for Camel Kafka Connector (apart from harcoding it but I really don't think that itis a good idea to follow this path). Even for the part that can be "mapped from the original camel catalog", there is missing information in the Properties file to know which Camel connector id needs to be used. See https://issues.redhat.com/browse/FUSETOOLS2-670 > It remains the problem relative to the properties coming directly from kafka connect, did you investigate if there is a way to gathering those from somewhere in kafka? no. I'm awaiting feedback from Developer Tooling team that should come with plans for Kafka tooling in general. I hope it would include the kafka /kafka Connect properties (but I have absolutely no visibility so far on that, they just told me to wait). This is a very separate problem than this issue anyway. ---------------------------------------------------------------- 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: us...@infra.apache.org
