We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
从官方文档来看, 是支持Reference级别的MigrationStep配置的.
但MigrationRule会缓存首次从ConsumerURL里解析出来的migration.step. 第二个ConsumerURL进来时, 支持取的上次的解析结果. 这块有点疑惑, 是逻辑BUG 还是设计如此.
public MigrationStep getStep(URL consumerURL) { MigrationStep value = getValue(consumerURL, SubMigrationRule::getStep); if (value != null) { return value; } /** * FIXME, it's really hard to follow setting default values here. */ if (step == null) { // initial step : APPLICATION_FIRST step = MigrationStep.APPLICATION_FIRST; // 这里会缓存上次解析结果 step = Enum.valueOf(MigrationStep.class, consumerURL.getParameter(MIGRATION_STEP_KEY, getDefaultStep(consumerURL, step.name()))); } return step; }
The text was updated successfully, but these errors were encountered:
下面这块是为了设置一个默认值呀
Sorry, something went wrong.
step = Enum.valueOf(MigrationStep.class, consumerURL.getParameter(MIGRATION_STEP_KEY, getDefaultStep(consumerURL, step.name()))); 看逻辑这里才会去ReferenceConfig里获取migration.step这个参数值, 缓存之后下一个ReferenceConfig里获取的就是上个ReferenceConfig里的值了. 目前这边有个场景是部分Reference需要声明FORCE_APPLICATION, 不使用默认的APPLICATION_FIRST.
Fix in #13237
No branches or pull requests
从官方文档来看, 是支持Reference级别的MigrationStep配置的.
![image](https://private-user-images.githubusercontent.com/10057108/249990071-19a1e68c-00c1-47e2-8bda-d41eb5aafa3e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNTU2MzYsIm5iZiI6MTcyNjE1NTMzNiwicGF0aCI6Ii8xMDA1NzEwOC8yNDk5OTAwNzEtMTlhMWU2OGMtMDBjMS00N2UyLThiZGEtZDQxZWI1YWFmYTNlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTEyVDE1MzUzNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQwNzQ5YzYzZjQ1NGNmNTE0Yjk0NjgzNzBjNTUyNDZkM2QyMzNiOGE1YzNlMjM4YWI4MWZiNzY0YmFjOGQwNjgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.7Wjlbnt8q4yFhWbh3ZS5hF70RIvRa6cg9pNfPFrUmxY)
但MigrationRule会缓存首次从ConsumerURL里解析出来的migration.step. 第二个ConsumerURL进来时, 支持取的上次的解析结果. 这块有点疑惑, 是逻辑BUG 还是设计如此.
The text was updated successfully, but these errors were encountered: