[
https://issues.apache.org/jira/browse/SOLR-16131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515969#comment-17515969
]
Houston Putman commented on SOLR-16131:
---------------------------------------
You don't have to edit solr.in.sh, it's just an environment variable, which is
a much more standard way of enabling features in cloud services. So in the
future we are actually trying to move forward in a way that all options are set
via the solr.xml, system properties OR environment variables. Give users the
choice.
I also just tested the solr docker image, using {{--env SOLR_MODULES=sql}} and
it worked just fine. I think it's more an issue with how you are using
solr.in.sh
> sql module cannot load Calcite driver
> -------------------------------------
>
> Key: SOLR-16131
> URL: https://issues.apache.org/jira/browse/SOLR-16131
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Joel Bernstein
> Priority: Blocker
> Fix For: 9.0
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> After adding the sql module, using -Dsolr.modules=sql from the command line
> on startup, sql queries throw the following error:
> Failed to load JDBC driver for
> 'org.apache.solr.handler.sql.CalciteSolrDriver'
> This makes the sql module inoperable.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
