`SMISMEMBER` is a unknown command for `ConnectionSplittingInterceptor`

[SunghyunKim9744]

Spring-data-redis 2.7.12를 사용하고 있습니다. Transactional을 활성화 했을 때, SMISMEMBER가 RedisCommand에 등록되지 않아서, Read Command임에도 RedisCommand.UNKOWN을 반환해서 결과 값으로 null을 반환합니다. (RedisConnectionUtils > ConnectionSplittingInterceptor > intercept Method)

[SunghyunKim9744]

RedisTemplate.opsForSet().isMember(K key, Object... objects) 호출 시, Issue와 같은 문제가 발생합니다.

[mp911de]

Thanks for the report. Please note that this issue tracker communication is English. Below is the translated description:

I'm using Spring-data-redis 2.7.12. When Transactional is enabled, SMISMEMBER isn't registered with RedisCommand, so even though it's a read command, it returns RedisCommand.UNKOWN, which returns null as the result value. (RedisConnectionUtils > ConnectionSplittingInterceptor > intercept Method)

[christophstrobl]

Thank you @SunghyunKim9744. The SMISMEMBER command is recognized as such and executed returning the expected result. Unfortunately it seems the result is dismissed right after when adding conversion for future results for string based redis connections.

[SunghyunKim9744]

Thank you @christophstrobl
SMISMEMBER는 RedisCommand에 등록되지 않아서 queue로 들어가고 있습니다. SISMEMBER는 RedisCommand에 있어서 queue로 들어가지 않고, 별도의 Connection에서 즉시 조회가 가능한게 아닌가요?