:
Gesendet: 20:42 Mittwoch, 22.August 2012
Betreff: Re: How to query by rowKey-infix
Hi Christian,
I had the similar requirements as yours. So, till now i have used
timestamps for filtering the data and I would say the performance is
satisfactory. Here are the results of timestamp based
...@gmail.com
An: user@hbase.apache.org; Christian Schäfer syrious3...@yahoo.de
CC:
Gesendet: 20:42 Mittwoch, 22.August 2012
Betreff: Re: How to query by rowKey-infix
Hi Christian,
I had the similar requirements as yours. So, till now i have used
timestamps for filtering the data and I would say
: 22:18 Donnerstag, 9.August 2012
Betreff: Re: How to query by rowKey-infix
jfyi: documented FuzzyRowFilter usage here: http://bit.ly/OXVdbg. Will
add documentation to HBase book very soon [1]
Alex Baranau
--
Sematext :: http://sematext.com/ :: Hadoop - HBase - ElasticSearch - Solr
[1
there to illustrate an
comparable situation.
Thanks,
Chris
- Ursprüngliche Message -
Von: Michael Segel michael_se...@hotmail.com
An: user@hbase.apache.org; Christian Schäfer syrious3...@yahoo.de
CC:
Gesendet: 14:21 Freitag, 3.August 2012
Betreff: Re: How to query by rowKey-infix
Hi
that
are applied for efficient time-related scans (except coprocessors full table
scans).
- Ursprüngliche Message -
Von: Christian Schäfer syrious3...@yahoo.de
An: user@hbase.apache.org user@hbase.apache.org
CC:
Gesendet: 11:23 Freitag, 3.August 2012
Betreff: Re: How to query by rowKey-infix
...@yahoo.de
Gesendet: 0:57 Freitag, 3.August 2012
Betreff: Re: How to query by rowKey-infix
Hi Christian!
If to put off secondary indexes and assume you are going with heavy scans,
you can try two following things to make it much faster. If this is appropriate
to your situation, of course.
1
subset to avoid getting the hbase schema indexing (by
coprocessors) too complicated.
regards
Chris
- Ursprüngliche Message -
Von: Matt Corgan mcor...@hotpads.com
An: user@hbase.apache.org
CC:
Gesendet: 3:29 Freitag, 3.August 2012
Betreff: Re: How to query by rowKey-infix
Yeah - just
.August 2012
Betreff: Re: How to query by rowKey-infix
Actually w coprocessors you can create a secondary index in short order.
Then your cost is going to be 2 fetches. Trying to do a partial table scan
will be more expensive.
On Jul 31, 2012, at 12:41 PM, Matt Corgan mcor...@hotpads.com wrote
it helping me to get a bit into it.
And yes that helped :)
regards
Chris
Von: Alex Baranau alex.barano...@gmail.com
An: user@hbase.apache.org; Christian Schäfer syrious3...@yahoo.de
Gesendet: 0:57 Freitag, 3.August 2012
Betreff: Re: How to query by rowKey-infix
CC:
Gesendet: 13:52 Mittwoch, 1.August 2012
Betreff: Re: How to query by rowKey-infix
Actually w coprocessors you can create a secondary index in short order.
Then your cost is going to be 2 fetches. Trying to do a partial table scan will
be more expensive.
On Jul 31, 2012, at 12:41 PM, Matt
@hbase.apache.org
CC:
Gesendet: 13:52 Mittwoch, 1.August 2012
Betreff: Re: How to query by rowKey-infix
Actually w coprocessors you can create a secondary index in short order.
Then your cost is going to be 2 fetches. Trying to do a partial table scan will
be more expensive.
On Jul 31, 2012, at 12:41
, 1.August 2012
Betreff: Re: How to query by rowKey-infix
Actually w coprocessors you can create a secondary index in short order.
Then your cost is going to be 2 fetches. Trying to do a partial table scan
will be more expensive.
On Jul 31, 2012, at 12:41 PM, Matt Corgan mcor...@hotpads.com
...@hotmail.com
An: user@hbase.apache.org
CC:
Gesendet: 13:52 Mittwoch, 1.August 2012
Betreff: Re: How to query by rowKey-infix
Actually w coprocessors you can create a secondary index in short
order.
Then your cost is going to be 2 fetches. Trying to do a partial table
scan
to deployment)
regards
Chris
- Ursprüngliche Message -
Von: Michael Segel michael_se...@hotmail.com
An: user@hbase.apache.org
CC:
Gesendet: 13:52 Mittwoch, 1.August 2012
Betreff: Re: How to query by rowKey-infix
Actually w coprocessors you can
Message -
Von: Matt Corgan mcor...@hotpads.com
An: user@hbase.apache.org
CC: Christian Schäfer syrious3...@yahoo.de
Gesendet: 19:41 Dienstag, 31.Juli 2012
Betreff: Re: How to query by rowKey-infix
When deciding between a table scan vs secondary index, you should try to
estimate what percent
Actually w coprocessors you can create a secondary index in short order.
Then your cost is going to be 2 fetches. Trying to do a partial table scan will
be more expensive.
On Jul 31, 2012, at 12:41 PM, Matt Corgan mcor...@hotpads.com wrote:
When deciding between a table scan vs secondary
Hello there,
I designed a row key for queries that need best performance (~100 ms) which
looks like this:
userId-date-sessionId
These queries(scans) are always based on a userId and sometimes additionally on
a date, too.
That's no problem with the key above.
However, another kind of queries
Hi Chris:
I'm thinking about building a secondary index for primary key lookup, then
query using the primary keys in parallel.
I'm interested to see if there is other option too.
Best Regards,
Jerry
On Tue, Jul 31, 2012 at 11:27 AM, Christian Schäfer syrious3...@yahoo.dewrote:
Hello there,
When deciding between a table scan vs secondary index, you should try to
estimate what percent of the underlying data blocks will be used in the
query. By default, each block is 64KB.
If each user's data is small and you are fitting multiple users per block,
then you're going to need all the
19 matches
Mail list logo
