[
https://issues.apache.org/jira/browse/APEXMALHAR-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279013#comment-15279013
]
ASF GitHub Bot commented on APEXMALHAR-1988:
--------------------------------------------
Github user DT-Priyanka commented on a diff in the pull request:
https://github.com/apache/incubator-apex-malhar/pull/186#discussion_r62758000
--- Diff:
contrib/src/main/java/com/datatorrent/contrib/cassandra/AbstractCassandraInputOperator.java
---
@@ -112,8 +115,15 @@ public void emitTuples()
String query = queryToRetrieveData();
logger.debug("select statement: {}", query);
+ SimpleStatement stmt = new SimpleStatement(query);
+ stmt.setFetchSize(fetchSize);
--- End diff --
The query is fetched each time "queryToRetrieveData()". In current
implementation query doesn't change much. But anyone can implement that
function to change query parameters in each run. In that case we need to create
statement using the current query. This is abstract class so trying to make
sure it helps in all known use cases.
> CassandraInputOperator fetches less number of records inconsistenly
> -------------------------------------------------------------------
>
> Key: APEXMALHAR-1988
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-1988
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Priyanka Gugale
> Assignee: Priyanka Gugale
>
> CassandraInputOperator fetches less number of records than available in
> table. Also number of records returned in each runs are different.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)