Skip to content

MultipleFileDownload does not provide a getSubTransfers() method #785

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
c-n-d opened this issue Jul 22, 2016 · 2 comments
Closed

MultipleFileDownload does not provide a getSubTransfers() method #785

c-n-d opened this issue Jul 22, 2016 · 2 comments
Labels
feature-request A feature should be added or improved.

Comments

@c-n-d
Copy link

c-n-d commented Jul 22, 2016

Hi Team,

The MultipleFileUpload interface defines a method for accessing the underlying transfers:

public Collection<? extends Upload> getSubTransfers();

getSubTransfers() is implemented by MultipleFileUploadImpl:

public Collection<? extends Upload> getSubTransfers() {
    return Collections.unmodifiableCollection(subTransfers);
}

MultipleFileDownload does not seem to define an analogous method. Is it possible to otherwise access the SubTransfers of MultipleFileDownload and if not, would it be possible to add getSubTransfers() to MultipleFileDownload?

public Collection<? extends Download> getSubTransfers();

Is there a recommended way of accessing the SubTransfers of MultipleFileDownload (specifically key and version of each downloaded object)?

@c-n-d c-n-d changed the title MultipleFileDownload does not provide a getSubTransfers() MultipleFileDownload does not provide a getSubTransfers() method Jul 22, 2016
@kiiadi kiiadi added the feature-request A feature should be added or improved. label Aug 5, 2016
@kiiadi
Copy link
Contributor

kiiadi commented Aug 5, 2016

Thanks for the feature request, if others up-vote this one we can raise the priority.

@debora-ito
Copy link
Member

Hi @c-n-d, the SDK team has reviewed the feature request list for V1, and since they're concentrating efforts on V2 new features they decided to not implement this one in V1. It's still being considered for the TransferManager refactor in V2, see the referenced issue above. I'll go ahead and close this.

Please feel free to comment on the V2 issue with your use case, and reach out if you have further questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

4 participants