[
https://issues.apache.org/jira/browse/PHOENIX-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563852#comment-15563852
]
James Taylor commented on PHOENIX-3359:
---------------------------------------
Would be great if we could come up with a way of getting the Phoenix explain
plan instead of the Calcite one. Two ideas:
- Create a new detail level for EXPLAIN PLAN in Calcite and have this generate
the Phoenix explain plan. This would be the cleanest way, I think.
- Take advantage of the subtle difference in syntax (i.e. EXPLAIN PLAN FOR
<query> versus EXPLAIN <query>) and have the latter generate the Phoenix
explain plan.
If we can make a general change across the board for the Calcite branch to
generate Phoenix explain plans, I think it's probably worth it. If they're just
one-off changes, though, I agree, we should move on to other stuff.
> Update JDBC urls to match connection type
> -----------------------------------------
>
> Key: PHOENIX-3359
> URL: https://issues.apache.org/jira/browse/PHOENIX-3359
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Eric Lomore
> Assignee: Eric Lomore
>
> Connection's that are intended to be unwrapped into PhoenixConnection's need
> to be created using the old JDBC url,
> {{DriverManager.getConnection(getOldUrl())}}
> {{PhoenixConnection pc = conn.unwrap(PhoenixConnection.class);}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
