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

Streams Configuration Reuse - Bootstrap Vector #2

Open
d-t-w opened this issue Oct 6, 2021 · 1 comment
Open

Streams Configuration Reuse - Bootstrap Vector #2

d-t-w opened this issue Oct 6, 2021 · 1 comment

Comments

@d-t-w
Copy link
Member

d-t-w commented Oct 6, 2021

End users and our sample Spring Cloud integration both identify issue with reusing the Spring config, e.g:

StreamsBuilderFactoryBean streamsBuilderFactoryBean = context.getBean("&stream-builder-process", StreamsBuilderFactoryBean.class);
        KafkaStreams streams = streamsBuilderFactoryBean.getKafkaStreams();
        Topology topology = streamsBuilderFactoryBean.getTopology();

        // Create connection properties for the StreamsRegistry producer to send metrics to internal kPow topics
        // You should be able to use streamsBuilderFactoryBean.getStreamsConfiguration() but in this particular case
        // Those properties contain 'bootstrap.servers = [[localhost:9092]]' which errors on startup
        
        Properties properties = new Properties();
        properties.setProperty("bootstrap.servers", "127.0.0.1:9092");

From README: https://github.com/operatr-io/kpow-streams-agent-example-spring

  1. Investigate why Bootstrap presented as an array of nodes.
  2. Identify if it's possible other configuration params have unexpected format.
  3. Interpret or make error case very clear, depending on (1) and (2)
@d-t-w
Copy link
Member Author

d-t-w commented Oct 6, 2021

Tom points out this might just be an array of bootstrap being valid for streams config but not producer.

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

No branches or pull requests

1 participant