[
https://issues.apache.org/jira/browse/SOLR-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688190#comment-13688190
]
Uwe Schindler commented on SOLR-4934:
-------------------------------------
bq. Assuming there are plenty of file descriptors available, will a user get
better performance from compound files or separate files?
Searching on the index will have no negative impact. IndexInputSlicer returns
optimized indexinputs that remove the whole file offset stuff. Indexing speed
is identical, too, but merging (done in background) is more expensive.
> Prevent runtime failure if users use initargs "useCompoundFile" setting on
> LogMergePolicy or TieredMergePolicy
> --------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4934
> URL: https://issues.apache.org/jira/browse/SOLR-4934
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 5.0, 4.4
>
>
> * LUCENE-5038 eliminated setUseCompoundFile(boolean) from the built in
> MergePolicies
> * existing users may have configs that use <mergePolicy> init args to try and
> call that setter
> * we already do some explicit checks for these MergePolices in
> SolrIndexConfig to deal with legacy syntax
> * update the existing logic to remove "useCompoundFile" from the MergePolicy
> initArgs for these known policies if found, and log a warning.
> (NOTE: i don't want to arbitrarily remove "useCompoundFile" from the initArgs
> regardless of class in case someone has a custom MergePolicy that implements
> that logic -- that would suck)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
