You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2017/05/27 13:40:04 UTC

[jira] [Commented] (APEXMALHAR-2502) Fix KuduOutput operator for extensibility

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

Thomas Weise commented on APEXMALHAR-2502:
------------------------------------------

The window data manager needs to be checkpointed and hence should be assigned when the operator is constructed, not in activate. In some situations it also makes sense to let the user decide what implementation of window data manager to use.

> Fix KuduOutput operator for extensibility
> -----------------------------------------
>
>                 Key: APEXMALHAR-2502
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2502
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: Ananth
>            Assignee: Ananth
>             Fix For: 3.8.0
>
>
> There are a couple of issues with the Kudu output operator when using in an application. 
> - The ApexKuduConnection class is not usable outside of the Abstract class
> - The NotNull annotation for the window data manager needs to be removed as the window manager is being assigned in the activate window and not in the constructor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)