Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Match all topics with pattern #65

Closed
treziac opened this issue Feb 8, 2017 · 3 comments
Closed

Match all topics with pattern #65

treziac opened this issue Feb 8, 2017 · 3 comments
Labels

Comments

@treziac
Copy link

treziac commented Feb 8, 2017

Hi,

Is it possible, instead of passing a list of topics in "topics" config, to pass a template (ex: event.member.* will match all kafka topics starting with event.member. and place them in the corresponding index), which would also scan for newly ceated topics?

@treziac treziac changed the title Match all topics with wildcard Match all topics with pattern Feb 8, 2017
@tslater
Copy link

tslater commented May 3, 2017

I'm trying to figure out the same thing. I get:

[pool-1-thread-3] WARN org.apache.kafka.clients.NetworkClient - Error while fetching metadata with correlation id 105 : {topicprefix.*=INVALID_TOPIC_EXCEPTION}

Is this an option? Or do we have to know each, specific topic?

@ewencp ewencp added the question label May 3, 2017
@ewencp
Copy link
Contributor

ewencp commented May 3, 2017

@treziac & @tslater That's actually a config that's common to all sink connectors and defined by the Kafka Connect framework. That feature is currently missing -- we have https://issues.apache.org/jira/browse/KAFKA-3073 filed to track that request in Kafka.

I'm going to close this for now since this is already tracked in the Kafka project, but reopen if you have any further questions/clarifications.

@ewencp ewencp closed this as completed May 3, 2017
@kmillanr
Copy link

@treziac & @tslater That's actually a config that's common to all sink connectors and defined by the Kafka Connect framework. That feature is currently missing -- we have https://issues.apache.org/jira/browse/KAFKA-3073 filed to track that request in Kafka.

I'm going to close this for now since this is already tracked in the Kafka project, but reopen if you have any further questions/clarifications.

Hello, it has been 2 years. Was this ever solved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants