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

s3-to-dc does not index when s3 url doesn't contain * #485

Open
pindge opened this issue Jun 28, 2022 · 2 comments
Open

s3-to-dc does not index when s3 url doesn't contain * #485

pindge opened this issue Jun 28, 2022 · 2 comments

Comments

@pindge
Copy link
Contributor

pindge commented Jun 28, 2022

No description provided.

@pindge pindge self-assigned this Jun 28, 2022
@pindge pindge linked a pull request Jun 28, 2022 that will close this issue
@omad omad unassigned pindge Jun 9, 2023
@benjimin
Copy link
Contributor

benjimin commented Oct 5, 2023

There needs to be a way to index a specific dataset, without accidentally indexing other datasets.

Not accepting globs that do not contain wildcards is a weird bug (because such globs should certainly be valid).

There definitely should also be support for not using globs at all. It's silly to have to try to invent dummy globs for the cases where the intended dataset URI is already known exactly.

@omad
Copy link
Member

omad commented Oct 26, 2023

I haven't tested, but the ridiculously named --skip-check flag might enable this behaviour. :(

  --skip-check                    Assume file exists when listing exact file rather than wildcard.

This could be a default, dependent on * being in the argument.

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 a pull request may close this issue.

3 participants