We are relying on the nested field source.ts_ms to track creation/update times where the source table doesn't have or misuses corresponding columns. It would be great if the SMT could be configured to support this, or better yet if both timestamps were kept around.
We are relying on the nested field
source.ts_ms
to track creation/update times where the source table doesn't have or misuses corresponding columns. It would be great if the SMT could be configured to support this, or better yet if both timestamps were kept around.