[
https://issues.apache.org/jira/browse/CALCITE-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17656678#comment-17656678
]
Stamatis Zampetakis commented on CALCITE-5298:
----------------------------------------------
I left a comment under the PR. Actually I am wondering why we can't catch
SecurityException? As far as I know the class is not deprecated so I am not
sure why we need to rely on other workarounds.
> CalciteSystemProperty calcite.test.dataset path check fails under Java
> Security Manager
> ---------------------------------------------------------------------------------------
>
> Key: CALCITE-5298
> URL: https://issues.apache.org/jira/browse/CALCITE-5298
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.27.0, 1.28.0, 1.29.0, 1.30.0, 1.31.0, 1.32.0
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.33.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> SOLR-16433 found that Calcite does not handle the Java security manager
> returning permission denied when checking that the calcite.test.dataset path
> exists. Solr runs with a security manager that doesn't allow arbitrary
> filesystem access. This failure causes Calcite to not load and therefore
> unusable.
> The code in question is here:
> https://github.com/apache/calcite/blame/main/core/src/main/java/org/apache/calcite/config/CalciteSystemProperty.java#L189
> A few other places in Calcite already check for SecurityException:
> https://github.com/apache/calcite/search?q=SecurityException
--
This message was sent by Atlassian Jira
(v8.20.10#820010)