fix: behavior of Elasticsearch query differs from mongoDB query #1184
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 refines the Elasticsearch integration by updating the dataset field mappings, improving the query-building service, and ensuring that the logic is more intuitive and maintainable. The changes are aimed at enhancing the search functionality, ensuring better performance, and providing more accurate search results.
Motivation
The purpose of this PR is to enhance the Elasticsearch configuration and query-building logic to improve the flexibility and accuracy of search queries. This includes updating field mappings, refining the query-building service, and ensuring better alignment with the new requirements for data filtering and querying.
Fixes:
Changes:
Field Mapping Updates (datasetFieldMapping.ts):
Elasticsearch Service (elastic-search.service.ts):
Enums Update (fields.enum.ts):
Query Builder Service (query-builder.service.ts):
Tests included/Docs Updated?