Skip to content

Support for TYPE parameter of SCAN command #2089

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

Closed
Jamby93 opened this issue Jun 17, 2021 · 0 comments
Closed

Support for TYPE parameter of SCAN command #2089

Jamby93 opened this issue Jun 17, 2021 · 0 comments
Assignees
Labels
type: enhancement A general enhancement

Comments

@Jamby93
Copy link

Jamby93 commented Jun 17, 2021

As of #1559 (for Lettuce) and #2564 (for Jedis) TYPE parameter in SCAN commands is supported by both clients.
Lettuce supports it with KeyScanArgs while Jedis simply added an additional parameter to their scan commands.
ScanOptions currently does not offer the type field and I couldn't find a way to perform this type of SCAN without directly accessing the underneath repositories.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jun 17, 2021
@mp911de mp911de added type: enhancement A general enhancement status: ideal-for-contribution An issue that a contributor can help us with and removed status: waiting-for-triage An issue we've not yet triaged labels Jun 21, 2021
@mp911de mp911de self-assigned this Jul 1, 2021
@mp911de mp911de removed the status: ideal-for-contribution An issue that a contributor can help us with label Jul 1, 2021
mp911de added a commit that referenced this issue Jul 1, 2021
We now support the type argument for Keyspace scanning through KeyScanOptions.type.

Closes #2089
@christophstrobl christophstrobl added this to the 2.6 M1 (2021.1.0) milestone Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants