You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/07/10 08:08:00 UTC
[jira] [Commented] (SOLR-14641) PeerSync, remove
canHandleVersionRanges check
[ https://issues.apache.org/jira/browse/SOLR-14641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155252#comment-17155252 ]
ASF subversion and git services commented on SOLR-14641:
--------------------------------------------------------
Commit 9562dd887a31102f86f710fd99ea53b019a85fcf in lucene-solr's branch refs/heads/jira/SOLR-14641 from Cao Manh Dat
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=9562dd8 ]
SOLR-14641: PeerSync, remove canHandleVersionRanges check
> PeerSync, remove canHandleVersionRanges check
> ---------------------------------------------
>
> Key: SOLR-14641
> URL: https://issues.apache.org/jira/browse/SOLR-14641
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
>
> SOLR-9207 introduces PeerSync with updates range which committed in 6.2 and 7.0. To maintain backward compatibility at the time we introduce an endpoint in RealTimeGetComponent to check whether a node support that feature or not.
> It served well its purpose and it should be removed to reduce complexity and a request-response trip for asking that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org