m: Thomas D'Silva [mailto:tdsi...@salesforce.com]
> Sent: Monday, February 22, 2016 14:59
> To: user@phoenix.apache.org
> Subject: Re: Multiple versions for single row key
>
> You need to set the versions attribute of the scan :
> scan ‘t1’, {RAW => true, VERSIONS => 10}
Thanks Thomas. Do we have rough estimate of when PHOENIX-590 will be done?
-Original Message-
From: Thomas D'Silva [mailto:tdsi...@salesforce.com]
Sent: Monday, February 22, 2016 14:59
To: user@phoenix.apache.org
Subject: Re: Multiple versions for single row key
You need to se
query (select * from MULTI_ROW_KEYS) with this connection property
> (cal.set(2106, 1, 22, 11, 0, 0)), returns only first row (ID: a, PRICE:
> 100.0) and
>
> Running query (select * from MULTI_ROW_KEYS) with this connection property
> (cal.set(2106, 1, 22, 12, 0, 0)), returns only fi
uary 11, 2016 13:20
To: user@phoenix.apache.org
Subject: RE: Multiple versions for single row key
Thanks a lot James, I’ll try this.
From: James Taylor [mailto:jamestay...@apache.org]
Sent: Thursday, February 11, 2016 12:43
To: user@phoenix.apache.org<mailto:user@phoenix.apache.org>
Subject: Re:
Thanks a lot James, I’ll try this.
From: James Taylor [mailto:jamestay...@apache.org]
Sent: Thursday, February 11, 2016 12:43
To: user@phoenix.apache.org
Subject: Re: Multiple versions for single row key
Hi Kannan,
Yes, you can keep 3 versions of a cell in Phoenix (just add VERSIONS=3 to your
2016 12:03
> *To:* user@phoenix.apache.org
>
> *Subject:* Multiple versions for single row key
>
>
>
> Hello,
>
>
>
> HBase tables support multiple versions (default is 3) for single row key.
> I am trying to see how efficiently this can be achieved in Phoenix (don’t
> wan
Any suggestions?
From: Ramanathan, Kannan: IT (NYK)
Sent: Wednesday, February 10, 2016 12:03
To: user@phoenix.apache.org
Subject: Multiple versions for single row key
Hello,
HBase tables support multiple versions (default is 3) for single row key. I am
trying to see how efficiently this can be
Hello,
HBase tables support multiple versions (default is 3) for single row key. I am
trying to see how efficiently this can be achieved in Phoenix (don't want to
create view on existing HBase table, just want to go with new Phoenix table).
Is it better to create a separate secondary key column
