[
https://issues.apache.org/jira/browse/SOLR-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042471#comment-13042471
]
Robert Muir commented on SOLR-2567:
-----------------------------------
{quote}
Then I saw that there would be some side affects to that based on this patch? I
didn't really look closely, but from memory, I guess it would disable being
able to set compound file? And you wouldn't be able to change the tiered
policies settings? Or does Solr's config any given method voodoo work in this
case?
{quote}
Right, this is definitely a downside to not having this patch, they cannot set
compoundFile or mergeFactor.
And you are also right about tiered policy settings... you will notice I didn't
actually enable these in the patch. I guess thats because I thought it would be
confusing to add "MP-specific" settings all piled in to the config. I was
planning on opening another issue for this to allow for a factory configuration
like other things, especially so I can pass a 'long' random seed so that tests
can use MockRandomMergePolicy :)
> 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]
