Before we can split RESTBase, we need to clean up and simplify the storage semantics. Concretely, we need to get rid of the key_rev_value bucket and possibly re-engineer the way we use the multi_key_value bucket.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | WDoranWMF | T220449 Split RESTBase in two services: storage service and API router/proxy | |||
Resolved | • mobrovac | T220461 Simplify storage semantics | |||
Resolved | • Pchelolo | T215960 Simplify MCS storage model | |||
Resolved | • Pchelolo | T215987 Verify that hit/miss stats in WebRequest are correct | |||
Resolved | Eevans | T221031 Create new mobile storage tables | |||
Resolved | Eevans | T221530 Drop old mobile-sections keyspaces | |||
Resolved | • Pchelolo | T215956 Consider stashing data-parsoid for VE | |||
Resolved | Eevans | T221528 Create new Parsoid tables | |||
Resolved | • mobrovac | T222639 VisualEditor should request Parsoid HTML with ?stash=true query parameter | |||
Resolved | • Pchelolo | T216636 Consider deprecating section editing API in RESTBase | |||
Resolved | • mobrovac | T223998 Remove old (a.k.a NG) Parsoid tables | |||
Resolved | • mobrovac | T224055 Rate-limit requests in parsoid.js that use stashing |
Event Timeline
Comment Actions
Both Parsoid and MCS storage are now using only binary key/value buckets for their storage needs and key_rev_value and multi_bucket are not used anymore, so this task is now complete.