[
https://issues.apache.org/jira/browse/SOLR-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262895#comment-15262895
]
Kevin Risden edited comment on SOLR-8593 at 4/28/16 8:15 PM:
-------------------------------------------------------------
Ok made a bunch of progress on the jira/solr-8593 branch:
* cleaned up the tests so that there are only a few remaining items to address
(outlined below)
* added support for float/double types
* fixed a CloudSolrClient resource leak
Left to do:
* Add support for aggregationMode (facets and map_reduce) and their parameters
* ensure the pushdown to facets/map_reduce works correctly
* figure out the CloudSolrClient cache (currently not caching and creating new
per stream)
* Push down aggregates to Solr
* add tests to ensure the proper plan is being generated by Calcite
* figure out avg(int) problem in tests.
** avg(int) returns int by design. need to figure out if casting is right for
the tests
* figure out sort asc by default in tests
** this currently doesn't sort properly even though I thought that the right
approach was sort on _version_.
was (Author: risdenk):
Ok made a bunch of progress on the jira/solr-8593 branch:
* cleaned up the tests so that there are only a few remaining items to address
(outlined below)
* added support for float/double types
* fixed a CloudSolrClient resource leak
Left to do:
* Add support for facets and map_reduce as parameters
* ensure the pushdown to facets/map_reduce works correctly
* figure out the CloudSolrClient cache (currently not caching and creating new
per stream)
* Push down aggregates to Solr
* add tests to ensure the proper plan is being generated by Calcite
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
