[jira] [Commented] (KUDU-2623) Expose PartialRow's schema in public API

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457304#comment-17457304 ] 

ASF subversion and git services commented on KUDU-2623:
-------------------------------------------------------

Commit 370e58c2fa4169e72dc4857dee5318d5c4d49bda in kudu's branch refs/heads/master from Zoltan Chovan
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=370e58c ]

[client] KUDU-2623 Expose table as public in WriteOp

Making KuduWriteOperation::table() method public to enable identification
of the problematic table when an error happens.

Change-Id: Idbfff6e931304cce7826bc272811155f57a5c4e5
Reviewed-on: http://gerrit.cloudera.org:8080/18075
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <as...@cloudera.com>
Reviewed-by: Attila Bukor <ab...@apache.org>


> Expose PartialRow's schema in public API
> ----------------------------------------
>
>                 Key: KUDU-2623
>                 URL: https://issues.apache.org/jira/browse/KUDU-2623
>             Project: Kudu
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.8.0
>            Reporter: Adar Dembo
>            Assignee: Zoltan Chovan
>            Priority: Minor
>              Labels: newbie
>
> A client session can be used to apply operations belonging to multiple tables. If there are any errors, there's no way currently to figure out which table each error belonged to short of the application keeping track of which primary keys belong to which tables. Seeing as each row error is associated with a PartialRow, a simple way to address this may be to expose PartialRow's schema in the public API.
> This applies to all client bindings.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)