phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <>
Subject Re: Query HBase column/row timestamp
Date Sat, 07 Jun 2014 07:26:12 GMT
Hi Justin,
What Jeffrey said is accurate. It would not be difficult to add a new
built-in function for this purpose, but it's ambiguous as far as which
KeyValue you'd use to get the timestamp as there is no "row"
timestamp. Would you filter all columns against the timestamp? If all
KeyValues for a row are filtered, would the entire row be filtered?
How would this be specified in SQL?

If you're interested, maybe take a stab at defining how it would work
and file a JIRA?


On Fri, Jun 6, 2014 at 3:46 PM, Jeffrey Zhong <> wrote:
> As far as I know there is no way in Phoenix that you can explicitly query
> data based on underlying hbase row key time stamp. Phoenix does provide a
> connection property "CurrentSCN" which sets the upper bound of time stamps
> but not point or range query against row key time stamp. You can explicitly
> create a timestamp column in your table if there is a need.
> From: Justin Workman <>
> Reply-To: <>
> Date: Friday, June 6, 2014 2:26 PM
> To: "" <>
> Subject: Query HBase column/row timestamp
> Sorry if this question has already been answered somewhere, I haven't been
> able to find it through normal channels or searching.
> Is it possible to query by the Hbase column or row timestamp value?
> Basically I want to select all records, via Phoenix, where the last
> timestamp is ~24 hours.
> Thanks
> Justin
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader of
> this message is not the intended recipient, you are hereby notified that any
> printing, copying, dissemination, distribution, disclosure or forwarding of
> this communication is strictly prohibited. If you have received this
> communication in error, please contact the sender immediately and delete it
> from your system. Thank You.

View raw message