cleanup.policy
of the __kafka_connect_offset_storage
topic to compact
to avoid the above error with below command:test
on Streamnative Cloud using different tools.
test
, run the following command.test
on StreamNative Cloud using different tools.
Please refer to the Kafka Connect SMTs to check the supported SMTs in StreamNative cloud.
test
with SMT, run the following command.location
should be the same as the region of your Pulsar cluster.The awsAccessKey
and awsSecretKey
is the field name, and the lambda-sink-secret
can be any unique name you want to give to the secret.For a Milvus sink, we should create a secret with a token
field.test
on Streamnative Cloud using different tools.
test
, run the following command.miluvs-sec
is the name of the secret you createdlibDir
specifies the directory where the third-party libraries are located in the zip file.mongo-source
on Streamnative Cloud using different tools.
mongo-source
, run the following command.sn.pulsar.package.url
is the package url you uploaded to the StreamNative Cloud Package service.sn.cpu
: The number of CPU cores to allocate to the connector, default to 0.5.sn.memory
: The bytes of memory to allocate to the connector, default to 2147483648 (2G).v3.0.8.4+
, v3.3.3.4+
or v4.0.1.3+
to use the sn.cpu
and sn.memory
configs.value.converter.schema.registry.internal: true
: if you want to use the internal schema registry for the value converter.key.converter.schema.registry.internal: true
: if you want to use the internal schema registry for the key converter.