hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Xiang Hua <bea...@gmail.com>
Subject Re: Performance of scan setTimeRange VS manually doing it
Date Thu, 13 Sep 2012 04:45:22 GMT
   do you have script in python for rack awareness configuration?



On Thu, Sep 13, 2012 at 5:52 AM, Tom Brown <tombrown52@gmail.com> wrote:

> When I query HBase, I always include a time range. This has not been a
> problem when querying recent data, but it seems to be an issue when I
> query older data (a few hours old). All of my row keys include the
> timestamp as part of the key (this value is the same as the HBase
> timestamp for the row).  I recently tried an experiment where I
> manually re-seek to the possible row (based on the timestamp as part
> of the row key) instead of using "setTimeRange" on my scan object and
> was amazed to see that there was no degradation for older data.
> Can someone postulate a theory as to why this might be happening? I'm
> happy to provide extra data if it will help you theorize...
> Is there a downside to stopping using "setTimeRange"?
> --Tom

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message