Closed dimstunt closed 2 years ago
@morazow, can you help me, please?
Hello @dimstunt,
Sorry, we somehow missed this issue. I am going to look into it.
Hello @dimstunt,
Thanks for the feedback!
Why in both cases I get 2 merges when creating a table
One of the is a prepare statement, the other is for actual execution. You could observe this on the "execution mode" column of the audit table.
How to fix this error?
I did check a little the code base.
The issue seems to be the deleteStatementBinder
is null, because the generic dialect does not override that interface. And we never update the prepared delete statement, but Kafka JDBC runs the statement anyway.
I have added a PR #24, that overrides statement binder. Could you please check it out?
I am going to do some updates (only in tests) then we can merge it soon.
Hello @morazow,
I tried to reproduce the case with kafka-connect-jdbc-exasol-1.0.0.jar
built from this branch
But the error was repeated exactly the same. Do I need to send something else, some kind of logs?
This project has been discontinued. Please use exasol/kafka-connector-extension for integration with Apache Kafka.
Hello,
I'm trying to run Exasol sink connector with line deletion enabled (
"delete.enabled ":"true"
). Myexasol-sink.json
looks this way:When checking the status after creation, I get this exception in docker log's message:
In
EXA_STATISTICS.EXA_DBA_AUDIT_SQL
I see this:But everything works when I turn off
delete.enabled
.In
EXA_STATISTICS.EXA_DBA_AUDIT_SQL
I see this:I do not understand
Can somebody help me?
Thanks in advance for your help.
Dmitry