[jira] [Updated] (SOLR-8734) fix deprecation warnings for absent (maxMergeDocs|mergeFactor)
[ https://issues.apache.org/jira/browse/SOLR-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke updated SOLR-8734: -- Attachment: SOLR-8734.patch Attaching proposed warnings fix patch against master. The proposed patch includes a fix/change of erroring/failing if a is combined with a element whereas the [existing code|https://github.com/apache/lucene-solr/blob/master/solr/core/src/java/org/apache/solr/update/SolrIndexConfig.java#L250] would ignore the element and use the default instead. Though perhaps that is too controversional a change in general or for any future 5.5.1 release in particular? > fix deprecation warnings for absent (maxMergeDocs|mergeFactor) > -- > > Key: SOLR-8734 > URL: https://issues.apache.org/jira/browse/SOLR-8734 > Project: Solr > Issue Type: Bug >Affects Versions: 5.5, master >Reporter: Christine Poerschke >Assignee: Christine Poerschke > Attachments: SOLR-8734.patch > > > [~markus17] wrote on the solr-user mailing list: > bq. 5.5.0 SOLR-8621 deprecation warnings without maxMergeDocs or mergeFactor > ... > bq. o.a.s.c.Config Beginning with Solr 5.5, is deprecated, > configure it on the relevant instead. > ... > bq. On my development machine for all cores. None of the cores has either > parameter configured. Is this expected? > ... > [~cpoerschke] replied: > ... > bq. Could you advise if/that the solrconfig.xml has a element > (for which deprecated warnings would appear separately) or that the > solrconfig.xml has no element? > ... > bq. If either is the case then yes based on the code > (SolrIndexConfig.java#L153) the warnings would be expected-and-harmless > though admittedly are confusing, and fixable. > ... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-8734) fix deprecation warnings for absent (maxMergeDocs|mergeFactor)
[ https://issues.apache.org/jira/browse/SOLR-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christine Poerschke updated SOLR-8734: -- Attachment: SOLR-8734.patch Simplified/Tweaked proposed patch a little. > fix deprecation warnings for absent (maxMergeDocs|mergeFactor) > -- > > Key: SOLR-8734 > URL: https://issues.apache.org/jira/browse/SOLR-8734 > Project: Solr > Issue Type: Bug >Affects Versions: 5.5, master >Reporter: Christine Poerschke >Assignee: Christine Poerschke > Attachments: SOLR-8734.patch, SOLR-8734.patch > > > [~markus17] wrote on the solr-user mailing list: > bq. 5.5.0 SOLR-8621 deprecation warnings without maxMergeDocs or mergeFactor > ... > bq. o.a.s.c.Config Beginning with Solr 5.5, is deprecated, > configure it on the relevant instead. > ... > bq. On my development machine for all cores. None of the cores has either > parameter configured. Is this expected? > ... > [~cpoerschke] replied: > ... > bq. Could you advise if/that the solrconfig.xml has a element > (for which deprecated warnings would appear separately) or that the > solrconfig.xml has no element? > ... > bq. If either is the case then yes based on the code > (SolrIndexConfig.java#L153) the warnings would be expected-and-harmless > though admittedly are confusing, and fixable. > ... -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
