[
https://issues.apache.org/jira/browse/CALCITE-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256638#comment-17256638
]
Stamatis Zampetakis commented on CALCITE-4188:
----------------------------------------------
You opted to model correlated variables as dynamic parameters in the SQL
statement and I think that's a good idea; but from that point onwards I don't
see why we should distinguish them. Possibly we could avoid introducing new
classes such as {{SqlFieldAccessCorrelate}} if we used entirely dynamic params.
I could try to see if it's possible to eliminate SqlFieldAccessCorrelate
without making the code much harder to understand but I was wondering if you
tried that already.
> support EnumerableBatchNestedLoopJoin in JdbcToEnumerableConverter implement
> ----------------------------------------------------------------------------
>
> Key: CALCITE-4188
> URL: https://issues.apache.org/jira/browse/CALCITE-4188
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.25.0
> Reporter: JIasen Sheng
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> support EnumerableBatchNestedLoopJoin in JdbcToEnumerableConverter implement
> function
> ENUMERABLE_BATCH_NESTED_LOOP_JOIN_RULE make correlate RexNode,
> when implementing,
> [https://github.com/apache/calcite/blob/eab043f4ef43112c16a9f6708e6c53a15b1cfbe0/core/src/main/java/org/apache/calcite/rel/rel2sql/SqlImplementor.java#L675]
> will throw null Exception
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
