When resolving issue #189 , we found that the github profile can be stored with new engine that will remove duplication, by keeping (github id, updated_at) fields tuple distinct. Which indeed defines a snap shot of a profile at a particular time.
So after changing the new engine, it is possible to sync github profile from remote clickhouse serivce by compare the search_key__updated_at and the new engine will keep removing duplication.
When resolving issue #189 , we found that the github profile can be stored with new engine that will remove duplication, by keeping (github id, updated_at) fields tuple distinct. Which indeed defines a snap shot of a profile at a particular time.
So after changing the new engine, it is possible to sync github profile from remote clickhouse serivce by compare the
search_key__updated_at
and the new engine will keep removing duplication.