We are implementing a JDBC driver on drill with Solr as a storage plugin
The code had been here and we need help if anyone can contribute doing a code 
review and performance testing
https://github.com/apache/drill/pull/201/files

Thanks,
Tirthankar

On Nov 20, 2015, at 12:25 PM, William Bell 
<[email protected]<mailto:[email protected]>> wrote:

How is performance on Calcite?

On Fri, Nov 20, 2015 at 5:12 AM, Joel Bernstein 
<[email protected]<mailto:[email protected]>> wrote:

After reading https://calcite.apache.org/docs/tutorial.html, I think it
should be possible to use the Solr's JDBC Driver with Calcites JDBC
adapter.

If you give it a try and run into any problems, please create a jira.

Joel Bernstein
http://joelsolr.blogspot.com/

On Thu, Nov 19, 2015 at 7:58 PM, Joel Bernstein 
<[email protected]<mailto:[email protected]>>
wrote:

It's an interesting question. The JDBC driver is still very basic. It
would depend on how much of the JDBC spec needs to be implemented to
connect to Calcite/Drill.

Joel Bernstein
http://joelsolr.blogspot.com/

On Thu, Nov 19, 2015 at 3:28 AM, Kai G?lzau 
<[email protected]<mailto:[email protected]>>
wrote:


We are currently evaluating calcite as a SQL facade for different Data
Sources

-          JDBC

-          REST

      SOLR

-          ...

I didn't found a "native" calcite adapter for solr (
http://calcite.apache.org/docs/adapter.html).

Is it a good idea to use the parallel sql feature (over jdbc) to connect
calcite (or apache drill) to solr?
Any suggestions?


Thanks,

Kai G?lzau







--
Bill Bell
[email protected]<mailto:[email protected]>
cell 720-256-8076



***************************Legal Disclaimer***************************
"This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message by mistake,
please advise the sender by reply email and delete the message. Thank you."
**********************************************************************

Reply via email to