Randal Boyle
03/23/2023, 4:11 AMRandal Boyle
03/23/2023, 4:11 AMRandal Boyle
03/23/2023, 4:12 AMwget <https://raw.githubusercontent.com/airbytehq/airbyte/v0.42.0/.env>
wget <https://raw.githubusercontent.com/airbytehq/airbyte/v0.42.0/docker-compose.yaml>
wget <https://raw.githubusercontent.com/airbytehq/airbyte/v0.42.0/flags.yml>
docker compose up
Yogic Wahyu
03/23/2023, 5:53 AMincremental dedup
using Airbyte by comparing (and filtering) CDC log (using other application) and batch data (ingested via Airbyte) stored in Data Warehouse (some new data is not ingested by its reference timestamp). So far, I suspected that there is some overlapping process when Airbyte has stated that the incremental process is done, the new data is persisted into database with reference timestamp should be included into running ingestion. Is there any case like this or is it possible?
Specs:
Airbyte Version : 0.40.28
Datasource : Postgres version 9/10
Source Connector : airbyte/source-postgres 0.4.38Y L
03/23/2023, 6:04 AMKevin Conseil
03/23/2023, 8:37 AMJohannes Müller
03/23/2023, 10:22 AMVỹ Dương
03/23/2023, 10:29 AMAirbyte version: v0.39.32-alpha
OS Version / Instance: Deployment: GCP Compute Engine
Step where error happened: Sync job
Chetan M
03/23/2023, 12:08 PMRomain LOPEZ
03/23/2023, 1:10 PMlaila ribke
03/23/2023, 1:17 PMSai Kumar Devulapelli
03/23/2023, 1:38 PMwp
03/23/2023, 2:59 PMYowan Ramchoreeter (Airbyte)
03/23/2023, 3:00 PMFaisal Anees
03/23/2023, 3:32 PMsupportsNormalization
response property for the api/v1/destination_definition_specifications/get
endpoint . According to the openapi.yaml
file, the response for this endpoint should follow this schema
DestinationDefinitionSpecificationRead:
properties:
connectionSpecification:
$ref: "#/components/schemas/DestinationDefinitionSpecification"
destinationDefinitionId:
$ref: "#/components/schemas/DestinationDefinitionId"
documentationUrl:
type: string
jobInfo:
$ref: "#/components/schemas/SynchronousJobRead"
supportedDestinationSyncModes:
items:
$ref: "#/components/schemas/DestinationSyncMode"
type: array
supportsDbt:
type: boolean
supportsNormalization:
type: boolean
required:
- destinationDefinitionId
- jobInfo
type: object
but when i call the API for the BigQuery
destination id (22f6c74f-5699-40ff-833c-4a879ea40133), i am getting a response which has a missing supportsNormalization
field . Based on docs, this destination does support normalization but why is the endpoing returning a response with this property missing ? I am adding the response that i got from the API in the commentsAnton Marini
03/23/2023, 3:47 PMSlackbot
03/23/2023, 4:40 PMReid Roman
03/23/2023, 4:41 PMAnton Marini
03/23/2023, 5:26 PM<gs://airbyte-vault/financial.csv>
which is linked as a sample from https://docs.airbyte.com/integrations/sources/file/#examples and it 404s in the file source setup, unless im misunderstanding the docs and those are 'pretend' configs to illustrate some usage of file source options?Anton Marini
03/23/2023, 6:26 PMJin Gong
03/23/2023, 6:32 PMGRANT rds_replication TO <user_name>;
instead the one listed in document ALTER USER <user_name> REPLICATION;
Andy Ritting
03/23/2023, 7:22 PMJin Gong
03/23/2023, 10:40 PM2023-03-23 22:31:48 [ERROR] - Stream [AssignmentQuestion] Error storing 431 source objects in [5ynfrw115cdzbio29kt6s.cbeif4p6gtjk75vw6n12l8] destination (1 attempts left): Error creating [postgres_assignmentquestion] table with statement [CREATE TABLE PROD_DB.postgres_assignmentquestion (_source_id text,_timestamp timestamp(6),assignmentid text,createdat timestamp(6),eventn_ctx_event_id text,gradingtype text,id text,instructiontext text,isactive boolean,nummaxmcqselections double precision,order double precision,responsetype text,responsevisibility text,src text,title text,updatedat timestamp(6))]: 001003 (42000): SQL compilation error:
syntax error line 1 at position 256 unexpected 'order'.
Dan Cook
03/23/2023, 10:45 PMOops! Something went wrong…
Unknown error occurred
John Olinger
03/24/2023, 1:21 AMKundan Kumar
03/24/2023, 5:21 AMDHANANJAY NAIKWADI
03/24/2023, 5:35 AMChetan M
03/24/2023, 6:43 AMGowrav Tata
03/24/2023, 7:07 AMLydia Lim Li Han
03/24/2023, 7:44 AM_ab_additional_properties
field is now empty. Is this a intended design or bug?
This design doesn’t quite make sense to me, since according to the docs in 2.0.0 onwards, the schema inference became more strict (based on the earliest file only). So, if the new fields is not kept in _ab_additional_properties
, it will become impossible to reconcile newer files with latest schema vs the older files - even if we refresh schema in Airbyte.