fketelaars / iidr-ue-kcop Goto Github PK

Hi Frank, how are you?

I'm using your IIDR-UE-KCOP, but I got in the code at KcopLiveAuditJson.java:

/*
 * Append the apply timestamp
 */
private void addApplyTimestamp(JsonObject kafkaAuditJson) {
	String timeStamp = new SimpleDateFormat("yyyy-MM-dd HH:mm:ss.SSS000").format(new Date());
	kafkaAuditJson.addProperty(applyTimestampColumn, timeStamp);
}

This bring me the format always with rounding, but in correct format. If I use the timestamp from IIDR, it bring me without the rounding but with an incorrect form:

"2018-06-29-07.42.53.936336" - Default from IIDR
"2018-06-29 07:40:56.446000" - Your UE KCOP

Is it possible change the rounding to bring the exactly time without the rounding?

Build in handling for invalid journal control columns which have been specified in the properties file. Non-existing JCCs must be ignored and a warning message must be issued to the event log.

Even though ordering of JSON keys is not relevant for parsing and extracting the values, maintaining the order makes it easier to validate the correct output. Instead of adding JsonObject keys, create a LinkedHashMap to hold the current change record's audit columns and column values.

Hi there,

When I try to configure the User Exit for the subscription I keep getting an error:

An error in User Exit com.ibm.replication.cdc.userexit.kcop.KcopLiveAuditJson.
Error: com.datamirror.ts.target.publication.userexit.kafka.KafkaCustomOperationProcessorIF

That's all there is to the error, can't see the java exception if there is one.

I'm running Version: 11.4.10014

I'd really appreciate any assistance you can provide as we're trying to get this working for a POC project.

Thanks
Liz

Do not re-read and parse properties when they are needed; only once during the start of the subscription

Frank

We happened to look through your code since we have a need to customize the message prior to sending it to the Kafkaproducer.
Noticed that the KcopRoundRobinPartitioner writes only to partition 0. We would like the ability to write to multiple partitions(for different keys). Is that something which we can customize this KcopRoundRobinPartitioner or is there some other upstream limitation/configuration that needs to also be made. I had increased the partition count on the broker side but found that it always go to the same partition and then looked at this code/documentation
Any advice/pointers would be helpful

Thanks
Meena