lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-2567) Solr should default to TieredMergePolicy
Date Wed, 01 Jun 2011 21:48:47 GMT

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

Mark Miller commented on SOLR-2567:
-----------------------------------

My initial reaction was it was not worth re-spinning for this either. But mostly based on
the assumption that the user could just configure it, and at worst we could drop a note about
it.

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?

Either way, I'd be fine if we didn't respin or if we did. It would still be an improvement,
even if it didn't support compound, and then that can be another improvement.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message