-
Notifications
You must be signed in to change notification settings - Fork 990
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
fix(search_family): Remove the output of extra fields in the FT.AGGREGATE command #4231
fix(search_family): Remove the output of extra fields in the FT.AGGREGATE command #4231
Conversation
8affbf7
to
c108b12
Compare
}; | ||
} | ||
|
||
PipelineResult Process(std::vector<DocValues> values, absl::Span<const PipelineStep> steps) { | ||
PipelineResult Process(std::vector<DocValues> values, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please put your prod-duty hat, and think about all the VLOG statements you would like to have, if we have problems in production with this code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return result; | ||
values = std::move(result.value()); | ||
PipelineResult step_result = step(std::move(result)); | ||
result = std::move(step_result); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to see step method modifying the result instead of all these moves
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean that we need to refactor this logic and have something like Aggregator
that stores current result and has methods like DoSort
, DoReduce
? Or use pointer here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about this question? to refactor steps and modify the result instead of moving it every time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I spoke about it today. I'm finalizing it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you going to create another PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think that it would be better to create another PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also for logs that Roman mentioned, because we first need to refactor the code before adding the logs in the appropriate places
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…GATE command fixes dragonflydb#4230 Signed-off-by: Stepan Bagritsevich <[email protected]>
Signed-off-by: Stepan Bagritsevich <[email protected]>
c108b12
to
49718c1
Compare
Just fixed the nit |
If you address comments please do an additional commit instead of amend and force push, because it's easier to review. |
fixes #4230
First PR for complete support of the SORTBY option (#3631)
To see examples please check the issue.
Add code that checks, during aggregate steps, what fields should be printed.