Change Details

Client wikis that have useLegacyChangesSubscription=false can be serviced using wb_changes_subscription, while other client wikis need to be serviced the old way, using wb_items_per_site. It's probably best to use a union of the info from both tables, until we are confident that we can rely on wb_changes_subscription alone.

Client wikis that have useLegacyChangesSubscription=false can be serviced using wb_changes_subscription, while other client wikis need to be serviced the old way, using wb_items_per_site. It's probably best to use a union of the info from both tables, until we are confident that we can rely on wb_changes_subscription alone. NOTE: update migration instructions in usagetracking-migration.wiki to mention configuration of the hybrid mode.

Client wikis that have useLegacyChangesSubscription=false can be serviced using wb_changes_subscription, while other client wikis need to be serviced the old way, using wb_items_per_site. It's probably best to use a union of the info from both tables, until we are confident that we can rely on wb_changes_subscription alone. NOTE: update migration instructions in usagetracking-migration.wiki to mention configuration of the hybrid mode.