You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello I am getting this error with the connector version 2.10.x. I installed it over confluent hub.
Connector Creation: validating the connector config for connector blob-to-kafka resulted in the following errors: Found error for field fs.listing.class: Invalid value io.streamthoughts.kafka.connect.filepulse.fs.AzureBlobStorageFileSystemListing for configuration fs.listing.class: Class io.streamthoughts.kafka.connect.filepulse.fs.AzureBlobStorageFileSystemListing could not be found.
I was doing some research on the issues and it seems the packaging could go wrong the last time you uploaded it to confluent hub. I will try to install it manually
The text was updated successfully, but these errors were encountered:
Hi @irux, thank you for reporting this issue. Do you get the same error with the latest release 2.13.0 ? Please note that Filepulse is no longer available on Confluent Hub due to a new Confluent security policy that has excluded a large number of connectors.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hello I am getting this error with the connector version 2.10.x. I installed it over confluent hub.
Connector Creation: validating the connector config for connector blob-to-kafka resulted in the following errors: Found error for field fs.listing.class: Invalid value io.streamthoughts.kafka.connect.filepulse.fs.AzureBlobStorageFileSystemListing for configuration fs.listing.class: Class io.streamthoughts.kafka.connect.filepulse.fs.AzureBlobStorageFileSystemListing could not be found
.I was doing some research on the issues and it seems the packaging could go wrong the last time you uploaded it to confluent hub. I will try to install it manually
The text was updated successfully, but these errors were encountered: