## What is the purpose of the change

Fix the issue#1293. Provide user-define strategy to get `ReferenceConfig` from 
`ReferenceConfigCache`.

## Brief changelog

Add methods in ReferenceConfigCache.KeyGenerator .

## Verifying this change

three methods that user can implement.
```
String generateKey(String[] keys);
String[] mapReferenceConfigToCustomKeys(ReferenceConfig<?> referenceConfig);
ReferenceConfig mapCustomKeysToReferenceConfig(String[] keys);
```
If user implements these method then the method 
`ReferenceConfigCache#get(java.lang.String[])` can be used.

Follow this checklist to help us incorporate your contribution quickly and 
easily:

- [x] Make sure there is a 
[GITHUB_issue](https://github.com/apache/incubator-dubbo/issues) filed for the 
change (usually before you start working on it). Trivial changes like typos do 
not require a GITHUB issue. Your pull request should address just this issue, 
without pulling in other changes - one PR resolves one issue.
- [ ] Format the pull request title like `[Dubbo-XXX] Fix UnknownException when 
host config not exist #XXX`. Each commit in the pull request should have a 
meaningful subject line and body.
- [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
- [ ] Write necessary unit-test to verify your logic correction, more mock a 
little better when cross module dependency exist. If the new feature or 
significant change is committed, please remember to add integration-test in 
[test module](https://github.com/apache/incubator-dubbo/tree/master/dubbo-test).
- [x] Run `mvn clean install -DskipTests` & `mvn clean test-compile 
failsafe:integration-test` to make sure unit-test and integration-test pass.
- [ ] If this contribution is large, please follow the [Software Donation 
Guide](https://github.com/apache/incubator-dubbo/wiki/Software-donation-guide).


[ Full content available at: 
https://github.com/apache/incubator-dubbo/pull/2380 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to