[
https://issues.apache.org/jira/browse/HBASE-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394807#comment-14394807
]
ramkrishna.s.vasudevan commented on HBASE-13370:
------------------------------------------------
Currently PE tool does addColumn and it adds the only Column family and the
qualifier explicitly. This makes the Explicit ColumnTracker to be used. It
will internally make the store scanner to seek before deciding there is no
additional columns for that row. StoreScanner.seekAsDirection(). This patch
would avoid addColumns so internally this seek would be reduced. You can see a
minor change in the profiler as to how many different APIs call the blockSeek
now.
> PE tool could give option for using Explicit Column Tracker which leads to
> seeks
> --------------------------------------------------------------------------------
>
> Key: HBASE-13370
> URL: https://issues.apache.org/jira/browse/HBASE-13370
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 1.0.0, 1.0.1
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Attachments: HBASE-13370.patch, HBASE-13370_1.patch,
> HBASE-13370_1.patch
>
>
> Currently in PE tool all the scans and gets adds explicitly the columns to be
> scanned. The tool by default adds only one Qualifier. Doing this addColumns
> leads to Explicit Column Tracker which does seeks frequently. If we want to
> know a simple scan performance as a basic scenario then we should have the
> option to add this columns explicitly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
