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 MySQL: enable support dedup sync option #7544

Open
vijaybridgeme opened this issue Nov 1, 2021 · 2 comments
Open

Destination MySQL: enable support dedup sync option #7544

vijaybridgeme opened this issue Nov 1, 2021 · 2 comments
Labels
area/connectors Connector related issues area/databases community connectors/destination/mysql connectors/destinations-database frozen Not being actively worked on team/destinations Destinations team's backlog type/bug Something isn't working

Comments

@vijaybridgeme
Copy link

Enviroment

  • Airbyte version: 0.30.23-alpha
  • OS Version / Instance: macOS
  • Deployment: Docker
  • Source Connector and version: Doesn't matter
  • Destination Connector and version: MySQL
  • Severity: Medium
  • Step where error happened: Setup new connection

Current Behavior

MySQL documentation says that it supports dedup. But in the connection page, dedup option does not show up.

"supportsDBT": true,
"supported_destination_sync_modes": ["overwrite", "append"],
"connectionSpecification": {
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "MySQL Destination Spec",

Screen Shot 2021-10-28 at 10 57 36 AM

Expected Behavior

Add "dedup" option in supported sync modes.

Logs

If applicable, please upload the logs from the failing operation.
For sync jobs, you can download the full logs from the UI by going to the sync attempt page and
clicking the download logs button at the top right of the logs display window.

LOG

replace this with
your long log
output here

Steps to Reproduce

Are you willing to submit a PR?

Remove this with your answer.

@vijaybridgeme vijaybridgeme added the type/bug Something isn't working label Nov 1, 2021
@ChristopheDuong
Copy link
Contributor

There should be an SAT to make sure all destinations that currently support normalization have to support dedup sync options (and being tested for it)

@tq-tien
Copy link

tq-tien commented Nov 10, 2021

I had the same issue. However, I configured "incremental || dedupe history" via API and it worked normally, although the UI showed nothing at sync mode buttons. That can be a workaround.
image

@augan-rymkhan augan-rymkhan self-assigned this Nov 12, 2021
@sherifnada sherifnada removed this from the Connectors Nov 26 2021 milestone Nov 15, 2021
@bleonard bleonard added autoteam team/tse Technical Support Engineers labels Apr 26, 2022
@marcosmarxm marcosmarxm added area/databases team/databases and removed autoteam team/tse Technical Support Engineers labels Jun 14, 2022
@grishick grishick added the team/destinations Destinations team's backlog label Sep 27, 2022
@marcosmarxm marcosmarxm changed the title MySQL destination connector needs to support dedup sync option Destination MySQL: enable support dedup sync option Nov 30, 2022
@bleonard bleonard added the frozen Not being actively worked on label Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues area/databases community connectors/destination/mysql connectors/destinations-database frozen Not being actively worked on team/destinations Destinations team's backlog type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests