Issue Details
The BigQuery Shader JDBC driver is not shading SLF4J.
This breaks our logging.
Example
Environment
N/A issue is with shaded jar
Provide the relevant details about your environment:
N/A issue is with shaded jar
(Optional) If deployed on GCP, provide the relevant details about your GCP deployment environment:
- Project ID:
- Cloud Services:
- Deployment Environment (Compute, GKE, Run, etc):
Dependencies
N/A issue is with shaded jar
- Provide the versions of the relevant libraries:
https://mvnrepository.com/artifact/com.google.cloud/google-cloud-bigquery-jdbc/1.0.0)
Reproducer
N/A issue is with shaded jar
Example
N/A issue is with shaded jar
Logs and Stack Trace
N/A issue is with shaded jar
Example
N/A issue is with shaded jar
Behavior
Optional: Any additional information about the behavior of the error is helpful to debug.
Behavioral Questions:
- When did the issue begin? Is this behavior related to any dependency version upgrade?
- Is this behavior flaky? Or is this consistently seen in production?
- Is this behavior related to the volume of data?
Issue Details
The BigQuery Shader JDBC driver is not shading SLF4J.
This breaks our logging.
Example
Environment
N/A issue is with shaded jar
Provide the relevant details about your environment:
N/A issue is with shaded jar
(Optional) If deployed on GCP, provide the relevant details about your GCP deployment environment:
Dependencies
N/A issue is with shaded jar
https://mvnrepository.com/artifact/com.google.cloud/google-cloud-bigquery-jdbc/1.0.0)
Reproducer
N/A issue is with shaded jar
Example
N/A issue is with shaded jar
Logs and Stack Trace
N/A issue is with shaded jar
Example
N/A issue is with shaded jar
Behavior
Optional: Any additional information about the behavior of the error is helpful to debug.
Behavioral Questions: