[ 
https://issues.apache.org/jira/browse/SOLR-16433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622752#comment-17622752
 ] 

Kevin Risden commented on SOLR-16433:
-------------------------------------

Whoops that commit was supposed to reference SOLR-16443

> Security Manager prevents Solr SQL from working
> -----------------------------------------------
>
>                 Key: SOLR-16433
>                 URL: https://issues.apache.org/jira/browse/SOLR-16433
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Parallel SQL
>    Affects Versions: 9.0
>            Reporter: Kevin Risden
>            Assignee: Kevin Risden
>            Priority: Blocker
>             Fix For: 9.1, main (10.0)
>
>         Attachments: Calcite Exception.png
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Workaround: set SOLR_SECURITY_MANAGER_ENABLED=false. This is only defaulted 
> to true in Solr 9.0. Previously with Solr 8.x this was set to false.
> This was reported on the Solr user list:
> https://lists.apache.org/thread/hbozfyn9xpno2tk573pk3vjbyhohyqnm
> Calcite tries to initialize and check a few paths for the test dataset, but 
> the security manager throws an exception for this:
> * 
> https://github.com/apache/calcite/blob/main/core/src/main/java/org/apache/calcite/config/CalciteSystemProperty.java#L189
>  
> I'm tracking this down in CALCITE-5298
>  !Calcite Exception.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to