Skip to content

Fixed #5340 delete auxiliary objects in Swift#5356

Merged
kcondon merged 1 commit intoIQSS:developfrom
carlosmcgregor:5340-delete-aux-fix
Dec 18, 2018
Merged

Fixed #5340 delete auxiliary objects in Swift#5356
kcondon merged 1 commit intoIQSS:developfrom
carlosmcgregor:5340-delete-aux-fix

Conversation

@carlosmcgregor
Copy link
Contributor

@carlosmcgregor carlosmcgregor commented Nov 29, 2018

Change datafile storage identifier to work with joss
Change dataset storage identifier to reflect datafile storage identifier changes

Related Issues

Pull Request Checklist

Change datafile storage identifier to work with joss
Change dataset storage identifier to reflect datafile storage identifier changes
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.0003%) to 16.215% when pulling b1cf60f on carlosmcgregor:5340-delete-aux-fix into 0ee43fa on IQSS:develop.

@carlosmcgregor
Copy link
Contributor Author

Added a few lines on a previously uncovered function -> coverage decreased.

@sekmiller sekmiller self-requested a review December 5, 2018 20:53
@carlosmcgregor
Copy link
Contributor Author

Hello @pdurbin ! In a conversation with @landreev we have opened a can of worms re: storageidentifier in the Swift driver. A brief summary would be the following:

  • < 4.9.4 (presumed):
    • Example storageidentifier: swift://endpoint1:doi-10-1234-DM2-SZJXID:1673798809a-21f68803badb
    • Bug: Unknown
  • 4.9.4:
    • Example storageidentifier: swift://endpoint1:doi-10-1234-DM2/SZJXID:1673798809a-21f68803badb
    • Bug: Unable to delete files
  • 4.10:
    • Example storageidentifier: swift://endpoint1:doi-10-1234:DM2/SZJXID/1673798809a-21f68803badb
    • Bug: None

Given that 4.9.4's Swift driver was not production ready due to the inability to delete files, I would like your input on whether it would be necessary to investigate backward compatibility between 4.10 and < 4.9.4, and write a script to address any issue.

At a glance, I believe access to uploaded files would not be an issue. However, I would have to review on whether uploads become affected when working with already created datasets.

I apologize for bringing this to your attention so long after this PR!

@pdurbin
Copy link
Member

pdurbin commented Apr 11, 2019

@carlosmcgregor hi! If anyone is running any version of Dataverse before 4.10 and has trouble with Swift, we will just tell them to upgrade to the latest version of Dataverse. Thanks for the offer, though!

@pdurbin
Copy link
Member

pdurbin commented Apr 11, 2019

And thank you also for this great summary of what bugs existed when. It's easy for forget. I was having trouble helping a friend troubleshoot Swift yesterday at http://irclog.iq.harvard.edu/dataverse/2019-04-10#i_90842 and I was starting to wonder if Swift works at all. I asked at standup just now and it sounds like it does. And you're re-confirming that it works. (I believe I simply had auth misconfigured.) Thanks again for cracking open this Swift code and helping us improve it!

@carlosmcgregor
Copy link
Contributor Author

@pdurbin Glad I could help! Looking forward to making further contributions :)

@pdurbin
Copy link
Member

pdurbin commented Apr 11, 2019

@carlosmcgregor great! The next one to maybe look at is #5754

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

Successfully merging this pull request may close these issues.

5 participants