search

gvlproject / genomespace

Test suite & Issues for GenomeSpace Australia
0 stars 1 forks source link

not showing the segments' path inside genomespace may result in not showing the end user some of the files. #67

Closed ykowsar closed 7 years ago

ykowsar commented 7 years ago

People can select any path as the path for segments and if the path is the same name with the file but with multiple level of hierarchy from swift point of view everything is fine but ...

madisonkeene commented 7 years ago

That issue description made no sense hahaha 😂 is this the issue where if its not like segments_dir/<actual_segments> and instead it has for eg segments_dir/dir2/dir3/<actual_segments> , swift itself is OK but GenomeSpace won't hide the segments?

ykowsar commented 7 years ago

Yes. Exactly :D

On Thu, Nov 24, 2016 at 11:35 AM, Madison Flannery <notifications@github.com

wrote:

That issue description made no sense hahaha 😂 is this the issue where if its not like segments_dir/ and instead it has for eg segments_dir/dir2/dir3/ , swift itself is OK but GenomeSpace won't hide the segments?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/gvlproject/genomespace/issues/67#issuecomment-262663229, or mute the thread https://github.com/notifications/unsubscribe-auth/AIF_oB2eydw-lZpyitn00cnPe1c3Wt-yks5rBNvhgaJpZM4K6UjZ .

madisonkeene commented 7 years ago

Can we somehow use the info under the section Retrieving a large object from http://docs.openstack.org/developer/swift/overview_large_objects.html

specifically the part where you can grab the manifest itself?

madisonkeene commented 7 years ago

Theoretically that works but speed-wise I don't imagine it's great?

madisonkeene commented 7 years ago

Is the verdict that we're closing this? and documenting it?