[
https://issues.apache.org/jira/browse/SOLR-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128957#comment-15128957
]
Shai Erera commented on SOLR-8621:
----------------------------------
bq. my outlook currently is that all the master-solr-8621 history would be
squashed 'at the end' and going back to 'master' there would be just a single
commit. How does that sound
That sounds just like I would prefer it to happen, so glad to see we're in
agreement here. Just FYI, it would have been easier to do this squash if you
rebased master-solr-8621 on origin/master. Then all our commits would stack on
top of each other.
We can still do this though, but I think we'd need to cherry-pick all commits
there into a separate local branch, and then squash. Not sure it matters much
now though. I don't mind doing the final "commit" after we finish iterating on
the changes.
> solrconfig.xml: deprecate/replace <mergePolicy> with <mergePolicyFactory>
> -------------------------------------------------------------------------
>
> Key: SOLR-8621
> URL: https://issues.apache.org/jira/browse/SOLR-8621
> Project: Solr
> Issue Type: Task
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
>
> *<mergePolicyFactory> end-user benefits:*
> * Lucene's UpgradeIndexMergePolicy can be configured in Solr
> * (with SOLR-5730) Lucene's SortingMergePolicy can be configured in Solr
> * customisability: arbitrary merge policies including wrapping/nested merge
> policies can be created and configured
> *(proposed) roadmap:*
> * solr 5.5 introduces <mergePolicyFactory> support
> * solr 5.5(\?) deprecates (but maintains) <mergePolicy> support
> * solr 6.0(\?) removes <mergePolicy> support
> +work-in-progress git branch:+
> [master-solr-8621|https://github.com/apache/lucene-solr/tree/master-solr-8621]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
