apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay M Pujare (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-2068) FileSplitter- having multiple file splitters in an application results in incorrect behavior
Date Wed, 06 Jul 2016 22:53:11 GMT

    [ https://issues.apache.org/jira/browse/APEXMALHAR-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365274#comment-15365274
] 

Sanjay M Pujare commented on APEXMALHAR-2068:
---------------------------------------------

Regarding dependency on APEXCORE-448 , is there any reason why we can't use the ID (returned
by OperatorContext.getId() ) for uniquifying the recoveryPath in FSWindowDataManager instead
of trying to get the operator name from the OperatorContext?

> FileSplitter- having multiple file splitters in an application results in incorrect behavior
> --------------------------------------------------------------------------------------------
>
>                 Key: APEXMALHAR-2068
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2068
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: Chandni Singh
>            Assignee: Chandni Singh
>
> If an application has multiple logical operators that use Window Data Manager, then by
default they share the same state. This is confusing and cause issues.
> We need to make this path unique by default for each logical instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message