You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The client version: 2.2.0
The problem description:
We use snowflake ingest SDK to send data from our system to Snowflake. After updating SDK version to the newest one, we stopped getting 2 out of 3 errors (mentioned in the linked issue) but one of them still showed up:
"05:27:51.195 [�[32m�[0;39m] [�[32m�[0;39m] [�[34mingest-register-thread�[0;39m] �[1;31mERROR�[0;39m �[36mn.s.i.s.internal.RegisterService�[0;39m - [SF_INGEST] Building or uploading blob failed, client=9985d5b9-abac-4f67-b0f3-5ea24c504ee4, file=2024/8/26/5/25/sit8ey_qjd3TDS8bf81l1Bhsc2aynCppcFqtNiDiMFAAjAAoiZ4kCC_1014_2587_11.bdec, exception=java.util.concurrent.TimeoutException, detail=null, cause=null, cause_detail=null, cause_trace=null all channels in the blob will be invalidated"
Since 22th August it happened only once for now (previously it was happening more often) but it still caused the loss of data. We cannot specify when it happens exactly.
The text was updated successfully, but these errors were encountered:
Following this issue #806
The client version: 2.2.0
The problem description:
We use snowflake ingest SDK to send data from our system to Snowflake. After updating SDK version to the newest one, we stopped getting 2 out of 3 errors (mentioned in the linked issue) but one of them still showed up:
"05:27:51.195 [�[32m�[0;39m] [�[32m�[0;39m] [�[34mingest-register-thread�[0;39m] �[1;31mERROR�[0;39m �[36mn.s.i.s.internal.RegisterService�[0;39m - [SF_INGEST] Building or uploading blob failed, client=9985d5b9-abac-4f67-b0f3-5ea24c504ee4, file=2024/8/26/5/25/sit8ey_qjd3TDS8bf81l1Bhsc2aynCppcFqtNiDiMFAAjAAoiZ4kCC_1014_2587_11.bdec, exception=java.util.concurrent.TimeoutException, detail=null, cause=null, cause_detail=null, cause_trace=null all channels in the blob will be invalidated"
Since 22th August it happened only once for now (previously it was happening more often) but it still caused the loss of data. We cannot specify when it happens exactly.
The text was updated successfully, but these errors were encountered: