> The 1-day aggregate query you are running should work, you might have to
> increase the client thread pool and queue size.
> See
> http://mail-archives.apache.org/mod_mbox/phoenix-user/201607.mbox/%3c577d338d.2080...@gmail.com%3E
>
> On Tue, Nov 20, 2018 at 9:26 PM Monil Gandhi
gregated data in a separate table that you
> can populate using an UPSERT SELECT.
> I'm not sure why the explain plan you attached has a CLIENT MERGE SORT,
> since you don't have an order by.
>
> On Fri, Nov 16, 2018 at 9:44 AM Monil Gandhi wrote:
>
>> Here it is
v 15, 2018 at 5:23 PM Geoffrey Jacoby
wrote:
> Monil,
>
> Could you please post the results of an EXPLAIN plan of your query? For
> directions how to do this please see
> http://phoenix.apache.org/explainplan.html
>
> Geoffrey Jacoby
>
> On Thu, Nov 15, 2018 at 5:
Hello,
Currently we have hourly data in our phoenix table. However, the schema was
designed to perform well for daily data. Increasing the number of rows by
24X has lead to degradation of our service over time.
Our current schema is as follows
CREATE TABLE IF NOT EXISTS T1 (sid BIGINT NOT NULL, da
Josh Elser wrote:
> The thick client talks directly to HBase. The thin client talks to PQS.
> You cannot mix-and-match.
>
> Glad to hear you got it working. How can the documentation be improved
> to make this more clear?
>
> On 10/23/18 9:11 PM, Monil Gandhi wrote:
> &
Hello
Update. I was able to figure this out. Thanks for the initial pointer :)
On Mon, Oct 22, 2018 at 10:54 PM Monil Gandhi wrote:
> Hello,
> Thanks for the earlier reply.
> I am a little confused with documentation and the response from Josh. This
> may be my limited knowledge
particular query, I am trying to see how many rows are being scanned
and across how many region servers. If there is an easier way, please let
me know
On Thu, Oct 18, 2018 at 7:00 PM Monil Gandhi wrote:
> Okay. Will take a look. Thanks
> On Wed, Oct 17, 2018 at 8:28 AM Josh Elser wrote:
&g
uot;thick" JDBC driver is what's running inside of the Phoenix
> Query Server, just not in your local JVM. As such, you need to look at
> PQS for metrics.
>
> You probably want to look at what was done in
> https://issues.apache.org/jira/browse/PHOENIX-3655.
>
> On 1
Hello,
I am trying to collect some metrics on certain queries. Here is the code
that I have
Properties props = new Properties();
props.setProperty(QueryServices.COLLECT_REQUEST_LEVEL_METRICS, "true");
props.setProperty("phoenix.trace.frequency", "always");
try (Connection conn = DriverManager.get
