DURACLOUD-1268: refactor the RetrievalTool to create full list of contentIds, including chunked content, when a list-file is used #143
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.
This PR changes the DuraStoreSpecifiedRetrievalSource class so that when a list-file is specified it creates a full list of contentIds to be retrieved, including any chunked content of files in the list-file.
JIRA Ticket: https://duracloud.atlassian.net/browse/DURACLOUD-1268
What does this Pull Request do?
This PR changes the class used by the RetrievalTool when a list-file is specified to work more like the default behavior when retrieving a space. As as result of this change, the two classes can now retrieve content with the same function. This PR resolves the case where the RetrievalTool with a list-file specified fails to transfer when restarting from partially chunked files.
How should this be tested?
Interested parties
@duracloud/committers