You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the provided documentation here to build MySQL_to_BigQuery (v2), I keep getting the following error :
Relevant log output
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.145 s
[INFO] Finished at: 2024-05-11T10:58:22+03:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project mysql-to-googlecloud: Could not resolve dependencies for project com.google.cloud.teleport.v2:mysql-to-googlecloud:jar:1.0-SNAPSHOT: Failed to collect dependencies at com.google.cloud.teleport.v2:jdbc-to-googlecloud:jar:1.0-SNAPSHOT: Failed to read artifact descriptor for com.google.cloud.teleport.v2:jdbc-to-googlecloud:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: com.google.cloud.teleport.v2:jdbc-to-googlecloud:pom:1.0-SNAPSHOT (absent): Could not transfer artifact com.google.cloud.teleport.v2:jdbc-to-googlecloud:pom:1.0-SNAPSHOT from/to splunk-artifactory (https://splunk.jfrog.io/splunk/ext-releases-local): status code: 409, reason phrase: (409) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
The text was updated successfully, but these errors were encountered:
Related Template(s)
MySQL_to_BigQuery
Template Version
v2
What happened?
Following the provided documentation here to build MySQL_to_BigQuery (v2), I keep getting the following error :
Relevant log output
The text was updated successfully, but these errors were encountered: