-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#9269 - Add MSSQL Stored Procedure Support #14739
Conversation
Quality Gate failed for 'open-metadata-ingestion'Failed conditions 13.2% Duplication on New Code (required ≤ 10%) |
|
||
-- Add supportsQueryComment to MSSQL | ||
update dbservice_entity | ||
set json = JSON_SET(json, '$.connection.config.supportsQueryComment', true) | ||
where serviceType = 'Mssql'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pmbrull as supportsQueryComment by default is set to true, if it doesn't find it, it will be set to true, do we need a migration in these cases?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without it the server did not start. I don't think the problem is the value but the server expecting the key
there I guess
* Remove unnecessary field * Remove unnecessary field * Support query comments in MSSQL * Remove unnecessary field * Format * Add external type * Add MSSQL SP support
…a#14739) * Remove unnecessary field * Remove unnecessary field * Support query comments in MSSQL * Remove unnecessary field * Format * Add external type * Add MSSQL SP support
Describe your changes:
Fixes #9269
Also:
supportsQueryComment
to MSSQL. Tested it with our instance and it's all good thereleft a comment in the issue with the SP lineage query we are using. It's not great since I did not find a way to link SP <> Query via session ID or anything similar, so we might end up having some false positives.
Let's see if someone in the community is more versed in MSSQL than I am and can chip in
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>