[
https://issues.apache.org/jira/browse/HBASE-15425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187228#comment-15187228
]
Ted Yu edited comment on HBASE-15425 at 3/9/16 3:22 PM:
--------------------------------------------------------
lgtm
{code}
5300 boolean success = false;
{code}
success gives people impression that the outcome is a success.
Please rename it to isSuccessful.
I guess it would be difficult to write a test for this scenario.
was (Author: [email protected]):
lgtm
{code}
5300 boolean success = false;
{code}
success gives people impression that the outcome is a success.
Please rename it to succeeded.
I guess it would be difficult to write a test for this scenario.
> Failing to write bulk load event marker in the WAL is ignored
> -------------------------------------------------------------
>
> Key: HBASE-15425
> URL: https://issues.apache.org/jira/browse/HBASE-15425
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Ashish Singhi
> Assignee: Ashish Singhi
> Attachments: HBASE-15425.patch
>
>
> During LoadIncrementalHFiles process if we fail to write the bulk load event
> marker in the WAL, it is ignored. So this will lead to data mismatch issue in
> source and peer cluster in case of bulk loaded data replication scenario.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
