[
https://issues.apache.org/jira/browse/APEXMALHAR-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229912#comment-15229912
]
ASF GitHub Bot commented on APEXMALHAR-1966:
--------------------------------------------
Github user DT-Priyanka commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/227#discussion_r58836661
--- Diff:
contrib/src/main/java/com/datatorrent/contrib/cassandra/CassandraPOJOOutputOperator.java
---
@@ -102,20 +92,31 @@ public CassandraPOJOOutputOperator()
}
@Override
+ public void beginWindow(long windowId)
+ {
+ super.beginWindow(windowId);
+ recordsProcessed = 0;
+ errorRecords = 0;
+ }
+
+ @Override
public void activate(Context.OperatorContext context)
{
+ // clear if it had anything
+ columnDataTypes.clear();
--- End diff --
It was required as in same test I am first running insert query and then
update, let me see if I can refactor that, anyone in product we won't support
if a query and fieldInfo changes on fly.
> Cassandra output operator improvements
> --------------------------------------
>
> Key: APEXMALHAR-1966
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-1966
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Priyanka Gugale
> Assignee: Priyanka Gugale
>
> Update existing Cassandra output operator to:
> 1. Accept use defined parameterized queries, the queries could be for update,
> insert or delete.
> 2. Add error port to emit tuples which couldn't be written to database.
> 3. Add metrics
> 4. Provide a way to restrict batch size
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
