@kapa.ai I'm getting some errors when trying to use the latest version s3 destination:

ConfigErrorException: Failed to initialize connector operation

, rooted at

java.lang.NullPointerException

in

io.airbyte.cdk.load.command.DestinationStreamFactory.make(DestinationStream.kt:204)

. I'm already on the latest airbyte version. Why would this happen?

Based on the knowledge sources, this error is a known bug related to using an official Airbyte connector image registered as a custom connector in the Airbyte UI. The root cause is that when a connector is added as a custom connector definition (even if the underlying Docker image is identical to an official catalog connector), Airbyte passes

generationId=null

,

minimumGenerationId=null

, and

syncId=null

to the destination connector. The CDK then throws a

NullPointerException

at

DestinationStreamFactory.make()

when it tries to use these null values. [Adding official connector as custom connector not working] The key detail from the issue report: > The same image (e.g.

airbyte/destination-s3-data-lake:0.3.35

) works correctly when used via the stock catalog definition but fails with this NPE when registered as a custom connector through the UI. [Adding official connector as custom connector not working] In summary: This is a platform-level bug where custom connector registrations do not properly populate the sync metadata fields that newer CDK-based connectors require. The issue has been confirmed on Airbyte versions 1.8.2 and 1.8.5. Workaround: If possible, use the connector via the official catalog definition rather than registering it as a custom connector. The knowledge sources do not mention a patch or fix having been released yet. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

I'm not using it as custom connector. What does that even mean? @kapa.ai

You're right to push back on that. A "custom connector" in Airbyte refers specifically to a connector that you register yourself through Settings > Sources/Destinations > New connector, by providing a custom Docker image name and tag, rather than using one of the pre-built connectors already listed in Airbyte's catalog. [Custom or New Connector] If you are using the S3 destination from the standard Airbyte catalog (not a self-registered custom connector definition), then the bug described in my previous answer likely does not apply to your situation. Unfortunately, the knowledge sources I have available don't contain enough information to diagnose your specific error (

ConfigErrorException

/

NullPointerException

in

DestinationStreamFactory.make

) outside of the custom connector context. I'd recommend: 1. Checking the full sync logs in the Airbyte UI for more context around the error. 2. Filing a bug report on the Airbyte GitHub issues page with your Airbyte version, connector version, and full stack trace, so the team can investigate. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

I'm using the S3 destination from the standard Airbyte catalog @kapa.ai

Thank you for clarifying. Unfortunately, the knowledge sources I have available do not contain enough information to explain why you would see a

ConfigErrorException: Failed to initialize connector operation

/

NullPointerException

in

DestinationStreamFactory.make

when using the standard catalog S3 destination on the latest Airbyte version. I'd suggest the following steps: 1. Check the full sync logs in the Airbyte UI for additional context around the error. 2. Search or file a bug report on the Airbyte GitHub issues page with your Airbyte version, S3 destination connector version, and the full stack trace. 3. Ask in the Airbyte community forum where other users or Airbyte engineers may have encountered the same issue. I'm sorry I can't be more specific — the knowledge sources simply don't have enough detail to diagnose this particular error in your scenario. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.