dotCMS / dotCMS/core

Refactor Relationship Logic to Eliminate Relationship Table Dependency

Open
#32,151 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #32214 by @fmontes — closed without merging
Team : Scout
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Task

We need to refactor our codebase to eliminate the relationship table and rely solely on the field table for loading relationships. The current architecture using the relationship table creates potential failure points during content type updates. This will be implemented as a gradual change to avoid disrupting existing functionality until we can fully remove the table.

Proposed Objective

Please Select

Proposed Priority

Please Select

Acceptance Criteria
  1. Identify all code paths that currently read from the relationship table
  2. Create new methods that obtain the same relationship data from the field table
  3. Implement feature flags to toggle between old and new implementations if needed
  4. Add comprehensive tests comparing data retrieved via both methods
  5. Create a migration plan for gradually deprecating the relationship table
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating every code path that reads from the relationship table and trace how the field table represents the same relationship data. Compare both retrieval approaches with comprehensive tests, then document the feature-flag rollout and migration plan needed to deprecate the relationship table.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, databases
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.