Re: Re: How to use Paged Queries?

For an example of this flow, see QueryMoreIT: https://github.com/apache/phoenix/blob/master/phoenix-core/src/it/java/org/apache/phoenix/end2end/QueryMoreIT.java On Fri, Jul 25, 2014 at 12:45 PM, James Taylor wrote: > Yes, we have code at Salesforce that does exactly that. You really > only need t

Re: Re: How to use Paged Queries?

Yes, we have code at Salesforce that does exactly that. You really only need to cache 1) the row number ordinal and 2) the PK column values (and only if there's an ORDER BY in your query, as otherwise you can page through the results through the paging mechanism described in this thread). Then you

Re: query client performance

Yes, we're planning on cutting an RC early next week. Thanks, James On Fri, Jul 25, 2014 at 12:36 PM, Abe Weinograd wrote: > Thanks James. That's very helpful. > > 4.1 is being released soon? > > Thanks, > Abe > > > On Fri, Jul 25, 2014 at 3:34 PM, James Taylor > wrote: >> >> Hi Abe, >> FWIW, t

Re: query client performance

Thanks James. That's very helpful. 4.1 is being released soon? Thanks, Abe On Fri, Jul 25, 2014 at 3:34 PM, James Taylor wrote: > Hi Abe, > FWIW, there's an improvement in place > (https://issues.apache.org/jira/browse/PHOENIX-539) for our upcoming > next release that doesn't cause the first

Re: query client performance

Hi Abe, FWIW, there's an improvement in place (https://issues.apache.org/jira/browse/PHOENIX-539) for our upcoming next release that doesn't cause the first rext row call to pull over everything. Instead, it is done in chunks. As far as what you can do now, I'd recommend putting a LIMIT clause on

Re: Location protocol error in Pig using Phoenix 3.0

Hi Steve, Specifying column names explicitly during LOAD and STORE is present from v 3.1.0 and not in the phoenix-3.0.0-incubating . You can try building the artifacts following the steps mentioned at http://phoenix.

Re: Location protocol error in Pig using Phoenix 3.0

Hi Martin, I noticed phoenix-3.0.0-incubating-client.jar doesn't have the feature of passing explicit column names during STORE. I did a download from http://phoenix.apache.org/download.html and checked it. So please try, STORE LoadProducts INTO 'hbase://SCHEMA.TABLE' using org.apache.pho

Re: Creating tables with columnfamily

Hello Rahul You will need to create at least one column, a default columnfamily will be created if you do not specify one. You will need to create at least one columnname per columnfamily you would like to have if you want specific columnfamilies in your table. At a later you can write or read fro

Re: Re: How to use Paged Queries?

Hey james Looking at your reply got me thinking. Could pagination of very large result sets be set up in a temporary hbase table. Say your query for a large dataset with a complex query, the result could be "cached" in a temp table and served paginated where rowkeys would be postions. This way you

Re: query client performance

Hello Abe You are right currently the pheonix client is the final step hence some processing can happen there. One way is to actually put the client on the cluster to avoid long anf suboptimal networks. Maybe a service standing in the cluster for you in front of the client to do last stepds and ev

Re: Error connecting through SQuirrel

Thanks Cosmin and Gabriel. Best Regards, Sid On Fri, Jul 25, 2014 at 5:55 AM, Gabriel Reid wrote: > Hi Sid, > > The location of the jar file looks correct. However, there seems to be > an issue with the build of hadoop2 phoenix-client jar -- the > hbase-default.xml in that jar refers to hadoop

Re: Location protocol error in Pig using Phoenix 3.0

You might be using a feature of PhoenixHBaseStorage that I am not familiar with. When I use store to Phoenix, my "into" value is simply this: … into 'hbase://MY_TABLE_NAME' … If one can specify specific column families and column names, I'd like to learn more about that myself. I saw no mention

Location protocol error in Pig using Phoenix 3.0

I am getting the following error when issuing a Store command in Pig: Caused by: java.io.IOException: Location must use the hbase protocol, hbase://tableName[/columnList]. Supplied location=file:/tmp/temp-172455017/tmp1219147161 The code is very simple, loading from a file and storing to a Phoe

Re: Error connecting through SQuirrel

Hi Sid, The location of the jar file looks correct. However, there seems to be an issue with the build of hadoop2 phoenix-client jar -- the hbase-default.xml in that jar refers to hadoop1 for some reason. I'm not sure how that would have happened, but I'll follow it up on the dev list. For now, I

Re: Error connecting through SQuirrel

Hi Sid, I had a similar problem while using DBVisualizer. One thing that you can do to quickly solve your problem is to clone the repo and build the client yourself. The fix is in the repo, but is not part of the official downloads yet. Alternatively, you can use my precompiled jar https://dl.dr