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

Arbitrary file endings for mapped resources #127

Open
mmalenic opened this issue Dec 23, 2022 · 0 comments
Open

Arbitrary file endings for mapped resources #127

mmalenic opened this issue Dec 23, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@mmalenic
Copy link
Member

Feature

After mapping a query ID, a file is fetched by appending the file extension based on the query format. For example, a Bam query must have files ending with .bam and their index files must end with .bam.bai. It would be good to allow arbitrary file endings so that files for a given format do not need to be bound to a particular ending.

Motivation

This would be useful for decoupling the location of a file and its index, so that they do not need to be in the same location, or for supporting a storage backend that may not require file endings.

Implementation

A config option could be added that allows setting the file endings for file formats. Or, a query ID could be resolved directly to a file and its index, by having two substitution strings - one for the target file, and one for the index.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants