-
Notifications
You must be signed in to change notification settings - Fork 753
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
bug: COPY INTO GCS location seems to duplicate path #16304
Comments
So it seems that including a trailing slash on the end of the path makes it behave correctly. I can include the slash, but since it always exports one or many parquet files to the location, should it not be assumed that the location is always a path, or at least that Works correctly: CREATE table t1 (c1 int null);
INSERT INTO t1 values (1), (2), (3);
COPY INTO 'gcs://bucket/tables/t1/'
CONNECTION = (
CREDENTIAL = '<snip>'
)
FROM default.t1
FILE_FORMAT = (TYPE = PARQUET); |
@rad-pat thank you. it is bug. |
@youngsofun , presume this is fixed now with #16321? Was this affecting internal storage if GCS is used, or would that have remained unaffected? |
it should have been fixed, please have a try |
Yes, seems fixed for COPY INTO, thanks. I just wondered if there was any effect to the parquet files stored by the system whilst this bug was happening? |
The behavior of the bug is as follows: If your location string does not end with a /, copying into While it’s unfortunate to make this mistake, I don’t think it’s a major issue in practice, especially if you are only using it for unloading. The additional |
Search before asking
Version
v1.2.618-nightly
What's Wrong?
When issuing a COPY INTO command for GCS, the resulting path in GCS is duplicated
How to Reproduce?
Looks in GCS, see that path is bucket/tables/t1/tables/t1
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: