Adapt jobs for multi-valued headers in WAT data#46
Merged
Conversation
Header data from WARC and HTTP headers will become multi-valued in WAT files. That is, the value is either a string or a list of strings. Jobs reading WAT files need to be adapted to the new data format.
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.
Header data from WARC and HTTP headers will become multi-valued in WAT files. That is, the value is either a string or a list of strings. Jobs reading WAT files need to be adapted to the new data format.
See commoncrawl/ia-web-commons#18 and commoncrawl/ia-web-commons#38 for further details about multi-valued headers in WAT files.