[
https://issues.apache.org/jira/browse/SOLR-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042426#comment-13042426
]
Yonik Seeley commented on SOLR-2567:
------------------------------------
bq. the patch currently adjusts the default based on luceneMatchVersion, but
this is confusing if we release 3.2 that "disagrees" with lucene's actual 3.2
defaults.
I don't think all of Solr's defaults need to match Lucene's defaults in general
- we can take it on a case-by-case basis. In this case, a TieredMergePolicy
default certainly does make sense. I'm not even sure it needed to be linked to
luceneMatchVersion... it's a rare solr user that would depend on the specifics
of merging or docid behavioral changes.
> Solr should default to TieredMergePolicy
> ----------------------------------------
>
> Key: SOLR-2567
> URL: https://issues.apache.org/jira/browse/SOLR-2567
> Project: Solr
> Issue Type: Bug
> Components: update
> Reporter: Robert Muir
> Fix For: 3.3, 4.0
>
> Attachments: SOLR-2567.patch, SOLR-2567.patch
>
>
> even if we set a luceneMatchVersion to >= 3.2 (SOLR-2557),
> Solr still defaults to LogByte
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
