Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Tue, 30 May 2017 23:38:04 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13057180.1489790655000.326082.1496187484126@Atlassian.JIRA>
In-Reply-To: <JIRA.13057180.1489790655000@Atlassian.JIRA>
References: <JIRA.13057180.1489790655000@Atlassian.JIRA> <JIRA.13057180.1489790655656@jira-lw-us.apache.org>
Subject: [jira] [Commented] (PHOENIX-3744) Support snapshot scanners for
 MR-based queries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 30 May 2017 23:38:07 -0000


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

ASF GitHub Bot commented on PHOENIX-3744:
-----------------------------------------

Github user akshita-malhotra commented on the issue:

    https://github.com/apache/phoenix/pull/239
  
    @JamesRTaylor  Thanks a lot for the review. I have made the suggested changes and uploaded the updated patch on the jira. 
    Regarding creating snapshot to generalize the use of snapshots for M/R jobs, I was under the impression that we are passing the snapshot name as input after our last discussion with @lhofhansl and Rahul G.
    If we are to follow the former approach, I will go ahead and make the changes.


> Support snapshot scanners for MR-based queries
> ----------------------------------------------
>
>                 Key: PHOENIX-3744
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3744
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Akshita Malhotra
>         Attachments: PHOENIX-3744.patch, PHOENIX-3744.patch
>
>
> HBase support scanning over snapshots, with a SnapshotScanner that accesses the region directly in HDFS. We should make sure that Phoenix can support that.
> Not sure how we'd want to decide when to run a query over a snapshot. Some ideas:
> - if there's an SCN set (i.e. the query is running at a point in time in the past)
> - if the memstore is empty
> - if the query is being run at a timestamp earlier than any memstore data
> - as a config option on the table
> - as a query hint
> - based on some kind of optimizer rule (i.e. based on estimated # of bytes that will be scanned)
> Phoenix typically runs a query at the timestamp at which it was compiled. Any data committed after this time should not be seen while a query is running.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)