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

shadow-raw-jdbc-example org.apache.shardingsphere.example.shadow.raw.jdbc.config.ShadowDefaultAlgorithmConfiguration defaultShadowAlgorithmName spell mistake #17697

Closed
grapeqin opened this issue May 16, 2022 · 1 comment · Fixed by #17751
Assignees
Milestone

Comments

@grapeqin
Copy link

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

5.1.1

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-JDBC

Expected behavior

when I run org.apache.shardingsphere.example.shadow.raw.jdbc.ShadowRawJavaConfigurationExample example,choose
private static ShardingType shardingType = ShardingType.SHADOW_DEFAULT_ALGORITHM;

Actual behavior

it shows:
image

Reason analyze (If you can)

I found when we set defaultShadowAlgorithmName simple-note-algorithm in method of createShadowRuleConfiguration (from line #51 in org.apache.shardingsphere.example.shadow.raw.jdbc.config.ShadowDefaultAlgorithmConfiguration )

but in method of createShadowAlgorithmConfigurations we put simple-hint-algorithm,so I think who spell mistake.

I try to modify set defaultShadowAlgorithmName simple-hit-algorithm in method of createShadowRuleConfiguration,then it works.

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

@soulasuna
Copy link
Contributor

I will fix it.
Please assign to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants