use csv instead of json for DMR to avoid data timeouts#139
Merged
bl-young merged 2 commits intorelease-v1.1.0from Jun 16, 2023
Merged
use csv instead of json for DMR to avoid data timeouts#139bl-young merged 2 commits intorelease-v1.1.0from
bl-young merged 2 commits intorelease-v1.1.0from
Conversation
…names accordingly; drop need to query by sic - no max error
Contributor
Author
Contributor
Author
|
@WesIngwersen just alerting you to this change in how DMR is processed |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Following issues with the actions not being able to complete the generation of DMR data, recommendation from data source experts is to use CSV which can be processed more efficiently. Time requirements are greatly reduced as well. No change in data products expected from this change.