You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/07/08 09:47:16 UTC
[GitHub] [shardingsphere] doveylovey opened a new issue, #18963: When using JPA, and in the absence of transaction management, the select is routed to the write-ds
doveylovey opened a new issue, #18963:
URL: https://github.com/apache/shardingsphere/issues/18963
## Bug Report
**For English only**, other languages will not accept.
Before report a bug, make sure you have:
- Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues).
- Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview).
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?
v5.1.2
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
### Expected behavior
When using JPA, and in the absence of transaction management, the select is routed to the write-ds, why not the read-ds?
### Actual behavior
### Reason analyze (If you can)
### 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).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] github-actions[bot] commented on issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #18963:
URL: https://github.com/apache/shardingsphere/issues/18963#issuecomment-1272349428
Hello , this issue has not received a reply for several days.
This issue is supposed to be closed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] doveylovey commented on issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
Posted by GitBox <gi...@apache.org>.
doveylovey commented on issue #18963:
URL: https://github.com/apache/shardingsphere/issues/18963#issuecomment-1179851679
@[terrymanu](https://github.com/terrymanu) Hello, can you take a look at this problem? I need some help, thank you
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] doveylovey commented on issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
Posted by GitBox <gi...@apache.org>.
doveylovey commented on issue #18963:
URL: https://github.com/apache/shardingsphere/issues/18963#issuecomment-1182649477
> Your application framework is too complicated, can you provide the code to reproduce it?
This is an example given in the project, located at:
https://github.com/apache/shardingsphere/blob/master/examples/shardingsphere-jdbc-example/single-feature-example/readwrite-splitting-example/readwrite-splitting-spring-boot-jpa-example/src/main/java/org/apache/shardingsphere/example/readwrite/splitting/spring/boot/jpa/ReadwriteSplittingSpringBootJpaExample.java
https://github.com/apache/shardingsphere/blob/master/examples/shardingsphere-jdbc-example/single-feature-example/readwrite-splitting-example/readwrite-splitting-spring-namespace-jpa-example/src/main/java/org/apache/shardingsphere/example/readwrite/splitting/spring/namespace/jpa/ReadwriteSplittingSpringNamespaceJpaExample.java
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] github-actions[bot] closed issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
Posted by GitBox <gi...@apache.org>.
github-actions[bot] closed issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
URL: https://github.com/apache/shardingsphere/issues/18963
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] terrymanu commented on issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #18963:
URL: https://github.com/apache/shardingsphere/issues/18963#issuecomment-1182013634
Your application framework is too complicated, can you provide the code to reproduce it?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] RaigorJiang commented on issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
Posted by "RaigorJiang (via GitHub)" <gi...@apache.org>.
RaigorJiang commented on issue #18963:
URL: https://github.com/apache/shardingsphere/issues/18963#issuecomment-1407562986
This is because of a feature at the time:
There are write operations on the same connection, and subsequent reads are also routed to write ds for consistency.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [shardingsphere] RaigorJiang closed issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
Posted by "RaigorJiang (via GitHub)" <gi...@apache.org>.
RaigorJiang closed issue #18963: When using JPA, and without transaction management, the select is routed to the write-ds, why not the read-ds?
URL: https://github.com/apache/shardingsphere/issues/18963
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org