Custom destination connector does not support file transfers

[toukoum]

@stephane-airbyte

Hello,

I’m encountering an issue while developing a custom destination connector using the Python CDK. I need to enable file transfers, so I configured my metadata.yaml with:

connectorSubtype: file
supportsFileTransfer: true

However, when I try to sync on my local Airbyte instance (using Google Drive as the source), I get the following error:

Exception message: Destination does not support file transfers, but source requires it. The destination version is: dev-1.
Type: io.airbyte.workers.exception.WorkerException

I build my connector image with the following command:

airbyte-ci connectors --name=destination-paradigm build --tag dev

Despite ensuring that metadata.yaml is correctly configured and included (using a MANIFEST.in, rebuilding without cache, etc.), Airbyte still does not detect that my destination supports file transfers.

I haven’t found much documentation on this issue. Could you please help me understand what might be going wrong or provide any guidance to resolve this?

Thanks in advance for your help!

[valentinpotie]

Hi,

I’m facing the same issue while developing a custom destination connector with the Python CDK. I’ve also set connectorSubtype: file and supportsFileTransfer: true in my metadata.yaml, but Airbyte doesn’t recognize that my destination supports file transfers.

I’ve tried rebuilding the connector without cache and ensuring the metadata is correctly included, but I still get the same error:

Destination does not support file transfers, but source requires it.

It would be great to get some guidance on this. Looking forward to a solution!

Thanks!