[
https://issues.apache.org/jira/browse/APEXMALHAR-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027662#comment-16027662
]
Munagala V. Ramanath commented on APEXMALHAR-2502:
--------------------------------------------------
The _windowDataManager_ field in _AbstractKuduOutputOperator_ is currently set
in _setup()_, not
_activate()_.
The _AbstractFileInputOperator_ assigns this field at the point of declaration
to a _NoopWindowDataManager_ with the expectation that, if exactly-once
semantics are desired, it will be set to a non-vacuous object by:
+ the application (in _populateDAG_ using the setter method); or
+ in the constructor of a concrete class; or
+ in the setup method after checking the class of the currently set value
The _AbstractKafkaInputOperator_ does likewise though it is missing the
_@NotNull_ annotation; it also has an _isIdempotent()_ method that does the
class check.
> 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)
