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

storage/s3: FORMAT option should be required or default to supported value #27101

Closed
Tracked by #7256
morsapaes opened this issue May 15, 2024 · 0 comments · Fixed by #27158
Closed
Tracked by #7256

storage/s3: FORMAT option should be required or default to supported value #27101

morsapaes opened this issue May 15, 2024 · 0 comments · Fixed by #27158
Assignees
Labels
C-bug Category: something is broken T-s3 Theme: s3 bulk exports and imports

Comments

@morsapaes
Copy link
Contributor

What version of Materialize are you using?

v0.98.6

What is the issue?

When no FORMAT is specified in a COPY TO command with an AWS CONNECTION, Materialize falls back to the default used for the vanilla variation of the command (TEXT), which isn't supported for bulk exports:

materialize=> COPY mv TO 's3://mz-to-snow/parquet/'
WITH (
    AWS CONNECTION = aws_role_assumption
  );
ERROR:  FORMAT TEXT not yet supported

We should either make FORMAT required when using this variation of the command, or default to one of the valid options.

@morsapaes morsapaes added C-bug Category: something is broken T-s3 Theme: s3 bulk exports and imports labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: something is broken T-s3 Theme: s3 bulk exports and imports
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants