[
https://issues.apache.org/jira/browse/HBASE-23788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051799#comment-17051799
]
Hudson commented on HBASE-23788:
--------------------------------
Results for branch master
[build #1652 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1652/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1652//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1652//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1652//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> ROW_INDEX_V1 encoder should consider the secondary index size with the
> encoded data size tracking
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-23788
> URL: https://issues.apache.org/jira/browse/HBASE-23788
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anoop Sam John
> Assignee: Abhinaba Sarkar
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Copied from parent issue comments
> "In case of Row Index this tracking is not accounting the row offsets index
> being written. Because on the go these are kept in memory only and written at
> the end of block write. This end block decision was based on size check only
> which did NOT include this offsets index."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
