{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/6c7c93bb2def43bd93722ab1cafd6938\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/6c7c93bb2def43bd93722ab1cafd6938-bdc0ecb891c49a1b.gif","duration":147.851,"title":"FullSync Parameter for Node Sync Updates","description":"This Loom discusses a change to how build change nodes are created during SyncAllNodesInRelation by adding a FullSync parameter. The author sets FullSync to true for the SyncAllNodesInRelation path (default false otherwise) and, when FullSync is enabled, compares source local IDs of nodes against the existing AllNodes map using a set difference to include missing nodes without short-circuiting. They then test behavior by removing a node from concepts, showing that periodic sync clears it, while running SyncAllNodesInRelation brings the concept back in the database. They conclude by verifying the change worked, noting some unexpected redundancy in the concept results and “last modified text” data."}