Re: Apache Phoenix integration

This is a very great news! But what do you mean exactly with "Apache Drill is off of it's fork"? When is this deeper integration going to be released/integrated? Will Phoenix (eventually) become just a Drill storage plugin, with huge benefits for both? On 2 Feb 2018 20:20, "James Taylor"

Anonymous survey: Apache HBase 1.x Usage

Please take this anonymous survey ​ to ​ let us know what version of Apache HBase 1.x you are using in production now or are planning to use in production in the next year or so. Multiple choices are allowed. ​There is no "I'm not using 1.x" choice. Consider upgrading! (smile)

Re: ROW_TIMESTAMP

Right. Will do in this way. Thank you again. :-) James Taylor wrote > Yes, I think having your own LAST_UPDATED column would be the best option > currently. > > On Fri, Feb 2, 2018 at 1:18 PM, Alberto Bengoa > alberto@.com > > wrote: > >> Hello James, >> >> Thanks for replying. >> >> It

Index table in SYSTEM.CATALOG without DATA_TABLE_NAME and INDEX_TYPE

Hi everyone, I am investigating a strange looking entry in our SYSTEM.CATALOG table. The row is an index table (TABLE_TYPE = i) but it does not contain any other index information (no DATA_TABLE_NAME and INDEX_TYPE, etc.). Has anyone encountered similar situation, or is there any other way to

Re: ROW_TIMESTAMP

Yes, I think having your own LAST_UPDATED column would be the best option currently. On Fri, Feb 2, 2018 at 1:18 PM, Alberto Bengoa wrote: > Hello James, > > Thanks for replying. > > It really seems that PHOENIX-4552 potentially fits to my purpose. I'll > track > this

Re: ROW_TIMESTAMP

Hello James, Thanks for replying. It really seems that PHOENIX-4552 potentially fits to my purpose. I'll track this JIRA to get updates about it. BTW, considering nowadays, there's no option except to update some date type field on client side every upsert? Thank you so much. Alberto James

Re: Apache Phoenix integration

Good idea - a joint meetup would be great. On Fri, Feb 2, 2018 at 11:15 AM, Saurabh Mahapatra < saurabhmahapatr...@gmail.com> wrote: > This is absolutely great news! Thanks for sharing, James! > > We should have this as a presentation in one of our weekly Drill hangout > sessions. > > It’s about

Re: Apache Phoenix integration

There's also a much deeper integration between Phoenix + Drill (code named Drillix) underway that should be possible to complete now that Apache Drill is off of it's fork and on a later version of Apache Calcite. I'm hoping that the output of this will be a Phoenix adapter in Drill. See

Re: ROW_TIMESTAMP

Hi Alberto, Sounds like you need PHOENIX-4552. If you agree, let's continue the discussion over there. Thanks, James On Fri, Feb 2, 2018 at 9:05 AM, Alberto Bengoa wrote: > Hello Folks, > > I'm working on a project where we need to identify when a row was changed >

ROW_TIMESTAMP

Hello Folks, I'm working on a project where we need to identify when a row was changed (updated fields). I was wondering if ROW_TIMESTAMP would help me to reach this goal. I created the test table bellow, and inserted some data: create table test( a integer not null, b integer,