Kanban style board for work scheduled for Q1 FY24-25
Details
Nov 26 2024
Change #1062430 merged by jenkins-bot:
[operations/mediawiki-config@master] config: remove eventbus instrumentation setting
Nov 4 2024
There was never an answer to some questions there.
Oct 31 2024
I'm looking at this in reference to releasing some projects, initially search/extra, search/extra-analysis, and search/highlighter, from gerrit. I see we didn't test releasing from gerrit yet. I suppose my main question is where should gerrit repos publish in gitlab? It seems either we create a project per repo, or we use a shared repo. I'm not fully versed in gitlab, but the access tokens i've used so far are per-repo. Shared repo would mean shared secret instead of per-project. Also i believe access tokens are max 1 year, so they will need rotation.
Oct 23 2024
Oct 11 2024
Oct 9 2024
Change #1078923 had a related patch set uploaded (by Gmodena; author: Gmodena):
[operations/deployment-charts@master] dse-k8s-services: content_history: version bump image.
Oct 8 2024
!!! amazing!
It isn't yet, but I think it will be? There are others that are ingested. mediawiki.page_change.v1, but it only has one partition.
The switchover has been done. The gerrit repositories are deprecated(set to read-only) and the schema servers have all been updated with the gitlab urls with @BTullis support.
Ah! I had forgotten :) But this st4ream is not ingested in hadoop.
Anyhow, if you agree with the approach, I can implement it.
keyed-topics is theoretical for us as we don't use them
FWIW, we do use them:
Our algorithm about flagging folders is working at topic-partition-level for high-volume topics, and at topic-level for low-volume topics. It doesn't really make sense to mix them.
My suggested solution would be to discard low-volume topic-partitions from high-volume topics. I think this would cover the issue.