-
Notifications
You must be signed in to change notification settings - Fork 217
return a v1write even for truncate #1353
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
base: master
Are you sure you want to change the base?
return a v1write even for truncate #1353
Conversation
/gcbrun |
Thanks for the contribution! It failed on
|
/gcbrun |
Please run |
/gcbrun |
/gcbrun |
Hi @isha97, is there anything outstanding I should do for this PR? Please help me understand the failing checks, thanks! |
Notice that SupportsOverwrite is not fully implemented, specifically the |
Hi @davidrabinowitz thank you for the response!
Wasn't this the case prior? Since the implementation of that comes from |
…1353) * Add new flag 'fs.gs.cloud.logging.enable' to export logs to cloud logging. * Add LoggingInterceptor to intercept log records sent to flogger and write those log records to Cloud logging. Also added unit test * Add LoggingInterceptor to intercept log records sent to flogger and write those log records to Cloud logging. Also added unit test * Configure logging configuration and add it to root logger handler. * Configure logging configuration and add it to root logger handler. * Merge remote-tracking branch 'origin/exp' into exp * Use credentials to create logging client. Structure log entry to include class and method name * Use credentials to create logging client. Structure log entry to include class and method name * Fix unit tests. * Add java doc, sort configuration and resolve other review comments. * Add java doc, sort configuration and resolve other review comments.
Spark35BigQueryWriteBuilder
supports V1Write butBigQueryWriteBuilder
is not an instance ofV1Write
. We need to return aV1Write
instance for truncate.