Arik Elbag
02/22/2023, 8:37 PMArik Elbag
02/22/2023, 8:38 PMJusten Walker
02/22/2023, 8:41 PMmetrics.metricsClient: otel
but the OTEL_COLECTOR_ENDPOINT
is sort of dynamic since it needs to be set to the host IP of the pod -- ie: it can't come directly from the configmapKumar K
02/22/2023, 9:28 PMIgnacio Alasia
02/22/2023, 10:00 PMCREATE USER "shared-h3-airbyte" WITH PASSWORD '**********';
GRANT USAGE ON SCHEMA public TO "shared-h3-airbyte";
GRANT SELECT ON TABLE public.addresses_cells TO "shared-h3-airbyte";
GRANT SELECT ON TABLE public.coverages_cells TO "shared-h3-airbyte";
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO "shared-h3-airbyte";
GRANT rds_replication TO "shared-h3-airbyte";
SELECT pg_drop_replication_slot('airbyte_shared_h3');
SELECT pg_create_logical_replication_slot('airbyte_shared_h3', 'pgoutput');
ALTER TABLE addresses_cells REPLICA IDENTITY DEFAULT;
ALTER TABLE coverages_cells REPLICA IDENTITY DEFAULT;
DROP PUBLICATION airbyte_publication_shared_h3;
CREATE PUBLICATION airbyte_publication_shared_h3 FOR TABLE addresses_cells,coverages_cells;
Konstantin Lackner
02/22/2023, 11:50 PMHTTPError('403 Client Error: Forbidden for url: <https://analyticsdata.googleapis.com/v1beta/properties/XXXXX/metadata>')
I already found this related thread: https://discuss.airbyte.io/t/ga4-connector-connection-test-fails/3439/2
But I added the user in Google Analytics on the account level.
So I'm not sure what's wrong here...Manav Kothari
02/23/2023, 3:57 AMSomething went wrong in the connector. See the logs for more details.
Stack Trace: com.mongodb.MongoCommandException: Command failed with error 292 (QueryExceededMemoryLimitNoDiskUseAllowed): 'PlanExecutor error during aggregation :: caused by :: Exceeded memory limit for $group, but didn't allow external sort. Pass allowDiskUse:true to opt in.' on server <http://cluster0-shard-00-01.ucrrp.mongodb.net:27017|cluster0-shard-00-01.ucrrp.mongodb.net:27017>. The full response is {"ok": 0.0, "errmsg": "PlanExecutor error during aggregation:: caused by :: Exceeded memory limit for $group, but didn't allow external sort. Pass allowDiskUse:true to opt in.", "code": 292, "codeName": "QueryExceededMemoryLimitNoDiskUseAllowed", "$clusterTime": {"clusterTime": {"$timestamp": {"t": 1677123912, "i": 96}}, "signature": {"hash": {"$binary": {"base64": "ZuTk1CUhOayPeR/0ir98n3rSvOA=", "subType": "00"}}, "keyId": 7168578009350275074}}, "operationTime": {"$timestamp": {"t": 1677123912, "i": 96}}}
at com.mongodb.internal.connection.ProtocolHelper.getCommandFailureException(ProtocolHelper.java:198)
Gautam B
02/23/2023, 5:33 AMsyncCatalog
for a connector when using the Airbyte API *POST* /v1/connections/create
. We are provisioning various 3rd party apps in Airbyte using API and right now we are not able to find the syncCatalog for each app. We are creating the connector in ui and taking the schema from the db, but this is just a hack. Is there a place where we can get the base/default schema definition for each connector?Le Minh Nguyen
02/23/2023, 6:53 AM김건희
02/23/2023, 7:06 AM2023-02-23 06:16:28 ERROR i.a.w.i.DefaultAirbyteStreamFactory(internalLog):163 - Check failed
Narendran Omprakash
02/23/2023, 8:03 AMxi-chen.qi
02/23/2023, 9:20 AMJana Kniel
02/23/2023, 10:54 AMBevis Lin
02/23/2023, 11:25 AM{
"size": 0,
"offset": 0,
"stores": [
{
"id": "S0000",
"name": "xxx shop",
"foods": [
{
"food_id": "f12345",
"food_nm": "Apple",
"sold_out": true
}
],
"create_date": "2019-12-28",
"update_date": "2023-02-23"
},
{
"id": "S0001",
"name": "yyy shop",
"foods": [
{
"food_id": "f11111",
"food_nm": "Banana",
"sold_out": false
}
],
"create_date": "2012-01-22",
"update_date": "2023-02-23"
}
]
}
Thiago Villani
02/23/2023, 11:56 AMDaniel Pietschmann
02/23/2023, 1:34 PMJason Vondersmith
02/23/2023, 1:59 PMKustomer
connector, currently in Alpha. I see there was a singer/user-agent issue with it originally. But then I found this PR that seems like it would correct the implementation. Is there a way to know when that PR might get merged?Francisco Andres
02/23/2023, 2:04 PMArman S
02/23/2023, 2:21 PMhelm repo add airbyte <https://airbyte.github.io/airbyte>
helm repo update
• Step 2: Create a namespace for Airbyte:
kubectl create namespace airbyte
• Step 3: Install Airbyte using the Helm chart
helm install airbyte airbyte/airbyte -n airbyte -f ./helm/values.yaml
• Step 4: Forward ports
kubectl --namespace airbyte port-forward service/airbyte-airbyte-webapp-svc 8000:80
My values.yaml file looks like this:
airbyte:
deployment:
replicas: 1
service:
type: ClusterIP
ingress:
enabled: false
persistence:
enabled: true
size: 200MB
image:
tag: 0.31.3
pullPolicy: IfNotPresent
worker:
enabled: true
command: ["/bin/bash", "-c"]
args:
- |
set -ex
/airbyte/integration/bin/entrypoint.sh
resources:
requests:
cpu: 500m
memory: 512Mi
limits:
cpu: 1
memory: 1Gi
However, I am struggling to understand why the Worker pod doesn't spin up. The logs say the following:
Stream closed: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"container \"airbyte-worker-container\" in pod \"airbyte-worker-767db5b6c7-k78cg\" is waiting to start: CreateContainerConfigError","reason":"BadRequest","code":400}
Is this something that anyone could help me with? I was also wondering if I need the cron and temporal deployments?Claudio Cavallo
02/23/2023, 2:38 PMirbyte_api_client.exceptions.ApiTypeError: Invalid type for variable 'non_breaking_changes_preference'. Required value type is NonBreakingChangesPreference and passed type was str at ['non_breaking_changes_preference']
Claudio Cavallo
02/23/2023, 2:39 PMKonstantin Lackner
02/23/2023, 4:25 PMdaily_active_users
. All other tables are empty. Can anyone help?Lior Shkiller
02/23/2023, 6:07 PMi.a.v.j.JsonSchemaValidator(test):130 - JSON schema validation failed.
errors: $: null found, string expected
What can be the reason?
Hubspot version: 0.3.2
Airbyte version: 0.40.23José Lúcio Zancan Júnior
02/23/2023, 6:52 PMJosé Lúcio Zancan Júnior
02/23/2023, 7:49 PMads_reports_daily
stream, which according to the connector docs:
For example, if you select the daily-aggregation flavor of a report, the report will contain a row for each day for the duration of the report. Each row will indicate the number of impressions recorded on that day.
My issue is that in the destination dataset, I'm only seeing data for that day of each ad. (If I ran a sync yesterday, I can only see the yesterday's clicks/impressions/conversions. If I run a sync again today, yesterday's data is deleted and I start seeing only today's values.)
I suspect this behavior is caused by the sync mode, which is set to "Incremental | Deduped + history", with stat_time_day
as cursor and ad_id
as primary key.
But:
1. stat_time_day
aren't suposed to be a primary key too? So the transformation can keep one entry for each day AND ad_id?
2. If I change the sync mode to "Incremental | Append", my problem is solved (kind of), but then I would make room for duplicates and missing data (days skipped due to errors or unavailability)
3. My guess is that for what I need, the "Incremental | *Deduped + history*" should work, but then I would need to set the stat_time_day
as the primary key as well, which seems to be impossible, since this field cannot be changed in the connector replication settings.
Any tips or anyone in the same situation?
Thanks in advance.An R
02/23/2023, 7:54 PMkubectl apply -k kube/overlays/stable
eventually a worker pod fails with a message similar to
ERROR i.m.r.Micronaut(handleStartupException):338 - Error starting Micronaut server: null
,
This error is preceded by a warning:
i.a.m.l.MetricClientFactory(initialize):74 - MetricClient was not recognized or not provided. Accepted values are `datadog` or `otel`.
Is there someway to disable METRIC_CLIENT?
We've tried different values for METRIC_CLIENT (we've tried none
, false
and empty) but the pod ends up failing)
We don't use Datadog or Otel, and leaving value empty for METRIC_CLIENT seems not tgo be a solution
What could we do?
Thanks!charlie song
02/23/2023, 8:49 PMShailendra Jaiswar
02/23/2023, 9:54 PMMalik
02/23/2023, 11:21 PMArik Elbag
02/23/2023, 11:45 PMLast attempt:
NaN Bytes | no records | no records | 2m 28s | Sync
Failure Origin: normalization, Message: Something went wrong during normalization
4:03PM 02/22
3 attempts
2023-02-23 00:13:46 - Additional Failure Information: message='io.temporal.serviceclient.CheckedExceptionWrapper: java.util.concurrent.ExecutionException: io.airbyte.workers.exception.WorkerException: Normalization Failed.', type='java.lang.RuntimeException', nonRetryable=false