New changelog reader options: mds_has_lu553 and mds_has_lu1331.
It is not possible without being intrusive to know whether the MDS supports either LU-543 or LU-1331, which are both used for renames.
To check whether each option must be set, create two files in an empty directory and move one onto the other:
  touch foo1 foo2
  mv foo1 foo2

Then look at the changelogs (08RNMFM and 09RNMTO):
22500778 08RNMFM 18:28:03.944224249 2013.05.23 0x0 t=[0x2000032e0:0x1107:0x0] p=[0x68300001:0xf6bf042a:0x0] foo1
22500779 09RNMTO 18:28:03.944224249 2013.05.23 0x0 t=[0x2000032e0:0x1107:0x0] p=[0x68300001:0xf6bf042a:0x0] foo2

If the 't' fields is the same, then both mds_has_lu543 and mds_has_lu1331 must be set to FALSE.
If the 't' fields are different, then mds_has_lu543 is TRUE.
If the event flag (hexadecimal number before "t=[") has its bit one set (0x1), then mds_has_lu1331 is TRUE. If it is not set (0x0), then mds_has_lu1331 is FALSE.

Remove the configure options --enable-cl-rename-overwrite and --enable-lu543 since the client's capabilities do not reflect those of the server.
When using changelog with Lustre, if a file doesn't exists anymore on the filesystem, we'll get an UNLINK record eventually.
If the file has been remove by we get some record related to it (such as ATIME. CLOSE, ...), the pipeline tries to delete the record, which lead to the following error:

... [23133/4]: ListMgr | Missing mandatory attribute name to ListMgr_Remove
... [23133/4]: EntryProc | Error 12 performing database operation.

There's no need to complicate the pipeline, since at some point an UNLINK event will happen, so just ignore that record.