Skip to content
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

🎉 Destination MSSQL: support normalization on destination-mssql destination connector #6876

Closed
bazarnov opened this issue Oct 7, 2021 · 0 comments · Fixed by #6877
Closed

Comments

@bazarnov
Copy link
Collaborator

bazarnov commented Oct 7, 2021

Tell us about the problem you're trying to solve

We need to include the support of Normalization feature for destination-mssql connector.
There is partial PR prepared and attached to this issue, all we need is to fix some acceptance-tests to pass correctly.

Describe the solution you’d like

Acceptance Tests for destination-mssql are passed successfully.

Additional Information

Due to change in this PR, the Normalization for MS SQL Server was added, but the destination-mssql does not pass the IntegrationTest with this change. We need to pass the acceptance test for SSH Tunnel with Normalization.

Link to the PR with Implementation of Normalization: #6079

IMPORTANT

! The half-ready PR is attached to this issue, please use this branch and fix the tests !
#6877

@bazarnov bazarnov added the type/enhancement New feature or request label Oct 7, 2021
@bazarnov bazarnov changed the title Destination MSSQL: support normalization on destination-mssql destination connector 🎉 Destination MSSQL: support normalization on destination-mssql destination connector Oct 7, 2021
@bazarnov bazarnov linked a pull request Oct 7, 2021 that will close this issue
38 tasks
@etsybaev etsybaev self-assigned this Oct 11, 2021
@sherifnada sherifnada moved this to Done in GL Roadmap Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants