[
https://issues.apache.org/jira/browse/PHOENIX-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729916#comment-14729916
]
James Taylor commented on PHOENIX-2198:
---------------------------------------
Thanks for the patch, [~maryannxue]. This is a very nice addition. What will be
the performance characteristics of a query that uses the new CorrelatedPlan as
a nested loop join? What kind of batching are we doing and what controls that?
Is it not currently possible to use the CorrelatedPlan in Phoenix, but only
from the Calcite branch?
Not sure about the failure, [~maryannxue] - I haven't seen that before.
Sometimes this can happen if the size of the row changes, as you'll send up
with more guideposts than before.
For this new dynamic filter that gets passed through, are there any potential
interactions when a VIEW is used? In this case, we grab the WHERE clause off of
the view and dynamically apply it when we compile the query. Will that work
together with this? Also, what about the skip scan we dynamically do when a
global index is hinted. Probably a good idea to add some testing around these
scenarios.
> Support correlate variable
> --------------------------
>
> Key: PHOENIX-2198
> URL: https://issues.apache.org/jira/browse/PHOENIX-2198
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Attachments: PHOENIX-2198.patch
>
> Original Estimate: 240h
> Remaining Estimate: 240h
>
> This will enable the outer query to set a correlate variable as a parameter
> to restart the inner query for each iteration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
