You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Anoop Sam John (Jira)" <ji...@apache.org> on 2020/02/04 04:50:00 UTC

[jira] [Updated] (HBASE-23788) ROW_INDEX_V1 encoder should consider the secondary index size with the encoded data size tracking

     [ https://issues.apache.org/jira/browse/HBASE-23788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anoop Sam John updated HBASE-23788:
-----------------------------------
    Description: 
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."

> 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
>            Priority: Major
>
> 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)