Johnny P
04/17/2023, 12:19 AMAkash
04/17/2023, 2:58 AMAbhishek Kale
04/17/2023, 3:25 AMAbhishek Kale
04/17/2023, 3:28 AMUUBOY scy
04/17/2023, 4:20 AMUUBOY scy
04/17/2023, 5:21 AMJaroslav Loutocký
04/17/2023, 6:34 AMBishan Singh
04/17/2023, 6:47 AMBishan Singh
04/17/2023, 7:29 AMGabriele Lomuscio
04/17/2023, 7:56 AMSlackbot
04/17/2023, 8:18 AMmohd shaikh
04/17/2023, 8:19 AMMark Nuttall-Smith
04/17/2023, 9:35 AMCONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
ab3a5b99c835 normalization-normalize-12215-0-mficw 0.00% 140.4MiB / 15.44GiB 0.89% 0B / 0B 63.4MB / 24.6kB 19
5b82e0e49c9b source-postgres-read-12214-0-tpikv 11.46% 3.004GiB / 15.44GiB 19.45% 0B / 0B 406kB / 0B 27
933713849e8e destination-postgres-write-12214-0-bffyw 45.89% 604.4MiB / 15.44GiB 3.82% 0B / 0B 815kB / 0B 27
13b8fc7fcd53 airbyte-proxy 0.09% 3.766MiB / 15.44GiB 0.02% 6.92MB / 6.94MB 8.55MB / 4.1kB 3
ea1753186749 airbyte-webapp 0.07% 6.062MiB / 15.44GiB 0.04% 5.18MB / 6.89MB 9.57MB / 8.19kB 5
a69204bca14e airbyte-cron 0.08% 1.782GiB / 15.44GiB 11.54% 137MB / 596kB 812MB / 0B 47
ad679b9c3dea airbyte-connector-builder-server 0.24% 41.76MiB / 15.44GiB 0.26% 1.73kB / 0B 30.3MB / 0B 1
cab52e80e142 airbyte-worker 31.13% 698.1MiB / 15.44GiB 4.41% 5.92MB / 1.22MB 110MB / 8.19kB 189
f222ef078bb1 airbyte-server 8.75% 951.7MiB / 15.44GiB 6.02% 120MB / 6.14MB 70.8MB / 0B 57
c2dda46d7d72 airbyte-temporal 2.67% 118MiB / 15.44GiB 0.75% 254MB / 163MB 134MB / 8.19kB 12
I find it particularly surprising, given all our connections are set to manual replication frequency! Is it normal?Slackbot
04/17/2023, 9:52 AMMonika Bednarz
04/17/2023, 9:56 AMGuillaume Jaouen
04/17/2023, 10:26 AMFailure Origin: normalization, Message: Normalization failed during the dbt run. This may indicate a problem with the data itself.
Do you know why ?
2. Looking at several tables in Snowflake, I can’t find all the past events. Example the title of a deal has been changed several times, but I don’t get the history of these changes. After the first synchronization, I only get the last status of the deal. How can we get the history of all the past events ?hedgar
04/17/2023, 11:51 AMNick Joanis
04/17/2023, 2:06 PMIsabella Dintinjana
04/17/2023, 2:32 PMAric Lasry
04/17/2023, 3:19 PMYepher
04/17/2023, 3:48 PMChristopher Wu
04/17/2023, 5:21 PMSandhya Manimaran
04/17/2023, 5:56 PMBen Greene
04/17/2023, 6:18 PMYepher
04/17/2023, 6:25 PMvalue.yaml
file so I can commit it into GitHub. This is what I am trying and it is not working:
kubectl create secret generic our-secrets --from-literal=airbyte-externaldatabase-password=airbytepass
for our values.yaml
we use:
externalDatabase:
host: <http://my-postgres.rds.amazonaws.com|my-postgres.rds.amazonaws.com>
user: airbyte
# password: "airbytepass"
existingSecret: "our-secrets"
existingSecretPasswordKey: "airbyte-externaldatabase-password"
database: db-airbyte
port: 5432
If we put password: "airbytepass"
in the values.yaml
file, it works fine.
But if we do this in the values.yaml
existingSecret: "our-secrets"
existingSecretPasswordKey: "airbyte-externaldatabase-password"
We get this error:
Warning Failed 9s (x4 over 40s) kubelet Error: couldn't find key DATABASE_PASSWORD in Secret default/airbyte-airbyte-secrets
I am sure I am doing something silly, but I can't quite sort it out. To install I am doing this helm upgrade -i airbyte airbyte/airbyte -f values.yaml
Luke Rodgers
04/17/2023, 6:30 PMSELECT "id","some","other","columns" FROM "public"."versions" ORDER BY "id" ASC
(actual columns redacted, other than id
).
However this query does not use a LIMIT
clause, and so it attempts a full table scan. This hangs for several hours, then fails with this error ERROR i.a.i.b.AirbyteExceptionHandler(uncaughtException):26 Something went wrong in the connector. See the logs for more details. java.lang.RuntimeException: java.lang.RuntimeException: org.postgresql.util.PSQLException: ERROR: could not write to file "base/pgsql_tmp/pgsql_tmp236578.139": No space left on device
. The EC2 instance has 1TB of disk. I could increase disk size and keep trying, but this seems like a bug with the code that determines fetch size.
How have others handled initial sync for large tables in non-CDC mode?[DEPRECATED] Marcos Marx
Slackbot
04/17/2023, 9:27 PMMichael Adaniken
04/17/2023, 9:36 PMTaylor Hubbard
04/17/2023, 9:38 PM/v1/user?modified_at={'gte': '2023-01-01'}
Does the low-code builder support this scenario?