Skip to content

RediSearch support (part 1 of 3) #3325

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

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

Conversation

tishun
Copy link
Collaborator

@tishun tishun commented Jun 16, 2025

Provide basic support for RediSearch

This implementation will provide support for:

Make sure that:

  • You have read the contribution guidelines.
  • You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
  • You applied code formatting rules using the mvn formatter:format target. Don’t submit any formatting related changes.
  • You submit test cases (unit or integration tests) that back your changes.

tishun and others added 3 commits June 5, 2025 18:58
* Add support for FT.DROPINDEX redis#2722

* Polishing
Vibe code the FT.SEARCH command
Pulled latest from the integration branch

Fixed a lot of the hallucinations

RESP2 parser improvements

JSON Indexing tests

Add some advanced use-cases

Fixed all integration tests

Fixed schema fields, added vector tests, but they are all failing

Fixed vector search tests

Improve coverage of integration and unit tests

One unit test fails
@tishun tishun force-pushed the feature/redisearch branch from 46080a3 to ab76b4b Compare June 16, 2025 15:57
tishun added 3 commits June 18, 2025 15:10
Fixing the integration tests for FT.AGGREGATE

Polishing 1/3

Add more documentation ot the AggregateArgs
Add Integration tests for the FT.CURSOR

Add RESP2 tests for all aggragation integration tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant