Skip to content
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

IndexFeatureFile should support GCS inputs/outputs #6161

Closed
droazen opened this issue Sep 13, 2019 · 3 comments · Fixed by #6246
Closed

IndexFeatureFile should support GCS inputs/outputs #6161

droazen opened this issue Sep 13, 2019 · 3 comments · Fixed by #6246
Assignees

Comments

@droazen
Copy link
Contributor

droazen commented Sep 13, 2019

No description provided.

@droazen
Copy link
Contributor Author

droazen commented Sep 13, 2019

Requested by @yfarjoun

@droazen droazen self-assigned this Sep 13, 2019
@droazen droazen added this to the Engine-Q3-2019 milestone Sep 13, 2019
@droazen droazen assigned cmnbroad and unassigned droazen Sep 23, 2019
@droazen droazen modified the milestones: Engine-Q3-2019, GATK-Triaged-Issues Sep 23, 2019
@cmnbroad
Copy link
Collaborator

While we're at it, we're going to change the name of the input argument from -F to -I.

@ldgauthier
Copy link
Contributor

I've had to index VCFs in the cloud and it made me sad, but part of what made me sad was that I didn't have write permissions to save my index. Any chance of indexing on the fly in those cases?

lbergelson pushed a commit that referenced this issue Nov 8, 2019
#6246)

* Cloud-enable IndexFeatureFile.
* Change IndexFeatureFile to use -I instead of -F.
* Fixes #6161
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants