Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Here's a raw scan dump taken after the MutableIndexIT.testCoveredColumns() test:
************ dumping IDX_T000002;hconnection-0x211e75ea ************** \x00a/0:/1487356752097/DeleteFamily/vlen=0/seqid=0 value = x\x00a/0:0:V2/1487356752231/Put/vlen=1/seqid=0 value = 4 x\x00a/0:0:V2/1487356752225/Put/vlen=1/seqid=0 value = 4 x\x00a/0:0:V2/1487356752202/Put/vlen=1/seqid=0 value = 3 x\x00a/0:0:V2/1487356752149/DeleteColumn/vlen=0/seqid=0 value = x\x00a/0:0:V2/1487356752097/Put/vlen=1/seqid=0 value = 1 x\x00a/0:_0/1487356752231/Put/vlen=2/seqid=0 value = _0 x\x00a/0:_0/1487356752225/Put/vlen=2/seqid=0 value = _0 x\x00a/0:_0/1487356752202/Put/vlen=2/seqid=0 value = _0 x\x00a/0:_0/1487356752149/Put/vlen=2/seqid=0 value = _0 x\x00a/0:_0/1487356752097/Put/vlen=2/seqid=0 value = _0 -----------------------------------------------
An optimization would be not to issue the first Put since the value behind it is the same.
Attachments
Issue Links
- relates to
-
PHOENIX-3685 Extra DeleteFamily marker in non tx index table when setting covered column to null
- Resolved