feature/es-phase-1 #3648
Draft
feature/es-phase-1 #3648
+3,343
−155
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
…sic queries (#3637) * CUMULUS-3692:Granule list endpoint for basic postgres query
…er by field value (#3656) * CUMULUS-3692:Granule list endpoint for basic postgres query * refactor * refactor * typing * add changelog entry * skip search_after * skip searchafter unit tests * add granule list test * rename * refactor * build query parameters * update comment * add field-mapping * update jsdoc * use type over interface,add log * update test description * build term/terms * buildDbQueryParameters * add unit test no terms search * add doc * rename * add unit test * add fields test * add more unit tests * support error.Error search * fix lint * rename functions * ignore files * add convert query unit tests * add all types * add unit test for fieldmapping types fix timestamp * update timestamp test * add multiple term field test * ignore execution in granule list record
…se psql (#3659) * first commit on new branch * CHANGELOG change * small fix * PR feedback * adding jsdoc + fixing spelling/grammar
#3660) * add range query support
* first committ * CHANGELOG change * fixing sortQueryMethod * simplifying code * PR feedback * merge conflicts + improving code * small jsdoc fix * PR feedback * PR feedback * PR feedback * fixing test * PR feedback * PR feedback
#3674) * add methods to convert terms,not,exists
| @@ -101,19 +101,12 @@ function _createNewGranuleDateValue() { | |||
| * @returns {Promise<Object>} the promise of express response object | |||
| */ | |||
| async function list(req, res) { | |||
| log.trace(`list query ${JSON.stringify(req.query)}`); | |||
There was a problem hiding this comment.
@Jkovarik mentioned that we generally use log.info, and using log.trace is a change to how we're logging so should be discussed with the team.
see convo https://github.com/nasa/cumulus/pull/3681/files#diff-c8cc016ab2b04a286a25bb2d230e35fe63392b371a4178296f58f6388936d72c
Is there a reason to use log.trace instead of log.info?
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.
Summary: Summary of changes
Addresses CUMULUS-XX: Develop amazing new feature
Changes
PR Checklist