-
Notifications
You must be signed in to change notification settings - Fork 399
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
[BUGFIX] argilla-server
: Query on response values without an user
#5003
Merged
frascuchon
merged 7 commits into
feat/v2.0.0
from
bugfix/argilla-server/query-on-response-values-without-an-user
Jun 13, 2024
Merged
[BUGFIX] argilla-server
: Query on response values without an user
#5003
frascuchon
merged 7 commits into
feat/v2.0.0
from
bugfix/argilla-server/query-on-response-values-without-an-user
Jun 13, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feat/v2.0.0 #5003 +/- ##
================================================
+ Coverage 61.07% 92.02% +30.94%
================================================
Files 328 135 -193
Lines 17645 5829 -11816
================================================
- Hits 10777 5364 -5413
+ Misses 6868 465 -6403
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This reverts commit 6826d71.
jfcalvo
approved these changes
Jun 12, 2024
frascuchon
deleted the
bugfix/argilla-server/query-on-response-values-without-an-user
branch
June 13, 2024 07:58
frascuchon
added a commit
that referenced
this pull request
Jul 4, 2024
…g response values without user (#5159) # Description <!-- Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. --> This PR fixes missing `await` call included in #5003 **Type of change** <!-- Please delete options that are not relevant. Remember to title the PR according to the type of change --> - Bug fix (non-breaking change which fixes an issue) **How Has This Been Tested** <!-- Please add some reference about how your feature has been tested. --> **Checklist** <!-- Please go over the list and make sure you've taken everything into account --> - I added relevant documentation - follows the style guidelines of this project - I did a self-review of my code - I made corresponding changes to the documentation - I confirm My changes generate no new warnings - I have added tests that prove my fix is effective or that my feature works - I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR includes a temporal workaround to fix searching records when filtering with response values without providing any user.
The solution uses index mapping to identify field paths to use in the query. Those fields are combined into a single bool query with an OR (should) operator.
Type of change
(Please delete options that are not relevant. Remember to title the PR according to the type of change)
How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference
tests
)Checklist
CHANGELOG.md
file (See https://keepachangelog.com/)