[
https://issues.apache.org/jira/browse/HBASE-30100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18075493#comment-18075493
]
Hudson commented on HBASE-30100:
--------------------------------
Results for branch master
[build #1440 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1440/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1440/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1440/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> Fix misleading Javadoc for Table.batch about null in results array
> ------------------------------------------------------------------
>
> Key: HBASE-30100
> URL: https://issues.apache.org/jira/browse/HBASE-30100
> Project: HBase
> Issue Type: Improvement
> Components: Client, documentation
> Reporter: Junegunn Choi
> Assignee: Junegunn Choi
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1
>
>
> The Javadoc for {{Table.batch(List<? extends Row>, Object[])}} states:
> {quote}
> A null in the result array means that the call for that action failed, even
> after retries.
> {quote}
> This has been wrong since HBASE-6295 (0.96.0). On per-action failure, the
> current implementation stores the {{Throwable}} in the slot, not {{null}}. A
> caller checking only for {{null}} will miss every operational failure.
> The "even after retries" wording is also wrong for the only case {{null}}
> still appears: synchronous input validation in {{RawAsyncTableImpl.batch}}
> (e.g., empty {{Put}} or over-sized cell) throws {{IllegalArgumentException}}
> before any RPC, leaving all slots {{null}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
