Syed Ali Raza
01/03/2023, 2:50 PMSandeep Yadav
01/03/2023, 3:48 PMSandeep Yadav
01/03/2023, 3:49 PMFrederic Laithier
01/03/2023, 4:49 PMThomas Pedot
01/03/2023, 4:51 PMGleber Baptistella
01/03/2023, 5:15 PMPosition: 243,externalMessage=Something went wrong in the connector. See the logs for more details.,metadata=io.airbyte.config.Metadata@567f3621[additionalProperties={attemptNumber=0, jobId=207613, from_trace_message=true, connector_command=read}],stacktrace=org.postgresql.util.PSQLException: ERROR: syntax error at or near "-"
Position: 243
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2675)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2365)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:355)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:490)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:408)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:329)
at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:315)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:291)
at org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:243)
at com.zaxxer.hikari.pool.ProxyStatement.executeQuery(ProxyStatement.java:110)
at com.zaxxer.hikari.pool.HikariProxyStatement.executeQuery(HikariProxyStatement.java)
at io.airbyte.integrations.source.postgres.PostgresSource.lambda$verifyCursorColumnValues$12(PostgresSource.java:532)
at io.airbyte.db.jdbc.DefaultJdbcDatabase.bufferedResultSetQuery(DefaultJdbcDatabase.java:55)
at io.airbyte.integrations.source.postgres.PostgresSource.verifyCursorColumnValues(PostgresSource.java:532)
at io.airbyte.integrations.source.postgres.PostgresSource.verifyCursorColumnValues(PostgresSource.java:78)
Hrvoje Piasevoli
01/03/2023, 5:32 PM+ temporal-sql-tool --plugin postgres --ep airbyte-db-svc -u docker -p 5432 create --db temporal
2023-01-03T17:19:34.826Z ERROR Unable to create SQL database. {"error": "pq: database \"temporal\" already exists", "logging-call-at": "handler.go:97"}
2023/01/03 17:19:35 Loading config; env=docker,zone=,configDir=config
2023/01/03 17:19:35 Loading config files=[config/docker.yaml]
{"level":"info","ts":"2023-01-03T17:19:35.468Z","msg":"Updated dynamic config","logging-call-at":"file_based_client.go:143"}
{"level":"info","ts":"2023-01-03T17:19:35.469Z","msg":"Starting server for services","value":["history","matching","frontend","worker"],"logging-call-at":"server.go:123"}
Unable to start server. Error: sql schema version compatibility check failed: version mismatch for keyspace/database: "temporal". Expected version: 1.6 cannot be greater than Actual version: 1.4
The problem seems to be in the update-and-start-temporal.sh
:
update_postgres_schema() {
{ export SQL_PASSWORD=${POSTGRES_PWD}; } 2> /dev/null
CONTAINER_ALREADY_STARTED="CONTAINER_ALREADY_STARTED_PLACEHOLDER"
if [ ! -e $CONTAINER_ALREADY_STARTED ]; then
touch $CONTAINER_ALREADY_STARTED
temporal-sql-tool --plugin postgres --ep "${POSTGRES_SEEDS}" -u "${POSTGRES_USER}" -p "${DB_PORT}" create --db "${DBNAME}"
...
fi
Steps to reproduce: (kubernetes deployment, for example minikube)
1. git checkout v0.40.25
2. kubectl apply -k kube/overlays/stable
3. git checkout v0.40.26
4. kubectl apply -k kube/overlays/stable
This will result in airbyte-temporal pod crashing
Fix (either works):
• edit the deployment for airbyte-temoral and update the image used to temporalio/auto-setup:1.7.0
• revert kube/resources/temporal.yaml
to previous version (basically changing the spec container image) and deployTill Blesik
01/03/2023, 6:14 PMspec.yaml
file. If I understand the tutorial correctly (Step 3: Connecting to the API | Airbyte Documentation), the spec is part of the source_connector-name/connector-name.yaml
file. Am I supposed to manually copy the spec section from that file into its own file or is there a step I am missing?Fabiano Pena
01/03/2023, 8:30 PMdocker cp airbyte-server:/tmp/workspace/${NORMALIZE_WORKSPACE}/build/run/airbyte_utils/models/generated/ models/
it didn’t create a full dbt project containing dbt_project.yml and packages.yml files.
It could only export the folder models
. Is there anything else I can do to export whole dbt project?Robert Put
01/03/2023, 10:28 PMAUTO_DETECT_SCHEMA=false
Is this supposed to pull in changes to schema at the start of syncs?Zaza Javakhishvili
01/04/2023, 3:04 AMAvi Sagal
01/04/2023, 8:19 AMFailure Origin: source, Message: Checking source connection failed - please review this connection's configuration to prevent future syncs from failing
is someone familiar with this issue? how did you solve it?
Thanks:)Andrey Tyukavin
01/04/2023, 10:36 AMTLDR: Full refresh | Overwrite clears the destination tables on the Normalization phase when it fails to connect to the source database.This is crucial for our use case, because we have to run a rather long Full refresh replication, and if the data gets deleted there's a big gap until the next successful run. Thanks a lot!
Gleber Baptistella
01/04/2023, 10:46 AMjava.lang.RuntimeException: io.airbyte.workers.exception.WorkerException: Running the launcher replication-orchestrator failed
at io.airbyte.commons.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:314) ~[io.airbyte-airbyte-commons-temporal-0.40.26.jar:?]
at io.airbyte.workers.sync.LauncherWorker.run(LauncherWorker.java:114) ~[io.airbyte-airbyte-commons-worker-0.40.26.jar:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$5(TemporalAttemptExecution.java:195) ~[io.airbyte-airbyte-workers-0.40.26.jar:?]
at java.lang.Thread.run(Thread.java:1589) ~[?:?]
Caused by: io.airbyte.workers.exception.WorkerException: Running the launcher replication-orchestrator failed
at io.airbyte.workers.sync.LauncherWorker.lambda$run$3(LauncherWorker.java:230) ~[io.airbyte-airbyte-commons-worker-0.40.26.jar:?]
at io.airbyte.commons.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:309) ~[io.airbyte-airbyte-commons-temporal-0.40.26.jar:?]
... 3 more
Caused by: io.airbyte.workers.exception.WorkerException: Orchestrator process exited with non-zero exit code: 1
at io.airbyte.workers.sync.LauncherWorker.lambda$run$3(LauncherWorker.java:210) ~[io.airbyte-airbyte-commons-worker-0.40.26.jar:?]
at io.airbyte.commons.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:309) ~[io.airbyte-airbyte-commons-temporal-0.40.26.jar:?]
... 3 more
I've found a similar thread without an answer...
https://airbytehq.slack.com/archives/C021JANJ6TY/p1661440742418679
Could someone help me?Nicolas Xu
01/04/2023, 10:57 AMRachel RIZK
01/04/2023, 11:27 AMAravindh MK
01/04/2023, 12:45 PMMauro Veneziano
01/04/2023, 1:37 PMSandeep Yadav
01/04/2023, 1:57 PMRenato Todorov
01/04/2023, 2:49 PMAbubakar Alaro
01/04/2023, 2:52 PMDavison Rebechi
01/04/2023, 3:22 PMJusten Walker
01/04/2023, 4:49 PMAravindh MK
01/04/2023, 5:47 PMAravindh MK
01/04/2023, 5:48 PMTamas Foldi
01/04/2023, 5:56 PMThomas Pedot
01/04/2023, 6:27 PMMurat Cetink
01/04/2023, 6:45 PMLuan Carvalho
01/04/2023, 7:26 PMRuud Erie
01/04/2023, 8:05 PM