`contributor_repo` table does not relate to `repo`
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The contributor_repo table is filled by the contributor breadth worker; inspect that worker and the database schema to see how repo_git and gh_repo_id are written. First read the worker code and any migration scripts, then discuss with maintainers whether to link to repo via repo_src_id. Done means an agreed plan to reclaim space and add the foreign key before multi-forge support.
由索引模型根据 Issue 内容生成。
描述
the contributor_repo table does not have a foreign key to the repo table.
It has its own repo_git column and repo_name column which i dont believe is getting updated when repos move/get renamed. it appears to store events from the github events api (such as PushEvent and CreateEvent). Do we want to keep storing the historical names as they were when the data was collected? the urls seem likely redundant.
We do also have a gh_repo_id column so we can maybe associate this table with repo using the repo_src_id - this would be best to do before we move over to supporting other forges, otherwise this migration may be more difficult
In our 42k repo instance, this table is ~120GB
This table seems to be filled in by the contributor breadth worker.
The unique key on this table seems to be up to ~1.4 billion (im pretty sure its an autoincrement integer)
I suspect this table also has not been the target of any deletion queries we have ever run on this database
This table does not appear to be used by 8Knot but may be used by DSWG notebooks (and some internal stuff)
What should we do to make this table a more sensible use of space?
- 主要语言
- Python
- 星标
- 17
- 派生
- 30
- 平均合并
- 6 小时 16 分钟
- 30 天内合并 PR
- 9
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
chaoss/CollectOSS 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
chaoss/CollectOSS#548 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
chaoss/CollectOSS#521 ·
维护者通常 1 天内回复
-
mask keys by default when checking API key expiry可能已有人在做 @iGufrankhan 于 139 天前认领。 未关闭challenging first issue CLI
难度 2/5 1-3 小时 新手友好度 68/100
chaoss/CollectOSS#414 · 2 条评论 ·
维护者通常 1 天内回复
-
challenging first issue CLI
难度 2/5 1-3 小时 新手友好度 68/100
chaoss/CollectOSS#413 · 3 条评论 ·
维护者通常 1 天内回复
-
Output current time alongside API key reset time可能已有人在做 @Dipro-cyber 于 145 天前认领。 未关闭CLI good first issue
难度 2/5 1-3 小时 新手友好度 68/100
chaoss/CollectOSS#412 · 1 条评论 ·
维护者通常 1 天内回复
查看 chaoss/CollectOSS 的全部 Issue
相似的 Issue
-
integration: media_player
难度 2/5 1-3 小时 新手友好度 82/100
home-assistant/core#193344 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
daniel-ospina/tortoise#13607 ·
维护者通常 1 天内回复
-
documentation priority: medium
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复