[
https://issues.apache.org/jira/browse/PHOENIX-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023279#comment-16023279
]
ASF GitHub Bot commented on PHOENIX-3744:
-----------------------------------------
Github user JamesRTaylor commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/239#discussion_r118314856
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/iterate/RegionContext.java ---
@@ -0,0 +1,15 @@
+package org.apache.phoenix.iterate;
+
+import org.apache.hadoop.hbase.coprocessor.RegionCoprocessorEnvironment;
+
+/**
+ * Maintains coprocessor environment state to
+ * make region observer functionality work for
+ * non-coprocessor environment
+ */
+public interface RegionContext {
+
+ /** @return the Coprocessor environment */
+ RegionCoprocessorEnvironment getEnvironment();
--- End diff --
If this is the only method, we don't really need this interface. Why not
just keep using RegionCoprocessorEnvironment in our APIs and you can just
instantiate you snapshot-based one prior to getting the RegionScanner?
> 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
>
>
> 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)
