-
Notifications
You must be signed in to change notification settings - Fork 0
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
Surfacing mcf required filters in the backend #327
Surfacing mcf required filters in the backend #327
Conversation
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.
Looks reasoanble to me. I don't think I have enough understanding of this service though!
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.
Functionally this looks great to me, and I think the tests you've added look good. I am wondering if we might need one more test in the search tests that makes sure we get metadata back? Like how we are currently doing for geographies. This would give us good confidence in this all fitting together correctly. This is good to go from my view otherwise!
A thought - add multiple geographies to test data to ensure we're ready for that as I think they're all just a list of the single geo currently. |
Definitely! I've added some more assertions for the other fields to the |
* Working commit. * Clean up. * Making populate db families deterministic. * Adding distinct deterministic and random fixtures for family metadata. --------- Co-authored-by: Mark <[email protected]>
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.
Looking good! Some minor points to make decisions on below. Nothing blocking though, good work! 👍 👍
dea39b7
to
cc3a5f8
Compare
* Move vespa search tests & the search_fixtures they use under dedicated sub-folder (#334) * Move vespa search tests under dedicated vespa folder * Move /search_fixtures under vespa search folder & rename to fixtures * Bump to 1.14.20 * Move vespa search result order tests into a separate file (#335) * Move vespa search tests under dedicated vespa folder * Move /search_fixtures under vespa search folder & rename to fixtures * Bump to 1.14.20 * Move vespa search result order tests to separate file * Bump to 1.14.19 * Move continuation token vespa search tests to separate file (#336) * Move vespa search tests under dedicated vespa folder * Move /search_fixtures under vespa search folder & rename to fixtures * Bump to 1.14.20 * Move vespa search result order tests to separate file * Bump to 1.14.19 * Move vespa search continuation token tests to separate file * Group pagination and continuation token tests * Move keyword and range vespa search tests into separate file (#337) * Move vespa search tests under dedicated vespa folder * Move /search_fixtures under vespa search folder & rename to fixtures * Bump to 1.14.20 * Move vespa search result order tests to separate file * Bump to 1.14.19 * Move vespa search continuation token tests to separate file * Move keyword and range vespa search tests into separate file * Delete test_vespa_search_cont_tokens.py * Move _make_search_request into vespa search setup * Move vespa search tests for ignoring special chars & case to separate file (#338) * Move data download tests into parent folder * Move query insensitivity & special chars ignoring tests out * Rename from test_vespasearch * Bump to 1.14.20 * Removing refactored file. * Adding back in the changes from the test_vespasearch. --------- Co-authored-by: Katy Baulch <[email protected]> Co-authored-by: Mark <[email protected]>
Description
This pull request surfaces changes made to the
cpr_sdk
to support filtering for theMCF
corpus data.SearchResponseFamily
object.geography
togeographies
.cpr_sdk
version to contain the new queries.Note:
We can't test for the
corpus_type_name
orcorpus_import_id
in the search response as it isn't included in the object.Do we want this as part of this PR or as part of future work?
Proposed version
Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.
Visit the Semver website to understand the
difference between
MAJOR
,MINOR
, andPATCH
versions.Notes:
used -- e.g. Major > Minor > Patch
sure your selected option is marked
[x]
with no spaces in between thebrackets and the
x
Type of change
Please select the option(s) below that are most relevant:
How Has This Been Tested?
Please describe the tests that you added to verify your changes.
Reviewer Checklist