Skip to content

Conversation

@timuralp
Copy link
Member

We should use removeBlobs() for bulk-delete. The change deletes blobs
en-masse. Further, we no longer will perform a HEAD on every blob, as
that's fairly expensive.

Fixes #38

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We really shouldn't have printStackTrace anywhere in our code.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done -- was following the other code in the project (e.g. AuthResource, ExceptionLogger, and IdentityResource).

@timuralp timuralp force-pushed the bug/use-remove-blobs branch from c96cff5 to 52aa43b Compare June 15, 2015 18:24
@gaul
Copy link
Member

gaul commented Jun 15, 2015

Exception.printStackTrace does not go anywhere useful. If you want to log it, use logger.debug("some message", Exception) instead.

@timuralp timuralp force-pushed the bug/use-remove-blobs branch from 52aa43b to 7c9fe56 Compare June 15, 2015 19:48
@gaul
Copy link
Member

gaul commented Jun 15, 2015

👍

1 similar comment
@kahing
Copy link
Member

kahing commented Jun 17, 2015

👍

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to use a Multimap instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would work too. I'll change the commit.

We should use removeBlobs() for bulk-delete. The change deletes blobs
en-masse. Further, we no longer will perform a HEAD on every blob, as
that's fairly expensive.

Fixes #38
@timuralp timuralp force-pushed the bug/use-remove-blobs branch from 7c9fe56 to 7ff978e Compare June 17, 2015 22:19
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you need substring here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you're right, because we already do substring(1) on line 161. I'm not sure how this works right now for containers that start with "/"!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are probably deleting a non-existent container which does not generate an error. We should enable/add some swift-tests to check for these behaviors.

@gaul
Copy link
Member

gaul commented Dec 13, 2019

@timuralp Do we we a path forward on this PR?

@timuralp
Copy link
Member Author

@gaul I'll need to reload this into my brain. Will try to check it out over the weekend.

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.

Native multi-delete objects

4 participants