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

FT.Aggregate is giving extra empty row #368

Open
livinhigh opened this issue Jan 9, 2025 · 2 comments
Open

FT.Aggregate is giving extra empty row #368

livinhigh opened this issue Jan 9, 2025 · 2 comments
Assignees

Comments

@livinhigh
Copy link

Thanks for reporting an issue in NRedisStack! Please update the appropriate text below, as much data as possible really helps!

NRedisStack Version: What version of the library are you using

Redis Stack Version: What is the version of redis stack where this issue happens?

Description: Description of the issue, ideally with sample code, and a stack trace.

image

Suppose I create an index as below and add 3 docs as below:

FT.CREATE 'myIndex1' ON HASH PREFIX 1 "doc:" SCHEMA title TEXT SORTABLE body TEXT flag TEXT
HSET doc:1 title "Hello World" body "This is a test document"
HSET doc:2 title "Hello Mars" body "This is a test2 document"
HSET doc:3 flag "true"

When running below aggregate command , there is an extra empty row in the end which is incorrect i believe?
Has anything changed recently for this to happen, because I remember the extra row was not coming earlier

FT.AGGREGATE "myIndex1" "*"
LOAD 2 "title" "body"
SORTBY 2 "@title" ASC
LIMIT 0 10

image

@livinhigh livinhigh changed the title FT.Aggregate is giving extra empty rows FT.Aggregate is giving extra empty row Jan 9, 2025
@atakavci
Copy link
Collaborator

hey @livinhigh, thanks for reporting the case.
i see this is happening with Redis Insight, could you confirm if it is the same way with redis-cli ?
if yes, then the right place to report would be RediSearch repo

@atakavci
Copy link
Collaborator

atakavci commented Jan 14, 2025

BTW i think the extra row you mentioned is there due to HSET doc:3 flag "true", which seems right to me since it has no matching fields with the LOAD fields of FT.AGGREGATE.
Then again, my previous comment above still stands.
Let me know if i can provide further help.

@atakavci atakavci self-assigned this Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants