* Data Asset Rules configuration in settings
* Enable, delete and API loading states
* Convert card listing to table listing
* Icon update for preference page menu item
* Table loading fix on delete and edit
---------
Co-authored-by: Satish <satish@Satishs-MacBook-Pro.local>
Co-authored-by: Karan Hotchandani <33024356+karanh37@users.noreply.github.com>
* Revamp: left panle of data quality tab under entity detail page
* Enhance Data Quality UI: Add support for table type in TestCaseForm, improve filtering options in TestCases component, and update error handling in TestSuites component. Introduce new documentation links and update translations for entity pipeline information across multiple languages.
* Refactor Data Quality UI: Integrate getPopupContainer utility across various components for improved dropdown handling, enhance styling for select elements, and update form layouts. Additionally, refine the SummaryPanel and TestSuiteDetailsPage for better user experience.
* fixed unit test for the PR
* fixed playwright
* fix testSuite aut test
* Refactor DataQuality tests and components to integrate CodeEditor and enhance ParameterForm functionality
- Updated ParameterForm to use CodeEditor instead of SchemaEditor for SQL expressions.
- Added a renderWithForm utility for consistent form rendering in tests.
- Enhanced test cases for ParameterForm to ensure proper rendering and functionality.
- Introduced custom query functionality in TestCaseFormV1 with corresponding tests.
- Added translations for "custom-query" in multiple languages.
- Created CodeEditor component with tests for improved code editing experience.
* Update translations for "add-a-entity" and "entity-pipeline-information" in multiple languages to improve clarity and consistency across the UI.
* ISSUE-22596: Fix search alias resolution with clusterAlias configuration
**Problem:**
MCP SearchMetadataTool was failing with "Failed to find index table" error
in production environments when clusterAlias is configured, while working
correctly in development environments without clusterAlias.
**Root Cause:**
- SearchMetadataTool was directly using entity alias names (e.g., "table")
without applying the clusterAlias transformation
- When clusterAlias is configured, both search indices and their aliases
are created with the cluster prefix
- Without this transformation:
- Development: "table" alias exists ✅
- Production: only "openmetadata_table" alias exists, "table" doesn't ❌
**Solution:**
- Apply SearchRepository.getIndexOrAliasName() transformation to respect clusterAlias
- This ensures the correct alias name is used ("table" → "openmetadata_table" in production)
- Add enhanced logging to track alias name resolution
**Testing:**
- Added unit tests covering scenarios with and without clusterAlias
- Verified fix resolves production issue with clusterAlias="openmetadata"
**Impact:**
- Fixes MCP search functionality in production environments using clusterAlias
- No breaking changes to existing functionality
- Maintains backward compatibility with environments without clusterAlias
Closes #ISSUE-22596
* ISSUE-22596: Clean up SearchMetadataToolTest: remove unused imports and redundant comments
---------
Co-authored-by: dmitrii.cherkashin <dmitrii.cherkashin@welltory.com>
Co-authored-by: Sriharsha Chintalapani <harshach@users.noreply.github.com>
Co-authored-by: Mohit Yadav <105265192+mohityadav766@users.noreply.github.com>
* fix the cycle lineage nodes when being collapsed
* added unit test around removal of rootNode in collapse if there is cycle lineage happen
* added playwright test and added commetns where the fix operation is perforemed
* Initial Implementation of ER Diagram Upstream and downstream implementation
* Fix: Extra endpoint of entityRelationship removed
* Fix: Add upstreamEntityRelationship property in table index mappings for ES
* Fix: Removed isConnectedVia since it is not required for ER Diagram
* Improved some code, not final
* Fixed: Working with test cases
* Moved to TableResource from Database resource, need to fix tests
* Improved code and fixed test cases
* Fixing Painless Scipts along with reindexing Null Pointer Exceptions
* Reverted changes for Database Schema entity relationship
* Revert "Reverted changes for Database Schema entity relationship"
This reverts commit 544dd342fec924062d769472e59b29f0aa0eaf30.
* Minor: Reverted changes for Database Schema entity relationship - Fixed Build
* Refactor code: Fix Unnecessary functions, corrected imports
* Refactor code: Improve Test cases , fixed addNode to fqn hash inconsistency, Added Extra test cases for multihop and multi parent use case
* Refactor code: Make tests run in the same thread to not collide with other entity relationship tests
* Refactor code: Create Foreign Keys during the create table itself to avoid orphans
* Refactor code: Improve Test Cases to find the node and upstream details for matching as well
* Refactor code: Corrected Typo
* Update generated TypeScript types
* Database Schema ER Diagram Initial Implementation
* Refactor: Safe Delete function
* Update generated TypeScript types
* Refactored: GraphBuilders to closely Follow Lineage, Fixed Test Cases, refactored constants and generic pagination
* Test cases for Lineage and Improved Test cases for EntityRelationship for Table Level
* Test cases for Platform Lineage and DatabaseSchema ER Diagram
* Initial Improved Implementation of Database Schema ER with pagination
* mvn spotless apply
* Fixed the Test for auto approval
* Update generated TypeScript types
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Ashish Gupta <ashish@getcollate.io>
* update domains widget for filters
* add filter support for data assets widget
* fix full size widget bugs
* remove latest filter type from data assets wwidget
* fix unit test
* update empty data placeholders for widgets
* fix tooltip styles and remove icons from customise home modal
* minor fix
* fix(dq): enable ''Column values to be in set'' test case for boolean columns
Add BOOLEAN to supportedDataTypes array in columnValuesToBeInSet.json
to allow boolean column validation with predefined allowed values.
This enables users to enforce strict true/false validation on boolean
columns directly at the column level, resolving issue #22099.
Co-authored-by: IceS2 <IceS2@users.noreply.github.com>
* Add tests to the new feature
* Add migrations and columnValuesToBeNotInSet
---------
Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Co-authored-by: IceS2 <IceS2@users.noreply.github.com>
* Inherit Domains from Classification for Tags
* Changed domain to domains in TagResource
---------
Co-authored-by: Aniket Katkar <aniketkatkar97@gmail.com>
* fix the lineage operation being canclled on CI
* remove unwanted lineage test code and reduce welcome screen search time
* try skippin the test to check the CI
