[SOLR-16433] Security Manager prevents Solr SQL from working

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 9.0
• Fix Version/s: 9.1, main (10.0)
• Component/s: Parallel SQL
• Assignee: Kevin Risden
• Reporter: Kevin Risden
• Created: 25/Sep/22 15:08
• Updated: 25/Jan/23 16:16
• Resolved: 12/Oct/22 16:16

Description

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

Issue Links

• is related to: SOLR-16457 solr.data.home should not be set to empty string in bin/solr
• relates to: CALCITE-5298 CalciteSystemProperty calcite.test.dataset path check fails under Java Security Manager
• links to: GitHub Pull Request #1044
• links to: GitHub Pull Request #1106