[
https://issues.apache.org/jira/browse/SAMZA-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267401#comment-14267401
]
Yan Fang commented on SAMZA-502:
--------------------------------
After further exploration, actually this issue was fixed in SAMZA-461, because
after that patch, if the stream is empty, it will use the upcoming offset
instead of the "null". So far I do not see any side-effect of doing that. If
you guys agree, think we can close this issue.
> BootstrappingChooser never unblocks if bootstrap topic is initially empty
> --------------------------------------------------------------------------
>
> Key: SAMZA-502
> URL: https://issues.apache.org/jira/browse/SAMZA-502
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.8.0
> Reporter: Roger Hoover
> Assignee: Yan Fang
> Priority: Critical
> Fix For: 0.9.0
>
>
> To reproduce:
> - Create a job that bootstraps topic "config" and consumes topic "events"
> - Create both topics in Kafka but only populate the "events" topic
> - Start the job
> - Now populate the "config" topic
> What happens:
> - The job will consume the messages in the "config" topic but not unblock the
> "events" topic
> What should happen:
> * Either
> ** Samza should consider an empty bootstrap topic as "caught up" and
> immediately start processing the "event" topic
> ** Samza should consider an empty bootstrap topic as a fatal error and exit
> I uploaded some trace logs here in case they help:
> http://pastebin.com/RsdwYkRk
> In this case, the bootstrap topic is called
> "ops.web.parse_rules__ck_4_module" and the event topic is called
> "ops._raw.web_parsed"
> I'm testing using the ProcessJobFactory in case it matters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
