[ 
https://issues.apache.org/jira/browse/HBASE-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562430#comment-14562430
 ] 

Hudson commented on HBASE-13393:
--------------------------------

FAILURE: Integrated in HBase-TRUNK #6519 (See 
[https://builds.apache.org/job/HBase-TRUNK/6519/])
HBASE-13393 - Optimize memstore flushing to avoid writing tag information 
(ramkrishna: rev eeb11b53279268806cf986d6389b20b539829c14)
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/security/visibility/TestVisibilityLabels.java
* 
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/codec/KeyValueCodec.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultMemStore.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFlusher.java
* hbase-common/src/test/java/org/apache/hadoop/hbase/TestKeyValue.java
* 
hbase-common/src/main/java/org/apache/hadoop/hbase/codec/KeyValueCodecWithTags.java
* hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueUtil.java
* 
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreSnapshot.java


> Optimize memstore flushing to avoid writing tag information to hfiles when no 
> tags are present.
> -----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-13393
>                 URL: https://issues.apache.org/jira/browse/HBASE-13393
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 2.0.0, 1.2.0
>
>         Attachments: HBASE-13393.patch, HBASE-13393_1.patch, 
> HBASE-13393_2.patch, HBASE-13393_3.patch, HBASE-13393_addendum_trunk.patch, 
> HBase-13393_branch-1.patch
>
>
> We used to specify 'no tags' by choosing to write files that were version 2.  
> After parent goes in, make it so can ask a v3 file not to write tags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to