Error when creating connection between DynamoDB and PostgreSQL

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

Summary

The user is facing an error while trying to create a connection between DynamoDB and PostgreSQL. The error message includes warnings about deprecated package scanning for plugins.


Question

Hey Guys, my team is trying to create a connection between dynamo and postgress but i keep getting this error. We need help in trouble shooting this. Dynamo connection and permissions are fine as well as the postgres. cc <@U06JGEYJ2UF>

- 2024-02-14 20:00:09 platform &gt; kubectl cp /tmp/034c3289-08d1-40dc-b107-66d756276c7c/FINISHED_UPLOADING jobs/dynamodb-discover-1cbfa1be-5327-4784-a22a-9c0d06123565-0-vufnf:/config/FINISHED_UPLOADING -c init --retries=3
- 2024-02-14 20:00:09 platform &gt; Waiting for kubectl cp to complete
- 2024-02-14 20:00:10 platform &gt; kubectl cp complete, closing process
- 2024-02-14 20:00:10 platform &gt; Waiting until pod is ready...
- 2024-02-14 20:00:10 platform &gt; Setting stdout...
- 2024-02-14 20:00:11 platform &gt; Setting stderr...
- 2024-02-14 20:00:11 platform &gt; Reading pod IP...
- 2024-02-14 20:00:11 platform &gt; Pod IP: 172.32.1.215
- 2024-02-14 20:00:11 platform &gt; Using null stdin output stream...
- 2024-02-14 20:00:11 platform &gt; Reading messages from protocol version 0.2.0
- 2024-02-14 20:00:12 platform &gt; WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
- 2024-02-14 20:00:12 platform &gt; WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
- 2024-02-14 20:00:12 platform &gt; WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
- 2024-02-14 20:00:12 platform &gt; WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
- 2024-02-14 20:00:12 platform &gt; 2024-02-14 20:00:12 INFO i.a.i.s.d.DynamodbSource(main):47 - starting Source: class io.airbyte.integrations.source.dynamodb.DynamodbSource
- 2024-02-14 20:00:12 platform &gt; 2024-02-14 20:00:12 INFO i.a.c.i.b.IntegrationCliParser(parseOptions):126 - integration args: {discover=null, config=source_config.json}
- 2024-02-14 20:00:12 platform &gt; 2024-02-14 20:00:12 INFO i.a.c.i.b.IntegrationRunner(runInternal):132 - Running integration: io.airbyte.integrations.source.dynamodb.DynamodbSource
- 2024-02-14 20:00:12 platform &gt; 2024-02-14 20:00:12 INFO i.a.c.i.b.IntegrationRunner(runInternal):133 - Command: DISCOVER
- 2024-02-14 20:00:12 platform &gt; 2024-02-14 20:00:12 INFO i.a.c.i.b.IntegrationRunner(runInternal):134 - Integration config: IntegrationConfig{command=DISCOVER, configPath='source_config.json', catalogPath='null', statePath='null'}
- 2024-02-14 20:00:13 platform &gt; 2024-02-14 20:00:13 WARN c.n.s.JsonMetaSchema(newValidator):278 - Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword```


<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/C027KKE4BCZ/p1708015608226439) if you want to access the original thread.

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

<sub>
["dynamo", "postgress", "connection", "error", "deprecated-package-scanning", "plugins"]
</sub>