You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2019/06/15 18:58:00 UTC
[jira] [Updated] (KUDU-2737) Allow KuduContext row errors to be
handled
[ https://issues.apache.org/jira/browse/KUDU-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-2737:
------------------------------
Labels: usability (was: )
> Allow KuduContext row errors to be handled
> ------------------------------------------
>
> Key: KUDU-2737
> URL: https://issues.apache.org/jira/browse/KUDU-2737
> Project: Kudu
> Issue Type: Improvement
> Components: spark
> Affects Versions: 1.9.0
> Reporter: Grant Henke
> Priority: Major
> Labels: usability
>
> Currently when writing to Kudu via Spark the writeRows Api detects all row errors and throws a RuntimeException with some of the sample errors included in the string:
> https://github.com/apache/kudu/blob/master/java/kudu-spark/src/main/scala/org/apache/kudu/spark/kudu/KuduContext.scala#L344
> We should optionally return these row errors and allow users to handle them, or potentially take and error handler function to allow custom error handling logic to be passed through.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)