This problem is tracked in FLINK-11141 <https://issues.apache.org/jira/browse/FLINK-11141>, but there is not a solution yet considering the state compatibility. Have you encountered the problem in production?
Zen4YYDS <gafam...@163.com> 于2021年11月25日周四 下午3:30写道： > Hi devs: > > Using RocksDB, when key and namespace both have variable binary > length, to prevent [key, namespace] have equal binary number, we add key > length and namespace length after key and namespace respectively. Then the > format is: > Keygroup – key -keyLength– namespace-namespaceLenth > > Then what about we use a fixed length key and variable length > namespace and userkey. In current implement, I found the binary key format > is as below: > > Keygroup – key – namespace- userkey > > Think about following situation, I think we may get the same value for > different [namespace, userkey]. or I get something wrong? > > Keygroup key namespace userkey > 1 1 11 1 > 1 1 1 11 > > > 从 Windows 版邮件发送 > >
