[HBASE-17488] WALEdit should be lazily instantiated

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 1.4.0, 2.0.0
• Hadoop Flags: Reviewed

Release Note

prevent creating unused objects in the WALEdit's construction.
+If the cp#preBatchMutate returns true, the WALEdit is useless. So we should create the WALEdit after step 2.
+The cells came from cp should be counted because they are added into the WALEdit . The use case is the local index of phoenix
+If the mutation contains the SKIP_WAL property, its cells aren't added into the WALEdit. So these cells shouldn't be counted.

• Assignee: Chia-Ping Tsai
• Reporter: Chia-Ping Tsai
• Created: 19/Jan/17 03:30
• Updated: 20/Jan/17 23:32
• Resolved: 20/Jan/17 17:40

Description

Some trivial improvement.

1. create the WALEdit on step 3 instead of step 2
2. count the cells from coprocessor
3. don’t count the mutations which contain the Durability.SKIP_WAL property

Issue Links

• relates to: HBASE-15204 Try to estimate the cell count for adding into WALEdit