[
https://issues.apache.org/jira/browse/HBASE-14872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027363#comment-15027363
]
Andrew Purtell commented on HBASE-14872:
----------------------------------------
bq. Aside from that looks like ScannerModel is the last reference for
scan.getTimeRange() that needs to be updated. Looks like this is used for the
rest API, do we want to go ahead and make the changes there too?
Any changes to ScannerModel are fine as long as they are backwards compatible
with requests which might be made by older clients.
> Scan different timeRange per column family doesn't percolate down to the
> memstore
> ----------------------------------------------------------------------------------
>
> Key: HBASE-14872
> URL: https://issues.apache.org/jira/browse/HBASE-14872
> Project: HBase
> Issue Type: Bug
> Components: Client, regionserver, Scanners
> Affects Versions: 2.0.0, 1.3.0
> Reporter: churro morales
> Assignee: churro morales
> Fix For: 2.0.0, 1.3.0, 0.98.17
>
> Attachments: HBASE-14872.patch
>
>
> HBASE-14355 The scan different time range for column family feature was not
> applied to the memstore it was only done for the store files. This breaks
> the contract.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
