tristaZero edited a comment on issue #7703: URL: https://github.com/apache/shardingsphere/issues/7703#issuecomment-723738957
> The title of the issue can be misleading. +1, however, users may locate this issue by the concrete exception info, I guess. Besides, as I said above, `updating sharding key` (comes with row migration) is supposed to be one of the capabilities for a perfect distributed database solution. Unfortunately, SS can not has better support for it but is moving towards it at present. Hence, we can solve this issue by having users add an annotation for JPA and avoid this exception by [digesting some cases](https://github.com/apache/shardingsphere/issues/7703#issuecomment-716284082) inside SS. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
