[
https://issues.apache.org/jira/browse/HBASE-28268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898206#comment-17898206
]
Viraj Jasani commented on HBASE-28268:
--------------------------------------
Thank you for your contribution [~raghavendra.b]!
If you also wish to have the change backported to 2.x branches, please create
backport PR against branch-2 and I can take it further from there.
> Provide option to skip wal while using TableOutputFormat
> --------------------------------------------------------
>
> Key: HBASE-28268
> URL: https://issues.apache.org/jira/browse/HBASE-28268
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Ujjawal Kumar
> Assignee: Raghavendra B
> Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> If we have replication setup between clusters A <-> B, during production
> incidents where HFiles get corrupted (e.g. via hdfs missing blocks) on
> cluster A, we can use CopyTable job to copy the data from B
> In those cases considering the data is being copied from B to A via
> CopyTable, it doesn't make sense to write to WALs on A using
> TableOutputFormat (since the mutations being copied already exist on B).
> We can add a config to customise durability
> ([https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Durability.java])
> within TableOutputFormat so that an operator can use it to skip WAL writes
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
