| clear query|facets|time |
Search criteria: .
Results from 11 to 20 from
75 (0.134s).
|
|
|
Loading phrases to help you
refine your search...
|
|
Re: [ANNOUNCE] Phoenix 1.2 is now available - HBase - [mail # user]
|
|
...Hi Anil, No HBase changes were required. We're already leveraging coprocessors in HBase which is a key enabler. The other pieces needed are: - a type system - a means to evaluate an OR...
|
|
|
Author: James Taylor,
2013-05-16, 23:15
|
|
|
[ANNOUNCE] Phoenix 1.2 is now available - HBase - [mail # user]
|
|
...We are pleased to announce the immediate availability of Phoenix 1.2 (https://github.com/forcedotcom/phoenix/wiki/Download). Here are some of the release highlights: * Impr...
|
|
|
Author: James Taylor,
2013-05-16, 19:29
|
|
|
Re: Get all rows that DON'T have certain qualifiers - HBase - [mail # user]
|
|
...Hi Amit, Using Phoenix, the SQL skin over HBase (https://github.com/forcedotcom/phoenix), you'd do this: select * from myTable where value1 is null or value2 is null Regards, Jam...
|
|
|
Author: James Taylor,
2013-05-14, 15:39
|
|
|
Re: [DISCUSS] Namespace Delimiter - HBase - [mail # dev]
|
|
...Sorry, didn't explain the current Phoenix behavior correctly. Phoenix uses "." in table names currently by combining the and together with a "." as the separator. Fo...
|
|
|
Author: James Taylor,
2013-05-08, 19:02
|
|
|
Re: [DISCUSS] Namespace Delimiter - HBase - [mail # dev]
|
|
...Phoenix uses . to reference tables, so allowing a "." in names would make parsing ambiguous. James On 05/07/2013 11:36 PM, Stack wrote:...
|
|
|
Author: James Taylor,
2013-05-08, 06:55
|
|
|
Re: Coprocessors - HBase - [mail # user]
|
|
...Sudarshan, Below are the results that Mujtaba put together. He put together two version of your schema: one with the ATTRIBID as part of the row key and one with it as a key value. He also b...
|
|
|
Author: James Taylor,
2013-05-02, 00:01
|
|
|
Re: Very poor read performance with composite keys in hbase - HBase - [mail # user]
|
|
...Have you had a look at Phoenix (https://github.com/forcedotcom/phoenix)? It'll use all of the parts of your row key and depending on how much data you're returning back to the client, will q...
|
|
|
Author: James Taylor,
2013-04-30, 21:15
|
|
|
Re: Read access pattern - HBase - [mail # user]
|
|
...bq. The downside that I see, is the bucket_number that we have to maintain both at time or reading/writing and update it in case of cluster restructuring. I agree that this...
|
|
|
Author: James Taylor,
2013-04-30, 16:40
|
|
|
Re: HBase and Datawarehouse - HBase - [mail # user]
|
|
...Phoenix will succeed if HBase succeeds. Phoenix just makes it easier to drive HBase to it's maximum capability. IMHO, if HBase is to make further gains in the OLAP space, scans n...
|
|
|
Author: James Taylor,
2013-04-30, 06:28
|
|
|
Re: Coprocessors - HBase - [mail # user]
|
|
...Our performance engineer, Mujtaba Chohan has agreed to put together a benchmark for you. We only have a four node cluster of pretty average boxes, but it should give you an idea....
|
|
|
Author: James Taylor,
2013-04-25, 23:51
|
|
|
|
