[
https://issues.apache.org/jira/browse/KAFKA-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964345#comment-14964345
]
Ashish K Singh commented on KAFKA-2671:
---------------------------------------
bq. What's the use-case for starting Kafka server as a Singleton inside another
application?
I am trying to wrap kafka.Kafka in an app that takes care of config management
in a secure way. The goal of the app is not to use Kafka, but to just start it.
To be honest its a simple wrapper :).
bq. The reason I'm asking is that I've actually seen this requirement before,
and it seemed like a rather misguided attempt to use Kafka as a local queue for
a webserver (and use a local Kafka rather than a producer to a remote Kafka).
I'm rather concerned about enabling such use-cases, as they can lead to more
problems down the road.
Misguided attempts are still doable with the existing options, right?
bq. Also, are you sure you want to instantiate Kafka with a start() method to a
singleton? This is kind of non-standard.
That is true. Once I get a go on the idea, I can handle that in PR by
extracting to a separate class.
> Enable starting Kafka server with a Properties object
> -----------------------------------------------------
>
> Key: KAFKA-2671
> URL: https://issues.apache.org/jira/browse/KAFKA-2671
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Reporter: Ashish K Singh
> Assignee: Ashish K Singh
>
> Kafka, as of now, can only be started with a properties file and override
> params. It makes life easier for management applications to be able to start
> Kafka with a properties object programatically.
> The changes required to enable this are minimal, just a tad bit of
> refactoring of kafka.Kafka. The changes must maintain current behavior intact.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
