Code-Fight commented on issue #846:
URL:
https://github.com/apache/incubator-seata-go/issues/846#issuecomment-3007138106
> Is it different from constructing lock keys here? I remember converting
upper case in getmeata for lock key uniqueness. Is it necessary to convert it
before constructing lock keys instead of putting it in a unified function?
There are two issues:
1. When retrieving metadata, the tableName passed from the user
side should be used as-is, instead of converting it to uppercase.
2. After being stored in metaCache, all table names are in
uppercase, which results in the loss of the original actual table name. This
causes automatic refresh to fail (for example, the original name was in
lowercase, but the key in the cache is in uppercase).
有两个问题。
1.获取meta时，应该使用用户侧传过来的tableName，而不是转为大写的。
2.存入到metaCache后，都是大写的，丢失了原来的实际tablename，导致自动刷新，无法生效（比如原来是小写，但是cache里面的key是大写的）
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
