You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@rya.apache.org by "Jeff Dasch (JIRA)" <ji...@apache.org> on 2017/08/17 15:52:02 UTC
[jira] [Updated] (RYA-345) KafkaBindingSetExporterFactory does not
support multiple Kafka bootstrap servers.
[ https://issues.apache.org/jira/browse/RYA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Dasch updated RYA-345:
---------------------------
Description:
KafkaBindingSetExporterFactory needs to be updated to be able to handle a CSV (or ;SV) for the key ProducerConfig.BOOTSTRAP_SERVERS_CONFIG in the event the user is providing multiple bootstrap servers for Kafka. This implementation would be similar to how RyaBindingSetExporterFactory handles the CSV for the zookeeper connect.
An alternative option is to migrate to Fluo 1.1.0-incubating and implement an ObserverProvider. This may then eliminate the need for the above modification.
Or possibly take advantage of this section of the fluo.properties file:
{noformat}
#Application properties
#---------------
#Properties with a prefix of fluo.app are stored in zookeeper at
#initialization time and can easily be retrieved by a Fluo application running
#on any node in the cluster.
#fluo.app.config1=val1
{noformat}
was:
KafkaBindingSetExporterFactory needs to be updated to be able to handle a CSV (or ;SV) for the key ProducerConfig.BOOTSTRAP_SERVERS_CONFIG in the event the user is providing multiple bootstrap servers for Kafka. This implementation would be similar to how RyaBindingSetExporterFactory handles the CSV for the zookeeper connect.
An alternative option is to migrate to Fluo 1.1.0-incubating and implement an ObserverProvider. This may then eliminate the need for the above modification.
> KafkaBindingSetExporterFactory does not support multiple Kafka bootstrap servers.
> ---------------------------------------------------------------------------------
>
> Key: RYA-345
> URL: https://issues.apache.org/jira/browse/RYA-345
> Project: Rya
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.2.10
> Reporter: Jeff Dasch
> Priority: Minor
>
> KafkaBindingSetExporterFactory needs to be updated to be able to handle a CSV (or ;SV) for the key ProducerConfig.BOOTSTRAP_SERVERS_CONFIG in the event the user is providing multiple bootstrap servers for Kafka. This implementation would be similar to how RyaBindingSetExporterFactory handles the CSV for the zookeeper connect.
> An alternative option is to migrate to Fluo 1.1.0-incubating and implement an ObserverProvider. This may then eliminate the need for the above modification.
> Or possibly take advantage of this section of the fluo.properties file:
> {noformat}
> #Application properties
> #---------------
> #Properties with a prefix of fluo.app are stored in zookeeper at
> #initialization time and can easily be retrieved by a Fluo application running
> #on any node in the cluster.
> #fluo.app.config1=val1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)