Issue connecting Postgres source to Typesense destination

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

The user is facing an issue while trying to connect a Postgres source to a Typesense destination. The error message indicates a connection error with a NameResolutionError.


Question

Hey Guys, I was hoping to connect Postgres source to the typesense destination. While creating the new destination with typesense I am facing this issue:

2024-07-19 11:33:05 platform > Docker volume job log path: /tmp/workspace/b4c703e7-874c-4714-8203-d3616ed98b16/0/logs.log
2024-07-19 11:33:05 platform > Executing worker wrapper. Airbyte version: 0.63.8
2024-07-19 11:33:05 platform > 
2024-07-19 11:33:05 platform > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: '2.0'
2024-07-19 11:33:05 platform > ----- START CHECK -----
2024-07-19 11:33:05 platform > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: '2.0'
2024-07-19 11:33:05 platform > 
2024-07-19 11:33:05 platform > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: '0.1'
2024-07-19 11:33:05 platform > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: '0.1'
2024-07-19 11:33:05 platform > Checking if airbyte/destination-typesense:0.1.12 exists...
2024-07-19 11:33:05 platform > airbyte/destination-typesense:0.1.12 was found locally.
2024-07-19 11:33:05 platform > Creating docker container = destination-typesense-check-b4c703e7-874c-4714-8203-d3616ed98b16-0-vhwif with resources io.airbyte.config.ResourceRequirements@1f3be184[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=,additionalProperties={}] and allowedHosts null
2024-07-19 11:33:05 platform &gt; Preparing command: docker run --rm --init -i -w /data/b4c703e7-874c-4714-8203-d3616ed98b16/0 --log-driver none --name destination-typesense-check-b4c703e7-874c-4714-8203-d3616ed98b16-0-vhwif --network host -v airbyte_workspace:/data -v oss_local_root:/local -e DEPLOYMENT_MODE=OSS -e WORKER_CONNECTOR_IMAGE=airbyte/destination-typesense:0.1.12 -e AUTO_DETECT_SCHEMA=true -e LAUNCHDARKLY_KEY= -e SOCAT_KUBE_CPU_REQUEST=0.1 -e SOCAT_KUBE_CPU_LIMIT=2.0 -e FIELD_SELECTION_WORKSPACES= -e USE_STREAM_CAPABLE_STATE=true -e WORKER_ENVIRONMENT=DOCKER -e AIRBYTE_ROLE=dev -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e OTEL_COLLECTOR_ENDPOINT=<http://host.docker.internal:4317> -e FEATURE_FLAG_CLIENT=config -e AIRBYTE_VERSION=0.63.8 -e WORKER_JOB_ID=b4c703e7-874c-4714-8203-d3616ed98b16 airbyte/destination-typesense:0.1.12 check --config source_config.json
2024-07-19 11:33:05 platform &gt; Reading messages from protocol version 0.2.0
2024-07-19 11:33:10 platform &gt; Check connection job received output: io.airbyte.config.StandardCheckConnectionOutput@6e4c65cf[status=failed,message=An exception occurred: ConnectionError(MaxRetryError('HTTPSConnectionPool(host=\'ipxugriqiw7s60sqjhtoifio8orlt8pb\', port=8108): Max retries exceeded with url: /collections (Caused by NameResolutionError("&lt;urllib3.connection.HTTPSConnection object at 0xffffaa219180&gt;: Failed to resolve \'ipxugriqiw7s60sqjhtoifio8orlt8pb\' ([Errno -2] Name or service not known)"))')),additionalProperties={}]
2024-07-19 11:33:10 platform &gt; 
2024-07-19 11:33:10 platform &gt; ----- END CHECK -----
2024-07-19 11:33:10 platform &gt; ```
Is Typesense destination broken?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1721389232381089) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["postgres-source", "typesense-destination", "connection-issue", "name-resolution-error"]
</sub>
2

FYI I am tries the both OSS & Cloud version of airbyte!

3

host ipxugriqiw7s60sqjhtoifio8orlt8pb doesn’t look good

4

I am not sure why it is taking that as the host. I am putting in the right host but no luck!

5

Does it encode or something the host before connecting to it? I am not sure at this point!