[
https://issues.apache.org/jira/browse/APEXMALHAR-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127948#comment-15127948
]
ASF GitHub Bot commented on APEXMALHAR-1982:
--------------------------------------------
Github user DT-Priyanka commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/175#discussion_r51542209
--- Diff:
contrib/src/test/java/com/datatorrent/contrib/cassandra/CassandraOperatorTest.java
---
@@ -293,8 +293,8 @@ public void testCassandraInputOperator()
TestInputOperator inputOperator = new TestInputOperator();
inputOperator.setStore(store);
- inputOperator.setTablename(TABLE_NAME_INPUT);
inputOperator.setQuery(query1);
+ inputOperator.setTablename(TABLE_NAME_INPUT);
--- End diff --
Previously, query was dependent on "tableName" variable. As the order of
setting variables was tableName followed by query here the test case always
passed. To simulate situation where platform could set tablename after query
(there is no guarantee in which order variables are set) I did this change.
> CassandraInputOperator query setter fails with null pointer exception
> ---------------------------------------------------------------------
>
> Key: APEXMALHAR-1982
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-1982
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Priyanka Gugale
> Assignee: Priyanka Gugale
>
> Query property setter of operator uses other operator property "table" which
> is not yet set.
> This should be done in setup instead, we can't rely on order in which
> properties are set by platform.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
