[
https://issues.apache.org/jira/browse/SCB-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liubao resolved SCB-2806.
-------------------------
Resolution: Fixed
> disable OperationInstancesDiscoveryFilter by defalut
> ----------------------------------------------------
>
> Key: SCB-2806
> URL: https://issues.apache.org/jira/browse/SCB-2806
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Java-Chassis
> Reporter: liubao
> Assignee: liubao
> Priority: Major
> Fix For: java-chassis-2.9.0
>
>
> Why:
> This filter is used for below scenarios:
> 1. consumer invoke provider, and provider has v1 and v2 two versions. v1
> has operation o1, v2 has operations o1, o2(v2 add a new operation). Consumers
> invoke both o1 and o2.
> 2. If OperationInstancesDiscoveryFilter enabled, when consumer invoke o1,
> the request will dispatch to v1, and invoke o2, the request will dispatch to
> both v1 and v2.
>
> This solution is redundant in many real application. Because real application
> will upgrade providers first and then consumer. And this solution will depend
> a lot with service center and swagger registration. If the service center do
> not support this, it will fail.
>
> For future multi service center support, and reduce the effort to support
> multi service center, we will disable OperationInstancesDiscoveryFilter by
> default. And may remove this feature in 3.0.0.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
