Query events API using parameter attributes.command_id==<COMMAND_ID>
Instead, we must query on “attributes.command==HiveReplicationCommand” and parse the entire return to isolate the value of interest. This is a concern due to an ever increasing payload on the returned object.
Can the above query issue be investigated?
Another observation is that the BDR replication API does not support invocation / query by scheduleName.
We find this is an issue for route-to-live, as for example it is not possible to define the scheduleName in metadata in advance for onward deployment. We must create the jobs first and then capture the ID value in metadata.