* New schema import error fixed
* updated test for DatabaseSchema as per recursive import
* unskip and updated database playwright test for bulk import
* Import issue in StoredProcedure fixed
* added query editor for storeprocedure code
* Source url error fixed for import
* updated databaseService test as per recursive bulk import
* fix the storedprocedure parsing issue
* added storedProcedure playwright in the databse service level
* in import dry run set exist schema is false
* fix the playwrigth test around storedProcedure
* on dry run create parent columns
* fix the encoding issue in bulk edit page
* fix the bulk edit playwright test
* Fix Glossary Terms missing on export
---------
Co-authored-by: Ashish Gupta <ashish@getcollate.io>
Co-authored-by: mohitdeuex <mohit.y@deuexsolutions.com>
Co-authored-by: Mohit Yadav <105265192+mohityadav766@users.noreply.github.com>
* Unskip and fix the playwright
* fix: add name to fqnParts for partial search on testSuite/testCase/testResolution
* Update the alert tests to run in parallel
* skip the autoclassification spec
---------
Co-authored-by: sonika-shah <58761340+sonika-shah@users.noreply.github.com>
Co-authored-by: sonikashah <sonikashah94@gmail.com>
* Fix : case-insensitive issue on aggregation and simplify aggregation API response format
* add lowercase normaliser for service.name.keyword
* add lowercase normaliser for database.name.keyword, databaseSchema.name.keyword, columns.name.keyword
* fix lowercase normaliser for database.name, databaseSchema.name
* create new aggregateRequest.json and update aggregate function
* remove sort field in subAgg and trackScores(false)
* cleanup function
* rename aggregation Field
* fix the search cases
* fix locales
* fix search
* add test case
* hide lineage search for higher level layers
* fix tests
---------
Co-authored-by: Karan Hotchandani <33024356+karanh37@users.noreply.github.com>
Co-authored-by: karanh37 <karanh37@gmail.com>
Co-authored-by: Pere Miquel Brull <peremiquelbrull@gmail.com>
This PR fixes a bug in the Kinesis messaging source where the `Topic` class was incorrectly imported from `metadata.generated.schema.type.schema` instead of the correct entity
definition path `metadata.generated.schema.entity.data.topic`.
**Problem:**
The `yield_topic_sample_data` method used the `type.schema.Topic` definition when calling `fqn.build` and `metadata.get_by_name`. These functions expect the main entity
class.
**Fix:**
Changed the import statement to use `metadata.generated.schema.entity.data.topic.Topic`.
This ensures the correct type definition is used when interacting with the FQN utility and metadata API, preventing potential downstream issues.
