Well for Kafka too the old version had one huge string or a url to read an external configuration. I really disliked this and therefore completely rewrote the config to utilize Kafka Connect's internal configuration auditing facilities.
Chris Am 08.10.19, 12:51 schrieb "Julian Feinauer" <[email protected]>: Hey Chris, of Camel, you mean? Julian Am 08.10.19, 12:44 schrieb "Christofer Dutz" <[email protected]>: That was what many modules for Kafka seem to do, but I strongly disliked that option as it totally avoids the internal mechanisms of the framework. Chris Holen Sie sich Outlook für Android<https://aka.ms/ghei36> ________________________________ From: Julian Feinauer <[email protected]> Sent: Tuesday, October 8, 2019 12:33:53 PM To: [email protected] <[email protected]> Subject: Re: Camel integration for Scraper Another idea could be to point it tot he (external) resource which is our current yml like used here: https://camel.apache.org/components/latest/json-validator-component.html J Am 08.10.19, 12:29 schrieb "Julian Feinauer" <[email protected]>: Hi all, I know that we have a Camel Component but as most of us agree its of limited use to scrape only one value. Thus, other integrations (like ES and Kafka, AFAIR) use the (Triggered)Scraper as basis of their integration. I suggest to do the same with Camel (this would be really useful for us). But I don’t want to hack everything into this small connection string (ugly!). As I found out, there are also other ways to do that, e.g. for the Camel Avro integration: https://camel.apache.org/components/latest/avro-dataformat.html This would be my preffered way to go. Any Ideas or objections for that approach? Julian
