[
https://issues.apache.org/jira/browse/DRILL-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019913#comment-16019913
]
ASF GitHub Bot commented on DRILL-5229:
---------------------------------------
Github user sudheeshkatkam commented on the issue:
https://github.com/apache/drill/pull/828
@eskabetxe thank you for the pull request!
How did you test the patch? I have not looked into the Kudu plugin before,
but I noticed that the unit tests are [ignored by
default](https://github.com/apache/drill/commit/aa39c66d92ec03c90f3715df7cc4fde49d76a334).
> Upgrade kudu client to org.apache.kudu:kudu-client:1.2.0
> ---------------------------------------------------------
>
> Key: DRILL-5229
> URL: https://issues.apache.org/jira/browse/DRILL-5229
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Other
> Affects Versions: 1.8.0
> Reporter: Rahul Raj
> Fix For: 2.0.0
>
>
> Getting an error -" out-of-order key" for a query select v,count(k) from
> kudu.test group by v where k is the primary key. This happens only when the
> aggregation is done on primary key. Should drill move to the latest kudu
> client to investigate this further?
> Current drill kudu connector uses org.kududb:kudu-client:0.6.0 from
> cloudera repository, where the latest released library
> org.apache.kudu:kudu-client:1.2.0 is hosted on maven central. There are a
> few breaking changes with the new library:
> 1. TIMESTAMP renamed to UNIXTIME_MICROS
> 2. In KuduRecordReader#setup -
> KuduScannerBuilder#lowerBoundPartitionKeyRaw renamed to lowerBoundRaw
> andKuduScannerBuilder#exclusiveUpperBoundPartitionKeyRaw renamed
> exclusiveUpperBoundRaw. Both methods are deprecated.
> 3. In KuduRecordWriterImpl#updateSchema - client.createTable(name,
> kuduSchema) requires CreateTableOperatios as the third argument
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
