[
https://issues.apache.org/jira/browse/SAMZA-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566157#comment-14566157
]
Yan Fang commented on SAMZA-694:
--------------------------------
Hi [~theduderog],
{quote}
Since the user is not allowed to configure the name of the log stream (why
not?), then the Samza should create the topic automatically as it does with
checkpoint topics.
{quote}
I should have mentioned this in the doc. SAMZA-695 for updating the doc.
Actually you can set the topic name by
{code}
<param name="StreamName" value="foo">
{code}
{quote}
the Samza should create the topic automatically as it does with checkpoint
topics.
{quote}
This had some potential issues previously because the StreamAppender does not
have any knowledge about how many partitions the job has. That's why I did not
put auto-creation in the code. But maybe it's time to revisit because we have
refactored some code. It maybe possible now.
> Log4j stream appender should create the log topic in Kafka
> ----------------------------------------------------------
>
> Key: SAMZA-694
> URL: https://issues.apache.org/jira/browse/SAMZA-694
> Project: Samza
> Issue Type: Improvement
> Components: log4j
> Affects Versions: 0.9.0
> Reporter: Roger Hoover
>
> If your Kafka brokers do not allow auto topic creation, then the log4j stream
> appender will just block if the log topic is not already created.
> Since the user is not allowed to configure the name of the log stream (why
> not?), then the Samza should create the topic automatically as it does with
> checkpoint topics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
