design of selection strategy

[AkashKumar7902]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• N
• Y

fix: #269

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

[coveralls]

Pull Request Test Coverage Report for Build 8337308773

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 41.407%

---

Totals
Change from base Build 8322161610:	0.0%
Covered Lines:	1730
Relevant Lines:	4178

---

💛 - Coveralls

[AkashKumar7902]

@zong-zhe Please take a look !

[Peefy]

I think this design LGTM. Can you sign the DCO? We may merge at an appropriate time.

Besides, @zong-zhe, do you have any more suggestions and additions?

[zong-zhe]

@AkashKumar7902 😄

LGTM, maybe you need to squash commits into one and sign the DCO with the one commit.

[AkashKumar7902]

@zong-zhe done!

[Peefy]

LGTM