[
https://issues.apache.org/jira/browse/APEXMALHAR-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319589#comment-15319589
]
ASF GitHub Bot commented on APEXMALHAR-1966:
--------------------------------------------
Github user bhupeshchawda commented on a diff in the pull request:
https://github.com/apache/apex-malhar/pull/295#discussion_r66164298
--- Diff:
benchmark/src/main/java/com/datatorrent/benchmark/cassandra/CassandraOutputOperator.java
---
@@ -48,4 +48,9 @@ protected Statement
setStatementParameters(PreparedStatement updateCommand,
return boundStmnt.bind(id++,tuple);
}
+ @Override
+ public void deactivate()
--- End diff --
Can you move this to the Abstract parent class? Otherwise every
implementation would have to include this method.
> 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)
