You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/03/15 22:28:00 UTC

[jira] [Updated] (SOLR-18123) Tests: Shouldn't need to refer to ALLOW_PATHS_SYSPROP, usually

     [ https://issues.apache.org/jira/browse/SOLR-18123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated SOLR-18123:
----------------------------------
    Labels: newdev pull-request-available  (was: newdev)

> Tests: Shouldn't need to refer to ALLOW_PATHS_SYSPROP, usually
> --------------------------------------------------------------
>
>                 Key: SOLR-18123
>                 URL: https://issues.apache.org/jira/browse/SOLR-18123
>             Project: Solr
>          Issue Type: Test
>          Components: test-framework
>            Reporter: David Smiley
>            Priority: Minor
>              Labels: newdev, pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Many of our Java/JUnit tests use ALLOW_PATHS_SYSPROP {{solr.security.allow.paths}} to ensure the embedded Solr can read something.  Instead, our test infrastructure should, by default, not have such restrictions that necessitate a test configuring this.  That restriction is designed for security, which is a production consideration.  Perhaps it might be useful to isolate tests but I think we should have other mechanisms for that.



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

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