hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "churro morales (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14872) Scan different timeRange per column family doesn't percolate down to the memstore
Date Wed, 25 Nov 2015 21:50:11 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027663#comment-15027663
] 

churro morales commented on HBASE-14872:
----------------------------------------

Looks like changing the ScannerModel will be a bit of work.  Right now it doesn't look like
the rest API supports the everything the scan does, do you guys think its fine leaving this
column family time range feature for the rest client?  If not I can take a stab at making
it work but it will take some time,  I can get a patch for everything else to fix the other
issues right now.  What do you think [~stack] and [~apurtell] ? 

> 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)

Mime
View raw message