Ban and artifacts snapshots
CQL Schema changes:
CREATE TABLE minds.user_snapshots (
user_guid varint,
type text,
key text,
json_data text,
PRIMARY KEY (user_guid, type, key)
) WITH CLUSTERING ORDER BY (type ASC, key ASC);
17/17 discussions resolved
added 1 commit
- 9b179a3f - (proto): Posts, Comments and Subscriptions/Subscribers delegates
added 1 commit
- 31e5b67d - (proto): Move to Artifacts, comments should snapshot entity
added 1 commit
- 0a56c136 - (proto): Move to Artifacts, comments should snapshot entity
added 1 commit
- a58db9ea - (chore): Key serialization, snapshotable comments
added 1 commit
- f19ff274 - (chore): Always use delegates, fix comments and subs, CLI utility
added 1 commit
- 11cf756b - (refactor): Adapt to ban implementation; queue runner
added 1 commit
- 20876b2f - (test): Add Channels\Manager new methods and Channels\Snapshot
added 1 commit
- 64ee6ef2 - (feat): ElasticSearch Snapshot/Delete/Restore
unmarked as a Work In Progress
changed the description
added 1 commit
- e504da6e - (feat): Restore inverse relationship on subs
- Resolved by Mark Harding
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
added 2 commits
added 257 commits
- 4a04ab7c...8bd9d70c - 256 commits from branch
minds:master
- dd0940ad - Merge branch 'master' into sprint/Wire.feat.ban-snapshot-1
- 4a04ab7c...8bd9d70c - 256 commits from branch
added 1 commit
added 1 commit
- 1a28364e - (feat): Process subscriptions/subscribers by batches
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Resolved by Emiliano Balbuena
- Owner
I think we can greatly simplify/optimise the delete/snapshot stuff
- No need to snapshot/restore personal indexes
- No need to snapshot/restore lookup indexes
- No need to snapshot/restore entities (they can just add the 'delete' boolean to them)
- No need to download from ES (a boolean on all the owner_guids documents should suffice)
- There needs to be a distinction between hiding/deleting. I would just add another function called hide(), and if it is a delete operation for that delegate, it will just pass though as delete
added 16 commits
- 8c808555...9b4c685a - 15 commits from branch
minds:master
- 6cba56f6 - Merge remote-tracking branch 'upstream/master' into sprint/Wire.feat.ban-snapshot-1
- 8c808555...9b4c685a - 15 commits from branch
added 9 commits
- 6cba56f6...678abba9 - 8 commits from branch
minds:master
- a552f1de - Merge branch 'master' into sprint/Wire.feat.ban-snapshot-1
- 6cba56f6...678abba9 - 8 commits from branch
added 1 commit
- 03070565 - (refactor): Add hide() and optimize/simplify processes
added 25 commits
- 85776525...a11370c5 - 24 commits from branch
minds:master
- a82b01ae - Merge remote-tracking branch 'upstream/master' into sprint/Wire.feat.ban-snapshot-1
- 85776525...a11370c5 - 24 commits from branch
added 1 commit
- 1b9c9dd7 - (chore): Use string as queue name; use DI for Channels classes
resolved all discussions
Please register or sign in to reply