You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/07/16 20:10:06 UTC
[jira] [Resolved] (HBASE-899) Support for specifying a timestamp
and numVersions on a per-column basis
[ https://issues.apache.org/jira/browse/HBASE-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-899.
-------------------------
Resolution: Won't Fix
Resolving. Old.
> Support for specifying a timestamp and numVersions on a per-column basis
> ------------------------------------------------------------------------
>
> Key: HBASE-899
> URL: https://issues.apache.org/jira/browse/HBASE-899
> Project: HBase
> Issue Type: New Feature
> Reporter: Doğacan Güney
>
> This is just an idea and it may be better to wait after the planned API changes. But I think it would be useful to support fetching different timestamps and versions for different columns.
> Example:
> If a row has 2 columns, "col1:" and "col2:" I want to be able to ask for (during scan or read time, doesn't matter) 2 versions of "col1:" (maybe even between timestamps t1 and t2) but only 1 version of "col2:". This would be especially handy if during an MR job you have to read 2 versions of a small column, but do not want the overhead of reading 2 versions of every other column too....
> (Also, the mechanism is already there. I mean, making the changes to support a per-column timestamp/numVersions is ridiculously easy :)
--
This message was sent by Atlassian JIRA
(v6.2#6252)