Re: ROW_NUMBER() in Phoenix

Thanks for the Suggestion, James. I'll try that. On Wed, Apr 12, 2017 at 7:39 AM, James Taylor wrote: > Hi Bernard, > No support for ROW_NUMBER() in Phoenix. The closest you could get would be > to create a unique sequence on the fly (using a caching size of > Long.MAX_VALUE to prevent any RPCs)

Re: ROW_NUMBER() in Phoenix

Hi Bernard, No support for ROW_NUMBER() in Phoenix. The closest you could get would be to create a unique sequence on the fly (using a caching size of Long.MAX_VALUE to prevent any RPCs) and then use a NEXT VALUE FOR to generate the row number. Thanks, James On Tue, Apr 11, 2017 at 3:57 PM, Bern

Re: Phoenix Query Server query logging

FWIW, we use our metric framework[1] to collect that information, outputting one log line per statement or query and then Splunk to look at it. [1] http://phoenix.apache.org/metrics.html On Tue, Apr 11, 2017 at 3:24 PM Michael Young wrote: > Yes, the tracing webapp is working, at least in our d

ROW_NUMBER() in Phoenix

Hi, Is there something similar to ROW_NUMBER() in Phoenix? Or any alternatives to displaying the row number like this: row_number,name,purchases 1,John, 2,Joseph,999 3,Jordan,99 Thanks!

Re: Phoenix Query Server query logging

Yes, the tracing webapp is working, at least in our distro HDP 2.5 release. However, it seemed to negatively impact our performance and created a large volume of trace data which was somewhat overwhelming. We could not get simple SELECT query logging and query time info from the trace logs it pr

Re: Problem connecting JDBC client to a secure cluster

Hi all, I have been able to track down the origin of the problem and it is related to the hbase-site.xml not being loaded correctly by the application server. Seeing the instructions given by Anil in this JIRA: https://issues.apache.org/jira/browse/PHOENIX-19 it has been easy to reproduce it j

Problem connecting JDBC client to a secure cluster

Hi everybody !, We have a CDH 5.8 kerberized cluster in which we have installed Apache Phoenix 4.7 (via CLABS parcel). Everything works as expected. The only problem we are facing is when trying to connect a WeblogicServer to Apache Phoenix via the fat client. needed files are added in classpath: