You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a string key is set and subsequently accessed with the PFCOUNT command (which is meant for HyperLogLog), the system returns a count, indicating that the two data types are not isolated. This occurs because the type in the value format for both string and HyperLogLog is the same, as shown in the attached image.
The root of the problem is that the type field in the value format for both string and HyperLogLog is the same.
value format of String and Hyperloglog:
| type | value | reserve | cdate | timestamp |
| 1B | | 16B | 8B | 8B |
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is this a regression?
Yes
Description
When a string key is set and subsequently accessed with the PFCOUNT command (which is meant for HyperLogLog), the system returns a count, indicating that the two data types are not isolated. This occurs because the type in the value format for both string and HyperLogLog is the same, as shown in the attached image.
The root of the problem is that the type field in the value format for both string and HyperLogLog is the same.
value format of String and Hyperloglog:
| type | value | reserve | cdate | timestamp |
| 1B | | 16B | 8B | 8B |
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: