You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by James Taylor <ja...@apache.org> on 2015/11/08 03:53:34 UTC
blog describing new time-series data optimization
If you have time-series data for which you'd like to improve query
performance, take a look at this[1] blog written by Samarth Jain on a new
feature in our 4.6 release:
https://blogs.apache.org/phoenix/entry/new_optimization_for_time_series
Enjoy!
James
Re: blog describing new time-series data optimization
Posted by James Taylor <ja...@apache.org>.
bq. Would be cool to see if we could roll in some of the stuff talked about
at the last meetup too :)
+1. We're always open for patches, :-) though many of those changes would
be rolled in at the HBase level, I believe (assuming we're talking about
Vladimir's preso[1]). However, the auto-rollup stuff could be done through
materialized views in Calcite. Would be great if once our Phoenix/Calcite
integration is complete, if we could leverage Apache Kylin (which also uses
Calcite) to get that capability.
[1] http://files.meetup.com/1350427/TimeSeriesHBase.pptx
On Sun, Nov 8, 2015 at 11:52 AM, Jesse Yates <je...@gmail.com>
wrote:
> Great post, awesome to see the optimization going in.
>
> Would be cool to see if we could roll in some of the stuff talked about at
> the last meetup too :)
>
> On Sun, Nov 8, 2015, 11:27 AM James Taylor <ja...@apache.org> wrote:
>
>> Thanks, Juan. I fixed the typo.
>>
>> On Sun, Nov 8, 2015 at 11:21 AM, Samarth Jain <sa...@gmail.com>
>> wrote:
>>
>>> Glad you find it useful, Juan and thanks for reporting the typo. The
>>> column name should be EVENT_DATE. We will get it changed.
>>>
>>> On Sun, Nov 8, 2015 at 11:18 AM, Juan Rodríguez Hortalá <
>>> juan.rodriguez.hortala@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Very interesting post and very useful feature. Just a minor remark, I
>>>> think there is a typo in the post, in the CREATE TABLE EVENTS_RTS statement
>>>>
>>>> CREATE TABLE *EVENTS_RTS* (
>>>> EVENT_ID CHAR(15) NOT NULL,
>>>> EVENT_TYPE CHAR(3) NOT NULL,
>>>> EVENT_TIME DATE NOT NULL,
>>>> APPLICATION_TYPE VARCHAR,
>>>> SOURCE_IP VARCHAR
>>>> CONSTRAINT PK PRIMARY KEY (
>>>> EVENT_ID,
>>>> EVENT_TYPE,
>>>> EVENT_DATE *ROW_TIMESTAMP*))
>>>>
>>>> I think the column EVENT_TIME should be EVENT_DATE. Or maybe I'm not
>>>> understanding this correctly.
>>>>
>>>> Greetings,
>>>>
>>>> Juan
>>>>
>>>>
>>>>
>>>> On Sat, Nov 7, 2015 at 6:53 PM, James Taylor <ja...@apache.org>
>>>> wrote:
>>>>
>>>>> If you have time-series data for which you'd like to improve query
>>>>> performance, take a look at this[1] blog written by Samarth Jain on a new
>>>>> feature in our 4.6 release:
>>>>>
>>>>> https://blogs.apache.org/phoenix/entry/new_optimization_for_time_series
>>>>>
>>>>> Enjoy!
>>>>>
>>>>> James
>>>>>
>>>>
>>>>
>>>
>>
Re: blog describing new time-series data optimization
Posted by Jesse Yates <je...@gmail.com>.
Great post, awesome to see the optimization going in.
Would be cool to see if we could roll in some of the stuff talked about at
the last meetup too :)
On Sun, Nov 8, 2015, 11:27 AM James Taylor <ja...@apache.org> wrote:
> Thanks, Juan. I fixed the typo.
>
> On Sun, Nov 8, 2015 at 11:21 AM, Samarth Jain <sa...@gmail.com>
> wrote:
>
>> Glad you find it useful, Juan and thanks for reporting the typo. The
>> column name should be EVENT_DATE. We will get it changed.
>>
>> On Sun, Nov 8, 2015 at 11:18 AM, Juan Rodríguez Hortalá <
>> juan.rodriguez.hortala@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> Very interesting post and very useful feature. Just a minor remark, I
>>> think there is a typo in the post, in the CREATE TABLE EVENTS_RTS statement
>>>
>>> CREATE TABLE *EVENTS_RTS* (
>>> EVENT_ID CHAR(15) NOT NULL,
>>> EVENT_TYPE CHAR(3) NOT NULL,
>>> EVENT_TIME DATE NOT NULL,
>>> APPLICATION_TYPE VARCHAR,
>>> SOURCE_IP VARCHAR
>>> CONSTRAINT PK PRIMARY KEY (
>>> EVENT_ID,
>>> EVENT_TYPE,
>>> EVENT_DATE *ROW_TIMESTAMP*))
>>>
>>> I think the column EVENT_TIME should be EVENT_DATE. Or maybe I'm not
>>> understanding this correctly.
>>>
>>> Greetings,
>>>
>>> Juan
>>>
>>>
>>>
>>> On Sat, Nov 7, 2015 at 6:53 PM, James Taylor <ja...@apache.org>
>>> wrote:
>>>
>>>> If you have time-series data for which you'd like to improve query
>>>> performance, take a look at this[1] blog written by Samarth Jain on a new
>>>> feature in our 4.6 release:
>>>>
>>>> https://blogs.apache.org/phoenix/entry/new_optimization_for_time_series
>>>>
>>>> Enjoy!
>>>>
>>>> James
>>>>
>>>
>>>
>>
>
Re: blog describing new time-series data optimization
Posted by James Taylor <ja...@apache.org>.
Thanks, Juan. I fixed the typo.
On Sun, Nov 8, 2015 at 11:21 AM, Samarth Jain <sa...@gmail.com>
wrote:
> Glad you find it useful, Juan and thanks for reporting the typo. The
> column name should be EVENT_DATE. We will get it changed.
>
> On Sun, Nov 8, 2015 at 11:18 AM, Juan Rodríguez Hortalá <
> juan.rodriguez.hortala@gmail.com> wrote:
>
>> Hi,
>>
>> Very interesting post and very useful feature. Just a minor remark, I
>> think there is a typo in the post, in the CREATE TABLE EVENTS_RTS statement
>>
>> CREATE TABLE *EVENTS_RTS* (
>> EVENT_ID CHAR(15) NOT NULL,
>> EVENT_TYPE CHAR(3) NOT NULL,
>> EVENT_TIME DATE NOT NULL,
>> APPLICATION_TYPE VARCHAR,
>> SOURCE_IP VARCHAR
>> CONSTRAINT PK PRIMARY KEY (
>> EVENT_ID,
>> EVENT_TYPE,
>> EVENT_DATE *ROW_TIMESTAMP*))
>>
>> I think the column EVENT_TIME should be EVENT_DATE. Or maybe I'm not
>> understanding this correctly.
>>
>> Greetings,
>>
>> Juan
>>
>>
>>
>> On Sat, Nov 7, 2015 at 6:53 PM, James Taylor <ja...@apache.org>
>> wrote:
>>
>>> If you have time-series data for which you'd like to improve query
>>> performance, take a look at this[1] blog written by Samarth Jain on a new
>>> feature in our 4.6 release:
>>>
>>> https://blogs.apache.org/phoenix/entry/new_optimization_for_time_series
>>>
>>> Enjoy!
>>>
>>> James
>>>
>>
>>
>
Re: blog describing new time-series data optimization
Posted by Samarth Jain <sa...@gmail.com>.
Glad you find it useful, Juan and thanks for reporting the typo. The column
name should be EVENT_DATE. We will get it changed.
On Sun, Nov 8, 2015 at 11:18 AM, Juan Rodríguez Hortalá <
juan.rodriguez.hortala@gmail.com> wrote:
> Hi,
>
> Very interesting post and very useful feature. Just a minor remark, I
> think there is a typo in the post, in the CREATE TABLE EVENTS_RTS statement
>
> CREATE TABLE *EVENTS_RTS* (
> EVENT_ID CHAR(15) NOT NULL,
> EVENT_TYPE CHAR(3) NOT NULL,
> EVENT_TIME DATE NOT NULL,
> APPLICATION_TYPE VARCHAR,
> SOURCE_IP VARCHAR
> CONSTRAINT PK PRIMARY KEY (
> EVENT_ID,
> EVENT_TYPE,
> EVENT_DATE *ROW_TIMESTAMP*))
>
> I think the column EVENT_TIME should be EVENT_DATE. Or maybe I'm not
> understanding this correctly.
>
> Greetings,
>
> Juan
>
>
>
> On Sat, Nov 7, 2015 at 6:53 PM, James Taylor <ja...@apache.org>
> wrote:
>
>> If you have time-series data for which you'd like to improve query
>> performance, take a look at this[1] blog written by Samarth Jain on a new
>> feature in our 4.6 release:
>>
>> https://blogs.apache.org/phoenix/entry/new_optimization_for_time_series
>>
>> Enjoy!
>>
>> James
>>
>
>
Re: blog describing new time-series data optimization
Posted by Juan Rodríguez Hortalá <ju...@gmail.com>.
Hi,
Very interesting post and very useful feature. Just a minor remark, I think
there is a typo in the post, in the CREATE TABLE EVENTS_RTS statement
CREATE TABLE *EVENTS_RTS* (
EVENT_ID CHAR(15) NOT NULL,
EVENT_TYPE CHAR(3) NOT NULL,
EVENT_TIME DATE NOT NULL,
APPLICATION_TYPE VARCHAR,
SOURCE_IP VARCHAR
CONSTRAINT PK PRIMARY KEY (
EVENT_ID,
EVENT_TYPE,
EVENT_DATE *ROW_TIMESTAMP*))
I think the column EVENT_TIME should be EVENT_DATE. Or maybe I'm not
understanding this correctly.
Greetings,
Juan
On Sat, Nov 7, 2015 at 6:53 PM, James Taylor <ja...@apache.org> wrote:
> If you have time-series data for which you'd like to improve query
> performance, take a look at this[1] blog written by Samarth Jain on a new
> feature in our 4.6 release:
>
> https://blogs.apache.org/phoenix/entry/new_optimization_for_time_series
>
> Enjoy!
>
> James
>