[
https://issues.apache.org/jira/browse/SOLR-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042475#comment-13042475
]
Robert Muir commented on SOLR-2567:
-----------------------------------
Anyway, I'm interested in what others think the right thing to do here is... we
can bring it to the dev@ list if it will grab more attention.
the choices to me seem to be:
# release 3.2 as is, enable TieredMergePolicy in 3.3, using luceneMatchVersion
>= 3.3
# release 3.2 as is, enable TieredMergePolicy in 3.3, just changing the default
completely.
# respin and use this patch, with TieredMergePolicy defaulted on for
luceneMatchVersion >= 3.2 (consistent with lucene), but you don't have total
configuration over all its settings (just mergefactor and compoundfile).
# respin like the above, but also quickly try to add support for
MergePolicyFactory or similar, so that all tieredMP settings are exposed
and maybe there are other ideas I haven't mentioned.
> 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: [email protected]
For additional commands, e-mail: [email protected]
