Thanks a lot James, I’ll try this.

 

From: James Taylor [mailto:jamestaylor@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 DDL statement), however you'll only see one version when you query (by default, the latest - see [1] for how to see an earlier version). PHOENIX-590 (not implemented) is about seeing all versions.

 

HTH,

James

 

[1] https://phoenix.apache.org/faq.html#Can_phoenix_work_on_tables_with_arbitrary_timestamp_as_flexible_as_HBase_API

On Thursday, February 11, 2016, <kannan.ramanathan@barclays.com> wrote:

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 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 in Phoenix table which is of course not unique and setup secondary index on this column for faster querying?

 

Also, is this JIRA related what I am asking?

 

https://issues.apache.org/jira/browse/PHOENIX-590

 

Sorry if this has been answered before and thanks in advance.

 

Regards

Kannan.

_______________________________________________

This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.

For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.

_______________________________________________

_______________________________________________

This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.

For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.

_______________________________________________

_______________________________________________

This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.

For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.

_______________________________________________