This repository was archived by the owner on May 8, 2024. It is now read-only.
HySDS uses a new method of publushing datasets #100
Conversation
This file contains hidden or 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
uses new grq2 endpoint
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
related PR(s):
related HySDS core ticket: https://hysds-core.atlassian.net/browse/HC-376
Purpose
HySDS uses a new method of publishing datasets, using the ES bulk API and does proper rollback when publishing fails
it uses v2 of the grq2 dataset index endpoint so it needs to be configured in
celeryconfig.pyProposed Changes
GRQ_UPDATE_URL_BULK = "http://grq2:8878/api/v0.2/grq/dataset/index"toceleryconfig.pyIssues
Testing
tested it on NISAR in our dev-e2e test