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

ASF subversion and git services commented on SOLR-15349:
--------------------------------------------------------

Commit 4bbbe20898c43fc443d20d4297341cd8b1d1e593 in solr's branch 
refs/heads/main from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=4bbbe20898c ]

SOLR-15349: Remove solrcore.properties support (#3905)

* solrcore.properties is gone, but we still support custom properties files for 
a core.
* Move away from deprecated SolrJettyTestBase and embrace the SolrJettyTestRule 
in the tests

> Remove support for solrcore.properties
> --------------------------------------
>
>                 Key: SOLR-15349
>                 URL: https://issues.apache.org/jira/browse/SOLR-15349
>             Project: Solr
>          Issue Type: Task
>            Reporter: Cassandra Targett
>            Assignee: Eric Pugh
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> A few issues (such as SOLR-7613, SOLR-7507) mention that 
> {{solrcore.properties}} is now redundant with other features like Config 
> API's {{configoverlay.json}} and custom properties in {{core.properties}}. 
> It's also not read by ZooKeeper, so is of minimal value to any install using 
> SolrCloud.
> At some point {{solrcore.properties}} was marked as "deprecated" in the Ref 
> Guide, but as far as I can tell there hasn't been an issue filed yet to 
> actually remove it.
> I find its purpose confusing, so I am going to remove mention of it from the 
> Ref Guide for 9.0. But we should actually remove it if it's redundant and of 
> lesser value and if we can do that for 9.0 we should (I cannot, so won't be 
> changing anything other than docs).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to