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

Test Case for Extended Metadata Handling with Pulsar #11456

Open
jmchilton opened this issue Feb 23, 2021 · 0 comments
Open

Test Case for Extended Metadata Handling with Pulsar #11456

jmchilton opened this issue Feb 23, 2021 · 0 comments

Comments

@jmchilton
Copy link
Member

jmchilton commented Feb 23, 2021

I failed repeatedly at this task in late 2019 and early 2020, my latest failed attempt is at #9227 I think.

Getting some consistent stack traces so we can figure out what potential problems there are with running Pulsar with extended metadata on would be awesome and allow rapid progress.

In addition to being more efficient in these scenarios with remote storage and distributed compute, running Pulsar in extended metadata would solve many classes of output collection errors. Stuff like discovery of datasets (galaxyproject/pulsar#212 and galaxyproject/pulsar#239) would happen on the compute node and we wouldn't need to worry about transferring the right files back to Galaxy.

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

No branches or pull requests

1 participant