[
https://issues.apache.org/jira/browse/HBASE-14872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094949#comment-15094949
]
churro morales commented on HBASE-14872:
----------------------------------------
[~apurtell] good catch on the proto, guess thats why we should push upstream
before committing in our local repo :). I'll make that change. For the Map
being lazily initialized, I can make that happen in Query.java no problem. And
the exception message doesn't really apply, don't know if it ever did, but
since that was existing I just left it, that one I am willing to do whatever.
Will get you a patch soon.
> 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
> Reporter: churro morales
> Assignee: churro morales
> Fix For: 2.0.0, 1.2.0, 0.98.18
>
> Attachments: HBASE-14872-0.98.patch, HBASE-14872-v1.patch,
> 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)
