Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AF17D200CAD for ; Tue, 6 Jun 2017 02:02:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id ADC52160BE1; Tue, 6 Jun 2017 00:02:15 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 003A1160BD4 for ; Tue, 6 Jun 2017 02:02:14 +0200 (CEST) Received: (qmail 29027 invoked by uid 500); 6 Jun 2017 00:02:14 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 29016 invoked by uid 99); 6 Jun 2017 00:02:14 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2017 00:02:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id BA158C0310 for ; Tue, 6 Jun 2017 00:02:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id i3UUxyyrAkxS for ; Tue, 6 Jun 2017 00:02:13 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id BE8AF5FAFA for ; Tue, 6 Jun 2017 00:02:12 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5D913E00D4 for ; Tue, 6 Jun 2017 00:02:12 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1D58621E0A for ; Tue, 6 Jun 2017 00:02:12 +0000 (UTC) Date: Tue, 6 Jun 2017 00:02:12 +0000 (UTC) From: "Akshita Malhotra (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (PHOENIX-3744) Support snapshot scanners for MR-based queries MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 06 Jun 2017 00:02:15 -0000 [ https://issues.apache.org/jira/browse/PHOENIX-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akshita Malhotra updated PHOENIX-3744: -------------------------------------- Attachment: PHOENIX-3744-4.x-HBase-0.98.patch > 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-4.x-HBase-0.98.patch, PHOENIX-3744.patch, 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)