You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2016/02/27 00:08:18 UTC
[jira] [Resolved] (KUDU-1343) [java client] Scan sequence id is
never reset between tablets
[ https://issues.apache.org/jira/browse/KUDU-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans resolved KUDU-1343.
--------------------------------------
Resolution: Fixed
Fix Version/s: 0.8.0
Fixed in 0548324a855c1fe8dff8c224b010a45fcbb6eabd.
> [java client] Scan sequence id is never reset between tablets
> -------------------------------------------------------------
>
> Key: KUDU-1343
> URL: https://issues.apache.org/jira/browse/KUDU-1343
> Project: Kudu
> Issue Type: Bug
> Components: client
> Affects Versions: 0.5.0
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.8.0
>
>
> AsyncKuduScanner.sequenceId is never reset between tablets, so any multi-batch multi-tablet scan will fail with:
> {noformat}
> org.kududb.client.TabletServerErrorException: Server[196dfd5d5e1040dd9963e9b26820078e] INVALID_ARGUMENT[code 4]: Invalid call sequence ID in scan request
> at org.kududb.client.TabletClient.dispatchTSErrorOrReturnException(TabletClient.java:462)
> {noformat}
> It's an extremely easy fix, but we need more unit tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)