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 <[email protected]> wrote: > Thanks, Juan. I fixed the typo. > > On Sun, Nov 8, 2015 at 11:21 AM, Samarth Jain <[email protected]> > 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á < >> [email protected]> 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 <[email protected]> >>> 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 >>>> >>> >>> >> >
