Troubleshooting and FAQs
General Questions
Is the pricing model fixed?
Our standard pricing can always be adapted to special customer requirements.
What is the procedure for new features or bug fix requests?
The paid license includes an annual maintenance fee that covers patches for bugs and vulnerabilities.
In order to deliver patches quickly, customers are notified when a new version is released, and can download it directly from the INIT repository.
What is the ETA for new features or bug fix requests?
The ETA for bug fixes is usually a couple of days.
What kind of service is included in the annual maintenance fee?
The annual maintenance fee includes all patches provided to fix bugs, security issues, transitive library updates, etc.
It does not include, for example, potentially major enhancements to the functionality of the software. These enhancements may be made available through minor and major release updates. This is comparable to major release upgrades of other software systems. We reserve the right to charge an upgrade fee for these.
Where can I find more documentation about the INIT Connectors?
For an overview of the INIT connector portfolio, visit our Kafka Connectivity - INIT product page. It also contains links to more detailed documentation.
Connector Features
Can the connector be used with different converters (like Avro, JSON or Protobuf), SMTs, JMX based monitoring, Rest-API, and Rest-based UIs?
Yes, the connector is implemented against the Kafka Connect API and therefore fully integrated into Kafka Connect with all its functional possibilities.
Do Kafka Connectors support PUSH?
By design, the Kafka Connect API does not provide PUSH for connectors. See KIP-26 - Adding the Kafka Connect framework for data import/export.
Does Confluent support running partner connectors in the Confluent Managed Cloud?
Yes, Confluent supports running partner connectors in the managed cloud, but there are a few limitations to be aware of. For more details refer to Custom Connectors for Confluent Cloud - Limitations and Support.
Does the connector depend on installing custom SAP® enhancements using transport files?
Yes, the connector zip package contains an SAP transport that must be installed on the SAP system. The transport includes a small wrapper for the aDSO RFC Write API RSDSO_WRITE_API_RFC, implementing some custom performance improvements.
Troubleshooting
How can I validate a connection for a connector?
We recommend testing each connection to a new system using our included CLI tool, before creating a new connector instance.
How to handle a ClassCastException for type INT64?
I am facing the following issue, but the corresponding field types in the aDSO seem to be of the correct type INT8.
java.lang.ClassCastException: Schema field * type INT64 cannot be cast to ....
Have a look at SAP note 2212466.