You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/19 10:03:00 UTC
[jira] [Updated] (STORM-2712) accept arbitrary number of rows per
tuple in storm-cassandra
[ https://issues.apache.org/jira/browse/STORM-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated STORM-2712:
----------------------------------
Labels: pull-request-available (was: )
> accept arbitrary number of rows per tuple in storm-cassandra
> ------------------------------------------------------------
>
> Key: STORM-2712
> URL: https://issues.apache.org/jira/browse/STORM-2712
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-cassandra
> Affects Versions: 2.0.0, 1.1.1
> Reporter: Yohei Kishimoto
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Current implementation in `TridentResultSetValuesMapper::map` restricts a SELECT query to return one row. In `StateQueryProcessor::finishBatch`, it checks the equality between the result size of `batchRetrieve` and input tuple size. When the number of result rows is less than 1 or greater than 1, it breaks the condition and an exception is thrown.
> We should accept arbitrary number of rows by adjusting List dimensions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)