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

ASF GitHub Bot commented on APEXMALHAR-1966:
--------------------------------------------

Github user bhupeshchawda commented on a diff in the pull request:

    
https://github.com/apache/incubator-apex-malhar/pull/227#discussion_r58707688
  
    --- Diff: 
contrib/src/test/java/com/datatorrent/contrib/cassandra/CassandraOperatorTest.java
 ---
    @@ -269,15 +269,38 @@ public void testCassandraOutputOperator()
         fieldInfos.add(new FieldInfo("set1", "set1", null));
         fieldInfos.add(new FieldInfo("test", "test", null));
     
    -    outputOperator.setStore(transactionalStore);
         outputOperator.setFieldInfos(fieldInfos);
    +    outputOperator.input.setup(tpc);
    --- End diff --
    
    I think the setup of port is after the setup of operator.


> 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)

Reply via email to