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

Add arbitrary field indexing on gff3tabix tracks ref #1115 #1222

Merged
merged 5 commits into from Oct 9, 2018

Conversation

Projects
None yet
3 participants
@cmdcolin
Copy link
Contributor

cmdcolin commented Oct 4, 2018

If the config item "nameAttributes" is specified in the trackList.json/tracks.conf config (as either comma separated list or json array) then we can allow indexing those arbitrary fields

This addresses the issue of #1115 and is similar to the --nameAttributes argument to flatfile-to-json

@rbuels rbuels added this to the 1.15.5 milestone Oct 8, 2018

@rbuels

This comment has been minimized.

Copy link
Collaborator

rbuels commented Oct 8, 2018

sweet. could you add some web docs?

@cmdcolin cmdcolin force-pushed the arbitrary_fields_tabix branch from 41549d3 to 3a20779 Oct 9, 2018

@cmdcolin

This comment has been minimized.

Copy link
Contributor

cmdcolin commented Oct 9, 2018

There's a tangential addition to the PR which is that it now understands when multiple values are in the VCF ID column (separated by semi-colons) which is part of the VCF spec :)

@rbuels

This comment has been minimized.

Copy link
Collaborator

rbuels commented Oct 9, 2018

:shipit:

@rbuels rbuels merged commit f449965 into dev Oct 9, 2018

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@rbuels rbuels removed the in progress label Oct 9, 2018

@cmdcolin cmdcolin deleted the arbitrary_fields_tabix branch Oct 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment