Skip to content
New issue

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

Simply orchestation configuration #1328

Closed
3 of 5 tasks
tristaZero opened this issue Oct 9, 2018 · 0 comments
Closed
3 of 5 tasks

Simply orchestation configuration #1328

tristaZero opened this issue Oct 9, 2018 · 0 comments
Assignees

Comments

@tristaZero
Copy link
Contributor

tristaZero commented Oct 9, 2018

Feature Request

For English only, other languages will not accept.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot make decision by current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Delete type configuration for orchestration, and distinguish sharding or ms through sharding rule and master-slave rule. Therefore, user will not need to care about type.

  • Check type configuration for sharding proxy.
  • Check type configuration for sharding jdbc.
  • Consider remove type configuration for orchestration.
  • Check configuration domain modules.
  • Make proxy's configuration in registry consistent with jdbc's.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants