Re: querying time for Apache Phoenix

2016-07-29 Thread Maryann Xue
Hi James, I have filed a JIRA https://issues.apache.org/jira/browse/PHOENIX-3129 for using global index for such queries without hint. Feel free to watch and comment on this issue. Thanks, Maryann On Wed, Jul 27, 2016 at 12:29 PM, James Taylor wrote: > On Wed, Jul 27,

Re: querying time for Apache Phoenix

2016-07-27 Thread James Taylor
On Wed, Jul 27, 2016 at 8:07 AM, Heather, James (ELS) < james.heat...@elsevier.com> wrote: > - select * from documents where profile_id = ? (multiple rows returned, > doing a full scan) --- 5 sec > > See https://phoenix.apache.org/secondary_indexing.html#Index_Usage for > when an

Re: querying time for Apache Phoenix

2016-07-27 Thread James Taylor
I believe what you're saying is correct, James. The SMALL hint is calling scan.setSmall(true) on the scans for your query. There's some documentation on this here: https://issues.apache.org/jira/browse/HBASE-9488, but I'm having a hard time finding other documentation. Small scans prevent as many

Re: querying time for Apache Phoenix

2016-07-27 Thread Heather, James (ELS)
On Tue, 2016-07-26 at 08:39 -0700, James Taylor wrote: - if you're querying for a single row, use the serial and small hints like this: /*+ SERIAL SMALL */ Quoting from the language reference: Generally, if the query is a point lookup or returns data that is likely in a single data block (64

Re: querying time for Apache Phoenix

2016-07-27 Thread Heather, James (ELS)
- select * from documents where profile_id = ? (multiple rows returned, doing a full scan) --- 5 sec See https://phoenix.apache.org/secondary_indexing.html#Index_Usage for when an index is used/not used, but by default a global index won't be used if not all columns are contained

Re: querying time for Apache Phoenix

2016-07-26 Thread James Taylor
tay...@apache.org> > *Sent:* Tuesday, July 26, 2016 4:39:46 PM > *To:* user > *Subject:* Re: querying time for Apache Phoenix > > Hi Irina, > > I'd recommend trying the following: > - set the UPDATE_CACHE_FREQUENCY=6 property when you create your table > and index to

Re: querying time for Apache Phoenix

2016-07-26 Thread Placinta, Irina (ELS)
rder by added desc limit 1 (index on added) --- 5.5 sec Are there any timelines for the next release? Thanks, Irina From: James Taylor <jamestay...@apache.org> Sent: Tuesday, July 26, 2016 4:39:46 PM To: user Subject: Re: querying time for Apache Phoenix

Re: querying time for Apache Phoenix

2016-07-26 Thread James Taylor
Hi Irina, I'd recommend trying the following: - set the UPDATE_CACHE_FREQUENCY=6 property when you create your table and index to prevent extra RPCs at query time. - if you're querying for a single row, use the serial and small hints like this: /*+ SERIAL SMALL */ - though not strictly