Cells: Iteration 2: Identify all cross-joins between `users` and `namespaces`

Problem

As part of the Cells: Iteration 2: Make `users` to be `gitlab_... (#410370 - closed) and Cells: Iteration 2: Make `namespaces` to be `gi... (#390102 - closed) the users and namespaces become part of separate schemas. It is not allowed to cross-join across separate databases.

Currently those schemas are allowed to cross-join with due db/gitlab_schemas/gitlab_main_cell.yaml having allow_cross_joins: gitlab_main_clusterwide allow.

Steps

We should identify all cross-joins by:

1. From db/gitlab_schemas/gitlab_main_cell.yaml removing allow_cross_joins: gitlab_main_clusterwide.
2. Trying to get pipeline green, by:
   • get pipeline green by using allow_cross_joins_across_databases, and creating associated issue
   • allowlisting temporary all failed specs in spec/support/database/cross-join-allowlist.yml
3. Once identified schedule work on issues that overlap with Cells: Iteration 2: Fix all cross-joins related... (#409842 - closed)

marked this issue as related to #409840 (closed)

changed milestone to %16.2

added Category:Cell backend devopsdata stores grouptenant scale milestonep1 sectioncore platform typefeature workflowready for development labels

removed milestonep1 label

@lohrc I believe it is milestonep1 and workflowready for development once the !120605 (merged) is merged.

added to epic &9813 (closed)

marked this issue as blocked by #410370 (closed)

marked this issue as blocked by #390102 (closed)

marked this issue as blocking #409842 (closed)

mentioned in issue #409840 (closed)

added milestonep1 label

added workflowrefinement label and removed workflowready for development label

marked this issue as blocking #415207 (closed)

assigned to @OmarQunsulGitlab

Issue was refined in https://gitlab.com/gitlab-org/tenant-scale-group/group-tasks/-/issues/106#note_1435242170.

added workflowready for development label and removed workflowrefinement label

set weight to 3

added workflowin dev label and removed workflowready for development label

mentioned in commit a0f15e67

mentioned in merge request !124319 (merged)

mentioned in commit 41dc75b9

mentioned in commit 9d09bab7

mentioned in commit 8979e35a

mentioned in issue gitlab-org/quality/triage-reports#13028 (closed)

mentioned in commit 70de4f45

mentioned in commit 8452151e

mentioned in commit 6973fd64

mentioned in commit d3ea0c33

mentioned in issue gitlab-org/quality/triage-reports#13165 (closed)

mentioned in commit 31f7bd0f

mentioned in commit d5501c10

mentioned in commit 0b2f2aa4

mentioned in commit 249fba6f

@OmarQunsulGitlab Do you think this will be complete by %16.2 ? As this issue blocks #409842 (closed)

@tkuah yes. I am almost finished identifying all the cross joins. My next step is to group the relevant ones, and create issues for each one of them. For example, if there are multiple cross joins in 1 model, they can have 1 issue for them, instead of 1 issue for each cross join.

Kamil suggested, in a call, that I create an epic for all of them. And that's what I will do.

mentioned in commit 0756bd01

mentioned in commit 7b4d9d74

mentioned in commit ab6d72b8

mentioned in commit 137a8064

mentioned in commit b9776f97

mentioned in commit bdd090b8

mentioned in issue gitlab-org/quality/triage-reports#13259 (closed)

mentioned in commit 12465725

mentioned in epic &10973 (closed)

mentioned in commit 62b941fa

mentioned in issue #409842 (closed)

added workflowin review label and removed workflowin dev label

@OmarQunsulGitlab I guess we can close, given !124319 (merged) ?

closed

added workflowcomplete label and removed workflowin review label

mentioned in commit 75bf23b4

mentioned in issue #420109 (closed)

added devopstenant scale groupcells infrastructure sectioninfrastructure platforms labels and removed devopsdata stores grouptenant scale [DEPRECATED] sectioncore platform labels