[ https://issues.apache.org/jira/browse/PHOENIX-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011009#comment-16011009 ]
ASF GitHub Bot commented on PHOENIX-3744: ----------------------------------------- Github user JamesRTaylor commented on the issue: https://github.com/apache/phoenix/pull/239 Please amend your commit message to be prefixed with PHOENIX-3744 (instead of Phoenix-3744) so that review comments show up as comments on the JIRA, @akshita-malhotra. Also, let's get a patch attached to the JIRA so we can get a test run to make sure there are no regressions. Directions here: https://phoenix.apache.org/contributing.html#Generate_a_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 > > 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)