ATLAS-5197: Deprecate and Remove Legacy “New UI” (Backbone.js) from Apache Atlas#509
Merged
pawarprasad123 merged 1 commit intomasterfrom Jan 29, 2026
Merged
ATLAS-5197: Deprecate and Remove Legacy “New UI” (Backbone.js) from Apache Atlas#509pawarprasad123 merged 1 commit intomasterfrom
pawarprasad123 merged 1 commit intomasterfrom
Conversation
pawarprasad123
requested review from
chaitalicod,
mandarambawane and
pinal-shah
chaitalicod
approved these changes
Jan 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Background
Currently, Apache Atlas maintains three different UI implementations:
Classic UI – Backbone.js
New UI – Backbone.js
React UI
Maintaining three UI layers increases maintenance overhead, code duplication, and confusion for users and contributors.
Objective
Streamline the UI architecture by removing the legacy “New UI” built on Backbone.js, and retaining only:
Classic UI (Backbone.js)
React UI
The goal is to reduce complexity, improve maintainability, and align with the long-term UI direction of the project.
Scope of Work
Identify and remove:
New UI routes
Related Backbone.js views, templates, and assets
Feature toggles or flags referencing the New UI
Ensure:
Classic UI remains fully functional
React UI remains unaffected
Update:
Documentation (if applicable)
Navigation or routing logic pointing to the removed UI
Validate:
No broken links or references to the removed UI
Application builds and runs successfully after cleanup
Acceptance Criteria
“New UI” (Backbone.js) is completely removed from the codebase
Only Classic UI and React UI are available
No references to New UI remain in routing or navigation
Application works without UI-related regressions
Documentation updated if required
Notes
This change is intended as a cleanup and consolidation effort
No functional changes are expected in Classic or React UI
How was this patch tested?
Manually tested , build passed
