0, 2016 at 1:12 PM
To: "user@phoenix.apache.org<mailto:user@phoenix.apache.org>"
mailto:user@phoenix.apache.org>>
Subject: Re: Problems with Phoenix bulk loader when using row_timestamp feature
0: jdbc:phoenix:localhost
>
> *| * SERVER AGGREGATE INTO SINGLE ROW* |*
>
> *+--+*
>
> 4 rows selected (0.071 seconds)
>
> From: Samarth Jain
> Reply-To: "user@phoenix.apache.org"
> Date: Wednesday, August 10, 2016 at 12:05 AM
> To: "user@phoenix.apa
rg<mailto:user@phoenix.apache.org>"
mailto:user@phoenix.apache.org>>
Date: Wednesday, August 10, 2016 at 12:05 AM
To: "user@phoenix.apache.org<mailto:user@phoenix.apache.org>"
mailto:user@phoenix.apache.org>>
Subject: Re: Problems with Phoenix bulk loader whe
Ryan,
Can you tell us what the explain plan says for the select count(*) query.
- Samarth
On Tue, Aug 9, 2016 at 12:58 PM, Ryan Templeton
wrote:
> I am working on a project that will be consuming sensor data. The “fact”
> table is defined as:
>
> CREATE TABLE historian.data (
> assetid unsign
I am working on a project that will be consuming sensor data. The “fact” table
is defined as:
CREATE TABLE historian.data (
assetid unsigned_int not null,
metricid unsigned_int not null,
ts timestamp not null,
val double
CONSTRAINT pk PRIMARY KEY (assetid, metricid, tsp))
IMMUTABLE_ROWS=true;
I
