This has actually been in production for quite a while. Some related tasks are still pending, but there is no need to keep the general "we need a content archiver" task open anymore.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 12 2017
Feb 10 2017
Feb 9 2017
The initial count has been done:
Feb 7 2017
The counting strategy has been implemented in rDSTO598114c5da.
Jan 26 2017
Jan 13 2017
As explained on irc, there is actually a pagination.
The last element is used to create a new /revision/log/ link to follow in the 'next_urls_rev' key.
Jan 12 2017
See comment in T626, about code reuse and whether or not remove the underlying storage manager limit.
To this day, there is only a limit (propery configuration) to what's returned.
Remove such limit.
Jan 10 2017
Dec 17 2016
Deployment finished by olasd.
Dec 16 2016
Deployment finished by olasd.
Dec 15 2016
Nov 8 2016
So, after discussion with @olasd:
- PartitionKey: content ID
- RowKey: {revision_timestamp}_{revision ID} (without trailing sequential no)
Nov 7 2016
We need to generate RowKeys that are:
Sep 29 2016
Sep 26 2016
Sep 23 2016
Sep 22 2016
Sep 20 2016
Sep 15 2016
we need to add the new table for repository snapshot objects, but also rework origin_visit & friends to cope
Sep 5 2016
Sep 2 2016
Sep 1 2016
Fully implemented in rDSTO963634dca6ba
Aug 30 2016
The branch information on cache_revision_origin makes the complexity and redundancy of this task explode.
Aug 29 2016
Aug 26 2016
That's accurate, @ardumont. Nothing to add. Thanks for the puppet stuff!
An update on this, there are 3 checker implementations (all of them are puppetized independently):
Aug 24 2016
Aug 23 2016
Aug 22 2016
Aug 19 2016
The listening side of this (rDSTOd74b3e51f320) has now been deployed (rSPPROF2be94777ce21)