Skip to content

copy from shouldn't create not exist directories #6182

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

Open
MichaelScofield opened this issue May 26, 2025 · 0 comments
Open

copy from shouldn't create not exist directories #6182

MichaelScofield opened this issue May 26, 2025 · 0 comments
Labels
C-bug Category Bugs

Comments

@MichaelScofield
Copy link
Collaborator

What type of bug is this?

User Experience

What subsystems are affected?

Standalone mode

Minimal reproduce step

Start a standalone locally and execute:

create table foo (ts timestamp time index);
copy foo from '/tmp/should-not-have-been-existed-dir/foo.parquet' with (format = 'parquet');

You'll see the directory /tmp/should-not-have-been-existed-dirbeen created. I think it's a bad side effect which must be resolved, since "copy from" is expected to be a read only operation for the file system, from the perspective of users.

What did you expect to see?

If the directory is not existed, don't create it.

What did you see instead?

Directory been created.

What operating system did you use?

macos

What version of GreptimeDB did you use?

latest

Relevant log output and stack trace

@MichaelScofield MichaelScofield added the C-bug Category Bugs label May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category Bugs
Projects
None yet
Development

No branches or pull requests

1 participant