Re: Phoenix and NodeJS

Have you looked at paging [1] using Phoenix's row-value constructors together with the LIMIT clause? That might be what you are looking for. [1] http://phoenix.apache.org/paged.html Eli On Mon, May 18, 2015 at 6:46 AM, Isart Montane isart.mont...@gmail.com wrote: Hi, the company I work for

Re: Phoenix and NodeJS

Hi Eli, thanks a lot for your answer. That might be a workaround but I was hoping to get a more generic answer I can apply to the driver/phoenix since that will require me lots of changes to the code. Any clue on why it works with sqline but not trough the node driver? On Mon, May 18, 2015 at

Re: Problems with Phoenix and HBase

Sending to Phoenix user mailing list. Here is the thread: http://search-hadoop.com/m/YGbbu2WzHtZBkq1 On Mon, May 18, 2015 at 7:20 AM, Asfare aman...@hotmail.com wrote: Can someone give some tips? -- View this message in context:

Re: Trying to setup unittests to query phoenix test db but getting UnsupportedOperationException

Thanks! I will look into it. On 05/15/2015 06:24 PM, James Taylor wrote: You'll want to derive from BaseHBaseManagedTimeIT. The BaseConnectionlessQueryTest class is for compile-time only or negative tests as it doesn't spin up any mini cluster. Thanks, James On Fri, May 15, 2015 at 5:41 AM,

Re: Phoenix and NodeJS

I don't have info on what your app does with results from Phoenix. If the app is constructing some sort of object representations from Phoenix results and holding on to them, I would look at what the memory footprint of that is. I know this isn't very helpful but at this point I would try to dig

Re: Phoenix and NodeJS

Hi Isart, That code isn't Phoenix code. This sounds like a Node JS issue. Vaclav has done a lot with Node JS, so he may be able to give you some tips. Thanks, James On Mon, May 18, 2015 at 9:06 AM, Isart Montane isart.mont...@gmail.com wrote: Hi Eli, thanks a lot for your comments. I think you

Problem while upgrading from Phooenix 4.0.0 to 4.3.1

Hello, 1. Currently using phoenix 4.0.0 incubating for both client and server. 2. Upgraded to 4.3.1(most recent) 3. While trying to connect using the client in command line (using ./sqlline.py) the connection could not be success throwing the following error. 1) *Error: ERROR 1013 (42M04): Table

Re: Phoenix and NodeJS

Hi Eli, thanks a lot for your comments. I think you are right. I found the client code that's causing the issue. Do you have an example I can use to patch it? is that the recommended way to access phoenix? I've seen on the web that there's also a query server available, is it worth a try?

Re: Phoenix and NodeJS

Thanks James. That code is from the node driver, I will try to get some advice from it's developer. Thanks, On Mon, May 18, 2015 at 6:34 PM, James Taylor jamestay...@apache.org wrote: Hi Isart, That code isn't Phoenix code. This sounds like a Node JS issue. Vaclav has done a lot with Node

Re: Phoenix and NodeJS

Yeah, so you can see that code creates a String array containing the whole result set. Usually a very bad idea for 400K-row result sets. You want to process results incrementally, probably via paging using row-value constructors and LIMIT. On Mon, May 18, 2015 at 12:00 PM, Isart Montane

Re: Can we create an secondary index for two or more columns?

Thank you Jesse, that really makes sense. 2015-05-18 11:19 GMT+08:00 Jesse Yates jesse.k.ya...@gmail.com: create index my_idx on EXAMPLE (M.C0, M.C1) This will create an index on both columns _at the same time_. This means the row key in the index will be a combination of both columns.