DataWorks Summit/Hadoop Summit - Call for abstract

Just a quick note on the DataWorks Summit / Hadoop Summit Should have sent this across earlier but anyway.. The DataWorks Summit/Hadoop Summit Organizing Committee invites you to submit an abstract to be considered for the summit in San Jose on June 13-15. We

Re: Missing support for HBase 1.0 in Phoenix 4.9 ?

It would be nice if the actual Phoenix website mentioned things like this, instead of having to look through blog posts, mailing lists, the issue tracker, and whatever search-hadoop is... On Tue, Feb 7, 2017 at 9:52 AM, Ankit Singhal wrote: > The relevant thread where the decision was made to dr

Re: Missing support for HBase 1.0 in Phoenix 4.9 ?

The relevant thread where the decision was made to drop HBase 1.0 support from v4.9 onwards. http://search-hadoop.com/m/Phoenix/9UY0h21AGFh2sgGFK?subj=Re+DISCUSS+Drop+HBase+1+0+support+for+4+9 On Tue, Feb 7, 2017 at 8:13 PM, Mark Heppner wrote: > Pedro, > I can't answer your question, but if y

Re: ROW_TIMESTAMP weird behaviour

It's actually getting added but may be due to timezone difference, your values are going in future. You can set the local time zone by setting phoenix.query.dateFormatTimeZone https://phoenix.apache.org/tuning.html On Tue, Feb 7, 2017 at 6:34 PM, Dhaval Modi wrote: > Thanks Ankit. > > My issue i

Re: Missing support for HBase 1.0 in Phoenix 4.9 ?

Pedro, I can't answer your question, but if you look at the blog announcement for 4.9, they say it's compatible with HBase 0.98/1.1/1.2: https://blogs.apache.org/phoenix/entry/announcing_phoenix_4_9_released The announcements for 4.8 and lower says HBase 0.98/*1.0*/1.1/1.2: https://blogs.ap

Re: ROW_TIMESTAMP weird behaviour

Thanks Ankit. My issue is relevant to PHOENIX-3176. But additional observation is, any timestamp value after 13:oo hours of the same day is not added. 0: jdbc:phoenix:> select * from DUMMY; +--+ | XXX_TS | +--+ | 2017-01-01 15:02:

Re: ROW_TIMESTAMP weird behaviour

I think you are also hitting https://issues.apache.org/jira/browse/PHOENIX-3176. On Tue, Feb 7, 2017 at 2:18 PM, Dhaval Modi wrote: > Hi Pedro, > > Upserted key are different. One key is for July month & other for January > month. > 1. '2017-*07*-02T15:02:21.050' > 2. '2017-*01*-02T15:02:21.050'

Re: ROW_TIMESTAMP weird behaviour

Hi Pedro, Upserted key are different. One key is for July month & other for January month. 1. '2017-*07*-02T15:02:21.050' 2. '2017-*01*-02T15:02:21.050' Regards, Dhaval Modi dhavalmod...@gmail.com On 7 February 2017 at 13:18, Pedro Boado wrote: > Hi. > > I don't think it's weird. That column

activate apache phoenix metrics in spark

Hi, Is there any example of how can I activate the apache metrics in spark with python? https://phoenix.apache.org/metrics.html Thanks!