Carolina Buckler
06/08/2023, 6:47 PMNaren Kadiri
06/08/2023, 7:41 PMAlexander Ettingshausen
06/08/2023, 8:13 PMJamshid Hashimi
06/08/2023, 10:56 PM2023-06-08 22:25:41 replication-orchestrator > failures: [ {
"failureOrigin" : "destination",
"failureType" : "system_error",
"internalMessage" : "('Connection aborted.', timeout('The write operation timed out'))",
"externalMessage" : "Something went wrong in the connector. See the logs for more details.",
"metadata" : {
"attemptNumber" : 2,
"jobId" : 2509946,
"from_trace_message" : true,
"connector_command" : "write"
},
"stacktrace" : "Traceback (most recent call last):\n File \"/usr/local/lib/python3.9/site-packages/requests/adapters.py\", line 489, in send\n resp = conn.urlopen(\n File \"/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py\", line 787, in urlopen\n retries = retries.increment(\n File \"/usr/local/lib/python3.9/site-packages/urllib3/util/retry.py\", line 550, in increment\n raise six.reraise(type(error), error, _stacktrace)\n File \"/usr/local/lib/python3.9/site-packages/urllib3/packages/six.py\", line 769, in reraise\n raise value.with_traceback(tb)\n File \"/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py\", line 703, in urlopen\n httplib_response = self._make_request(\n File \"/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py\", line 398, in _make_request\n conn.request(method, url, **httplib_request_kw)\n File \"/usr/local/lib/python3.9/site-packages/urllib3/connection.py\", line 239, in request\n super(HTTPConnection, self).request(method, url, body=body, headers=headers)\n File \"/usr/local/lib/python3.9/http/client.py\", line 1285, in request\n self._send_request(method, url, body, headers, encode_chunked)\n File \"/usr/local/lib/python3.9/http/client.py\", line 1331, in _send_request\n self.endheaders(body, encode_chunked=encode_chunked)\n File \"/usr/local/lib/python3.9/http/client.py\", line 1280, in endheaders\n self._send_output(message_body, encode_chunked=encode_chunked)\n File \"/usr/local/lib/python3.9/http/client.py\", line 1079, in _send_output\n self.send(chunk)\n File \"/usr/local/lib/python3.9/http/client.py\", line 1001, in send\n self.sock.sendall(data)\n File \"/usr/local/lib/python3.9/ssl.py\", line 1204, in sendall\n v = self.send(byte_view[count:])\n File \"/usr/local/lib/python3.9/ssl.py\", line 1173, in send\n return self._sslobj.write(data)\nurllib3.exceptions.ProtocolError: ('Connection aborted.', timeout('The write operation timed out'))\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"/airbyte/integration_code/main.py\", line 11, in <module>\n DestinationTypesense().run(sys.argv[1:])\n File \"/usr/local/lib/python3.9/site-packages/airbyte_cdk/destinations/destination.py\", line 119, in run\n for message in output_messages:\n File \"/usr/local/lib/python3.9/site-packages/airbyte_cdk/destinations/destination.py\", line 113, in run_cmd\n yield from self._run_write(config=config, configured_catalog_path=parsed_args.catalog, input_stream=wrapped_stdin)\n File \"/usr/local/lib/python3.9/site-packages/airbyte_cdk/destinations/destination.py\", line 49, in _run_write\n yield from self.write(config=config, configured_catalog=catalog, input_messages=input_messages)\n File \"/airbyte/integration_code/destination_typesense/destination.py\", line 50, in write\n writer.flush()\n File \"/airbyte/integration_code/destination_typesense/writer.py\", line 34, in flush\n self.client.collections[self.steam_name].documents.import_(self.write_buffer)\n File \"/usr/local/lib/python3.9/site-packages/typesense/documents.py\", line 60, in import_\n api_response = <http://self.api_call.post|self.api_call.post>(self._endpoint_path('import'), docs_import, params, as_json=False)\n File \"/usr/local/lib/python3.9/site-packages/typesense/api_call.py\", line 141, in post\n return self.make_request(<http://requests.post|requests.post>, endpoint, as_json,\n File \"/usr/local/lib/python3.9/site-packages/typesense/api_call.py\", line 127, in make_request\n raise last_exception\n File \"/usr/local/lib/python3.9/site-packages/typesense/api_call.py\", line 101, in make_request\n r = fn(url, headers={ApiCall.API_KEY_HEADER_NAME: self.config.api_key}, **kwargs)\n File \"/usr/local/lib/python3.9/site-packages/requests/api.py\", line 115, in post\n return request(\"post\", url, data=data, json=json, **kwargs)\n File \"/usr/local/lib/python3.9/site-packages/requests/api.py\", line 59, in request\n return session.request(method=method, url=url, **kwargs)\n File \"/usr/local/lib/python3.9/site-packages/requests/sessions.py\", line 587, in request\n resp = self.send(prep, **send_kwargs)\n File \"/usr/local/lib/python3.9/site-packages/requests/sessions.py\", line 701, in send\n r = adapter.send(request, **kwargs)\n File \"/usr/local/lib/python3.9/site-packages/requests/adapters.py\", line 547, in send\n raise ConnectionError(err, request=request)\nrequests.exceptions.ConnectionError: ('Connection aborted.', timeout('The write operation timed out'))\n",
"timestamp" : 1686263140893
}, {
"failureOrigin" : "destination",
"internalMessage" : "Destination process exited with non-zero exit code 1",
"externalMessage" : "Something went wrong within the destination connector",
"metadata" : {
"attemptNumber" : 2,
"jobId" : 2509946,
Martin Jung
06/09/2023, 2:43 AMairbyte_api_client.exceptions.ApiTypeError: Invalid type for variable '0'. Required value type is SelectedFieldInfo and passed type was dict at ['selected_fields'][0]
. Is this because the CLI version doesn't match the Airbyte version, and if so, is there a release for Octavia CLI coming soon? I'm using the Docker image for octavia-cli.Chidambara Ganapathy
06/09/2023, 5:14 AMGary K
06/09/2023, 6:20 AMRishav Sinha
06/09/2023, 8:37 AMChidambara Ganapathy
06/09/2023, 8:52 AMMarc Fiani
06/09/2023, 9:51 AMGaëtan Podevijn
06/09/2023, 1:54 PMThe Airbyte platform relies on the existing Airbyte protocol primitives to implement schema propagation: the same DiscoverSchema operation that is being run when a user sets up a new connection is also being run automatically before sync. The platform then compares the newly fetched schema with the one that is currently stored from replication.
So I would expect that before each sync is triggered, Airbyte checks for schema changes and propagates the changes (if the option is selected of course).
I tried it with the version of the destination-databricks
version that supports schema evolution and with a postgres source configured with CDC.
However, it seems that Airbyte does not check for schema changes before the sync, or I did something wrong.
Are there any logs I should check in order to verify that there is a schema change detection before a sync is triggered? Thanks!Victor Babichev
06/09/2023, 2:13 PMJose Viera
06/09/2023, 4:38 PMSlackbot
06/09/2023, 5:48 PMSlackbot
06/09/2023, 5:51 PMOctavia Squidington III
06/09/2023, 7:45 PMMatheus Barbosa
06/09/2023, 10:14 PMMatheus Barbosa
06/09/2023, 10:22 PM22:20:30.400832 [error] [MainThread]: Code: 190. DB::Exception: Elements 'ad_group.excluded_parent_asset_field_types' and 'ad_group.targeting_s__g.target_restrictions' of Nested data structure 'ad_group' (Array columns) have different array sizes. (SIZES_OF_ARRAYS_DOESNT_MATCH)
kigland
06/09/2023, 11:29 PMkigland
06/10/2023, 12:04 AMVikas Bansal
06/10/2023, 1:01 PMWisnu Jinawi
06/12/2023, 12:17 AMKrutik Pathak
06/12/2023, 5:32 AMJan Vermeulen
06/12/2023, 7:43 AMJosefin Winberg
06/12/2023, 8:36 AMFaris
06/12/2023, 9:26 AMERROR i.a.w.i.VersionedAirbyteStreamFactory(internalLog):308 - unknown exception while pinging elasticsearch server
Stack Trace: ElasticsearchStatusException[Elasticsearch exception [type=security_exception, reason=unable to authenticate with provided credentials and anonymous access is not allowed for this request]]
at org.elasticsearch.rest.BytesRestResponse.errorFromXContent(BytesRestResponse.java:176)
at org.elasticsearch.client.RestHighLevelClient.parseEntity(RestHighLevelClient.java:1900)
at org.elasticsearch.client.RestHighLevelClient.parseResponseException(RestHighLevelClient.java:1877)
at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1634)
at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1606)
at org.elasticsearch.client.RestHighLevelClient.performRequestAndParseEntity(RestHighLevelClient.java:1573)
at <http://org.elasticsearch.client.RestHighLevelClient.info|org.elasticsearch.client.RestHighLevelClient.info>(RestHighLevelClient.java:774)
at io.airbyte.integrations.source.elasticsearch.ElasticsearchConnection.checkConnection(ElasticsearchConnection.java:101)
at io.airbyte.integrations.source.elasticsearch.ElasticsearchSource.check(ElasticsearchSource.java:51)
at io.airbyte.integrations.base.IntegrationRunner.runInternal(IntegrationRunner.java:125)
at io.airbyte.integrations.base.IntegrationRunner.run(IntegrationRunner.java:100)
at io.airbyte.integrations.source.elasticsearch.ElasticsearchSource.main(ElasticsearchSource.java:34)
Suppressed: org.elasticsearch.client.ResponseException: method [GET], host [<https://vsm-dev-cpu-optimized.es.eu-central-1.aws.cloud.es.io>], URI [/], status line [HTTP/1.1 401 Unauthorized]
{"error":{"root_cause":[{"type":"security_exception","reason":"unable to authenticate with provided credentials and anonymous access is not allowed for this request","additional_unsuccessful_credentials":"API key: invalid credentials","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}}],"type":"security_exception","reason":"unable to authenticate with provided credentials and anonymous access is not allowed for this request","additional_unsuccessful_credentials":"API key: invalid credentials","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}},"status":401}
at org.elasticsearch.client.RestClient.convertResponse(RestClient.java:326)
George Myrianthous
06/12/2023, 10:34 AMcategory
was removed).
I wanted to ask, how can we potentially disable/ignore any breaking schema changes? In this case, I would expect the connection to keep syncing using the old schema, unless I take a certain action on it. And given that I haven’t updated the connection version, I wouldn’t expect to see any changes at all.
Refreshing the source schema and reloading all the data from the very beginning every time this happens is not an option for us, due to the extremely high volume of data we ingest from Mixpanel.
Can someone shed some light on this? 🙏Juan Carbon
06/12/2023, 2:01 PMOctavia Squidington III
06/12/2023, 7:45 PMmangole
06/12/2023, 9:08 PM