Skip to content

Conversation

@hwware
Copy link
Member

@hwware hwware commented Aug 26, 2025

Add more fields to align with RedisSearch output
Highlight part is what i add in this PR

image

@hwware hwware force-pushed the ft-info-more-field branch from 2d5451e to 55b8ed4 Compare August 26, 2025 15:16
@hwware hwware force-pushed the ft-info-more-field branch from 55b8ed4 to 5c262d3 Compare August 26, 2025 15:45
@murphyjacob4
Copy link
Collaborator

Discussed in weekly meeting. We need to decide whether it makes sense to add dummy fields (which could silently break client-side logic) or if it makes sense to only add fields where we have some value and let customer apps break with syntactical parsing errors if they rely on such FT.INFO fields

Copy link
Collaborator

@yairgott yairgott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please follow the guidance: https://github.com/valkey-io/valkey-search/wiki/Weekly-meeting-2025-09-03#guidance-for-valkey-search-info-fields

FWIW, for most of these added fields with dummy values, the real values are either already captured or it's fairly easy to capture these values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants