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

Add support for glob patterns and/or prefixes to "mc" #2117

Closed
tmbdev opened this issue Apr 9, 2017 · 5 comments
Closed

Add support for glob patterns and/or prefixes to "mc" #2117

tmbdev opened this issue Apr 9, 2017 · 5 comments

Comments

@tmbdev
Copy link

tmbdev commented Apr 9, 2017

Expected behaviour

I would like

mc rm server/bucket/prefix-*

to remove all files starting with prefix- from the bucket.

Other glob patterns should also work.

Alternatively, a simpler form might be to just add a "prefix" option, as in:

mc rm --prefix server/bucket/prefix-

Actual behaviour

mc: Failed to remove ‘server/bucket/prefix-*’. Object key is missing, object key cannot be empty

Steps to reproduce the behaviour

run mc rm server/bucket/prefix-*

mc version

Version: DEVELOPMENT.GOGET
Release-tag: DEVELOPMENT.GOGET
Commit-id: DEVELOPMENT.GOGET

System information

Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial

@badscooter23
Copy link
Contributor

badscooter23 commented Apr 10, 2017

Per discussions with AB there are multiple topics that are related to ...

  • expected behavior for and mc command where the user specified a path name and --recursive
  • the desire to accept wildcards and/or regular expressions on multiple commands
  • this also ties into the desire to support a tiering relationship between multiple object stores (eg: a minio and an s3 object store) and the desire to express patterns / filters for behavior

I would like to tie this together into a more comprehensive proposal...
Can you assign this to me (for now) and I will do a write up on this?

Thx

@harshavardhana
Copy link
Member

This is not blocked anymore currently being addressed in #2201

@ebozduman
Copy link
Collaborator

Removed Blocked label per @harshavardhana 's comment.

@ebozduman
Copy link
Collaborator

Closing it since it is a duplicate of #2201

@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants