[
https://issues.apache.org/jira/browse/SOLR-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800706#comment-16800706
]
Josh Elser commented on SOLR-9963:
----------------------------------
{quote}Switched this over to SolrCloudTestCase and found an interesting error
that reproduces. I haven't tracked down why yet but it has something to do with
multiple shards/replicas on the same node.
{quote}
Well that's interesting. I thought the connectionId and statementId (UUIDs)
that Avatica generates are always random UUIDs. Without knowing anything about
SolrCloudTestCase, maybe something happens there that makes Avatica
inadvertently try to re-use an old one? Sounds like something worth chasing.
> Add Apache Calcite Avatica handler to Solr
> ------------------------------------------
>
> Key: SOLR-9963
> URL: https://issues.apache.org/jira/browse/SOLR-9963
> Project: Solr
> Issue Type: Improvement
> Components: Parallel SQL
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Major
> Attachments: SOLR-9963.patch, SOLR-9963.patch, SOLR-9963.patch,
> SOLR-9963.patch, SOLR-9963.patch, test_avatica_solr.sh
>
>
> Apache Calcite Avatica has an http endpoint which allows Avatica drivers to
> connect to the server. This can be wired in as a handler to Solr. This would
> allow Solr to be used by any Avatica JDBC/ODBC driver. This depends on the
> Calcite work from SOLR-8593.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
