Hi Team,
When I run sync with normalization enabled, observed that the sync process creates source and destination catalog files. Which happens to be the same.
Would like to understand the purpose of having same files with different names ?
Hi Team,
When I run sync with normalization enabled, observed that the sync process creates source and destination catalog files. Which happens to be the same.
Would like to understand the purpose of having same files with different names ?
source_catalog.json
is used during the read step from the source.
destination_catalog.json
is used during the write and normalization step for the destination.
They are very similar but there is a small difference the destination have the final stream name and stores the namespace of the destination.
Probably in the future it’s possible to refactor the code to have a unify catalog between source and destination.
Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.