[
https://issues.apache.org/jira/browse/STORM-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-2712.
---------------------------------
Resolution: Fixed
Assignee: Yohei Kishimoto
Fix Version/s: 1.1.2
1.2.0
2.0.0
Thanks [~morokosi], I merged into master, 1.x, 1.1.x branches.
Keep up the good work.
> 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
> Assignee: Yohei Kishimoto
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.0.0, 1.2.0, 1.1.2
>
> Time Spent: 1h
> 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)
