Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lack of Isolation Between HyperLogLog and String Types #2719

Closed
saz97 opened this issue Jun 11, 2024 · 0 comments
Closed

Lack of Isolation Between HyperLogLog and String Types #2719

saz97 opened this issue Jun 11, 2024 · 0 comments
Labels
☢️ Bug Something isn't working

Comments

@saz97
Copy link
Contributor

saz97 commented Jun 11, 2024

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

截图_20240611_170217_954

Please provide the version you discovered this bug in (check about page for version information)

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
☢️ Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants