[HBASE-28268] Provide option to skip wal while using TableOutputFormat

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.7.0, 3.0.0-beta-2, 2.5.11, 2.6.2
• Component/s: mapreduce
• Labels: newbie pull-request-available
• Hadoop Flags: Reviewed
• Assignee: Raghavendra B
• Reporter: Ujjawal Kumar
• Created: 18/Dec/23 15:37
• Updated: 15/Nov/24 21:34
• Resolved: 14/Nov/24 09:25

Description

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

Issue Links

• links to: GitHub Pull Request #6436
• links to: GitHub Pull Request #6472