Skip to content

Promote the RQE APIs to production #3566

@tishun

Description

@tishun

Feature Request

The Redis Query Engine APis in the RedisSearchCommands hierarchy is marked with the @Experimental

Is your feature request related to a problem? Please describe

Keeping the API in this mode would drastically reduce adoption.
It would also prevent us from adopting it in other upstream drivers.

Describe the solution you'd like

We need to promote the API after polishing it one last time.
Here is a list of items we should consider polishing out:
[ ] Consider having a similar API structure for FT.AGGREGATE and FT.HYBRID
[ ] Consider the implications of large data in the results and late parsing / decoding
[ ] etc.

Describe alternatives you've considered

N/A

Teachability, Documentation, Adoption, Migration Strategy

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: improvementAn improvement to the existing implementation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions