[
https://issues.apache.org/jira/browse/KUDU-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355947#comment-17355947
]
ASF subversion and git services commented on KUDU-3267:
-------------------------------------------------------
Commit a5bf0e7130c927d350a57c54213958dcb90d40a8 in kudu's branch
refs/heads/branch-1.15.x from Abhishek Chennaka
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=a5bf0e7 ]
[java] KUDU-3267 Improve logging on writes to non-existent partitions
This patch helps to log a more meaningful error message when a
non-existent range partition is written to by the Kudu Java client.
Due to different behavior of the client in different flush modes,
the existing messages returned by the client are different when
different flush modes are used. Effort has been made to bring
consistency to the error messages returned in all the flush modes
as well.
For example in the default AUTO_FLUSH_BACKGROUND mode
Existing log message snippet:
Not found: ([0x000000018005BDAA4BF52400, 0x000000028005BCC2F4C85400))
New log message snippet (in any FLUSH mode):
Not Found: accessed range partition ([0x80000064, 0x800000C8)) does
not exist in table: TestKuduSession
Thanks to Grant Henke for the help in writing this patch.
Change-Id: Ia24582de6b060e908f5ecbc46e2638b95cd567b3
Reviewed-on: http://gerrit.cloudera.org:8080/17518
Tested-by: Alexey Serbin <aser...@cloudera.com>
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
(cherry picked from commit cae3ec8df5037f560defe5b121f197f27c7065f1)
Reviewed-on: http://gerrit.cloudera.org:8080/17535
Reviewed-by: Bankim Bhavsar <ban...@cloudera.com>
Tested-by: Kudu Jenkins
> Improve error logging when writing to non-existant partition through kudu
> java client
> -------------------------------------------------------------------------------------
>
> Key: KUDU-3267
> URL: https://issues.apache.org/jira/browse/KUDU-3267
> Project: Kudu
> Issue Type: Improvement
> Components: client, java
> Reporter: Abhishek
> Assignee: Abhishek
> Priority: Minor
> Labels: beginner
> Fix For: 1.16
>
>
> When trying to access a non-existing partition, through spark a customer
> encountered the below error message which is not too self explanatory:
> {code:java}
> Caused by: java.lang.RuntimeException: Failed to write 1 rows to Kudu; Sample
> errors: Not found: ([0x000000018005BDAA4BF52400, 0x000000028005BCC2F4C85400))
> at
> org.apache.kudu.spark.kudu.KuduContext$$anonfun$writeRows$1.apply(KuduContext.scala:366)
> at
> org.apache.kudu.spark.kudu.KuduContext$$anonfun$writeRows$1.apply(KuduContext.scala:350){code}
> Filing this Jira to make the error message more meaningful
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
