[
https://issues.apache.org/jira/browse/SOLR-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276476#comment-15276476
]
Joel Bernstein edited comment on SOLR-8593 at 5/9/16 3:09 PM:
--------------------------------------------------------------
I think my main concern is that the join pushdown rules haven't been exercised
that much in production. Also do we have access to the SQL catalog and
statistics from inside the rules engine. We'll need that information to decide
which type of join to do. I guess we can make the catalog globally accessible
if the rules API doesn't provide hooks into it.
was (Author: joel.bernstein):
I think my main concern is that the join pushdown rules haven't been exercised
that much in production.
> Integrate Apache Calcite into the SQLHandler
> --------------------------------------------
>
> Key: SOLR-8593
> URL: https://issues.apache.org/jira/browse/SOLR-8593
> Project: Solr
> Issue Type: Improvement
> Reporter: Joel Bernstein
> Fix For: master
>
>
> The Presto SQL Parser was perfect for phase one of the SQLHandler. It was
> nicely split off from the larger Presto project and it did everything that
> was needed for the initial implementation.
> Phase two of the SQL work though will require an optimizer. Here is where
> Apache Calcite comes into play. It has a battle tested cost based optimizer
> and has been integrated into Apache Drill and Hive.
> This work can begin in trunk following the 6.0 release. The final query plans
> will continue to be translated to Streaming API objects (TupleStreams), so
> continued work on the JDBC driver should plug in nicely with the Calcite work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
