Skip to content

Identifying all cross joins between namespaces and users

Omar Qunsul requested to merge 415196-identify-all-cross-joins-between-namespaces-and-users into master

What does this MR do and why?

Identifying all cross joins between namespaces and users

Addressing Issue #415196 (closed)

Changelog: other

More Context

As part of the Cells we start identifying all the tables that should be moved to the clusterwide database, and tables that will be local to each pod cell. users and namespaces are known to be classified to clusterwide and cell already. All the tables that will be moved to different databases cannot have any cross joins between them. As part of this MR we are identifying all the ActiveRecord associations and code blocks that are doing JOINS between those tables. Issues have been created already to resolve them.

The allow_listing might not be happening exactly on the exact place where the join of the tables is happening. As it's hard to identify this for all the violations. That's the work left to be done in each individual issue in this Epic: &10973 (closed)

In each of these issue, the developer needs to:

  1. Remove the allowing of the cross joins
  2. See which test is failing and how
  3. Resolve the cross joins

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #415196 (closed)

Edited by Omar Qunsul

Merge request reports