[
https://issues.apache.org/jira/browse/HBASE-12303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-12303:
----------------------------------
Description:
Currently we seek to the next column when we encounter a family delete marker.
I think we safely seek the current store to next row.
We ran into a scenario with very slow scans after a lot of rows have been
deleted with family delete markers. Some profiling revealed that we seek for
once for each row and column.
This won't make this go away entirely, but at least we can seek once per row
rather than once per column.
was:
Currently we seek to the next column when we encounter a family delete marker.
I think we safely seek the current store to next row.
> Seek to next row after family delete markers
> --------------------------------------------
>
> Key: HBASE-12303
> URL: https://issues.apache.org/jira/browse/HBASE-12303
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Attachments: 12303.txt
>
>
> Currently we seek to the next column when we encounter a family delete marker.
> I think we safely seek the current store to next row.
> We ran into a scenario with very slow scans after a lot of rows have been
> deleted with family delete markers. Some profiling revealed that we seek for
> once for each row and column.
> This won't make this go away entirely, but at least we can seek once per row
> rather than once per column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
