[
https://issues.apache.org/jira/browse/CHUKWA-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731172#action_12731172
]
Ari Rabkin commented on CHUKWA-349:
-----------------------------------
This isn't just about Demux boundaries; won't this come up whenever a user
tries to visualize a still-ongoing job?
> State-machine generation across split files
> -------------------------------------------
>
> Key: CHUKWA-349
> URL: https://issues.apache.org/jira/browse/CHUKWA-349
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: Data Processors
> Affects Versions: 0.3.0
> Reporter: Jiaqi Tan
> Assignee: Jiaqi Tan
> Fix For: 0.3.0
>
>
> Current SALSA state-machine generation assumes input files contain all starts
> and ends of all states; this may not be the case if the input data is sliced
> across Demux boundaries. There is a need to track incomplete data across
> multiple runs of the FSMBuilder and to expire and purge state as it's kept
> past a certain duration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
