Dario Forti
10/14/2022, 7:10 PMDusty Shapiro
10/14/2022, 8:00 PMextraContainers
array in the chart values?Dipesh Kumar
10/14/2022, 5:51 PMLee Danilek
10/14/2022, 10:46 PMSourav Gupta
10/15/2022, 4:12 AMZaza Javakhishvili
10/15/2022, 4:58 AMZaza Javakhishvili
10/15/2022, 5:17 AMEmile Fyon
10/15/2022, 9:02 PMRobert Put
10/15/2022, 10:16 PMWendell Nascimento
10/16/2022, 1:24 AMGeoffrey Garcia
10/16/2022, 1:37 PMRahul Borse
10/16/2022, 4:52 PMMohamed Alsharif
10/16/2022, 6:57 PMGene Chu
10/17/2022, 2:43 AMairbyte-metrics
in my kubernetes.
i need to check the latest overall job status, and send alert when the job failed.胡得潮
10/17/2022, 2:59 AMGergely Imreh
10/17/2022, 7:28 AMtable
is indeed deduped, and that’s nice
• there is a table_scd
for the history, and that works fine as well, every entry has a unique _airbyte_ab_id
as expected
• The normalized table (say normalizing a properties
field), ends up as table_properties
as expected for this example, but the content is different from what I’ve expected to some respect:
The differences and questions are:
• the contents of table_properties
are normalized from table_scd
(as confirmed by looking at the generated dbt code) rather than as expected from table
, so end up with a loads more entries than expected. I would have expected table_properties
to be deduped after the normalized just as table
was before. Am I expecting something wrong?
• in table_properties
there’s actually a lot more entries even than table_scd
because a single entry seem to potentially (but not always) end up normalized multiple times, only the _airbyte_normalized_at
field being different, while all the content fields are the same (as are the hashid fields to confirm). Looking at duplicates, I see some some entries normalized multiple times for us up to 8x even (most of the duplicates are 2-3x) on our 1/h schedule. What can cause multiple normalization like this, if the underlying table does have only a single entry?Ramon Vermeulen
10/17/2022, 8:18 AMSteven Herweijer
10/17/2022, 8:45 AM2022-10-15 00:08:27 normalization > 128 of 132 OK created incremental model <table name removed> ....................................... [INSERT 0 12446501 in 17788.85s]
胡得潮
10/17/2022, 8:57 AMAndrew Exlet
10/17/2022, 11:14 AMRobert Put
10/17/2022, 1:44 PMSiddhant Singh
10/17/2022, 11:18 AMEric Lamphere
10/17/2022, 2:51 PMrequests.exceptions.HTTPError: 404 Client Error: Not Found for url: <https://templestclair.myshopify.com/admin/api/2021-07/shopify_payments/balance/transactions.json?limit=250&order=id+asc&since_id=0>
It seems like there's been some discussion around this on GH. Does anyone know if this issue has been fixed? Note: I'm connecting with the OAuth methodOyindamola Olatunji
10/17/2022, 4:13 PM# In your workstation terminal
ssh -i $SSH_KEY -L 8000:localhost:8000 -N -f ec2-user@$INSTANCE_IP
Just visit <http://localhost:8000> in your browser and start moving some data!
Lucas Gonthier
10/17/2022, 4:20 PMSid Lais
10/17/2022, 6:32 PMJing Xu
10/17/2022, 6:40 PMGenerating airbyte_ctes/AIRBYTE/CUSTOMER_AB1.sql from CUSTOMER
Generating airbyte_views/AIRBYTE/CUSTOMER_AB2.sql from CUSTOMER
Generating airbyte_views/AIRBYTE/CUSTOMER_AB3.sql from CUSTOMER
Generating airbyte_tables/AIRBYTE/ACCOUNT.sql from CUSTOMER
Generating airbyte_ctes/AIRBYTE/EVENT_AB1.sql from Event
Generating airbyte_ctes/AIRBYTE/EVENT_AB2.sql from Event
Generating airbyte_ctes/AIRBYTE/EVENT_AB3.sql from Event
Generating airbyte_tables/AIRBYTE/EVENT.sql from Event
Kevin Chan
10/17/2022, 8:01 PMFailure Origin: persistence, Message: Something went wrong during state persistence
? Activity failure. ActivityId=4f668877-8765-38e1-a288-02dac0332e72, activityType=Persist, attempt=1
java.lang.IllegalStateException: Job ran during migration from Legacy State to Per Stream State. One of the streams that did not have state is: io.airbyte.protocol.models.StreamDescriptor@6ffb8e41[name=clients,namespace=<null>,additionalProperties={}]. Job must be retried in order to properly store state.
Liyin Qiu
10/17/2022, 11:15 PMRobert Put
10/18/2022, 4:15 AM