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

[Content]: Segment Data Lakes (Azure) #5391

Open
jordanskole opened this issue Sep 21, 2023 · 2 comments
Open

[Content]: Segment Data Lakes (Azure) #5391

jordanskole opened this issue Sep 21, 2023 · 2 comments
Assignees
Labels
content When the bug is about content that needs to get fixed stale triage

Comments

@jordanskole
Copy link

What article on segment.com/docs is affected?

https://segment.com/docs/connections/storage/catalog/data-lakes/#set-up-segment-data-lakes-azure

What part(s) of the article would you like to see updated?

In Part 3 - Set up Azure MySQL Database it asks you to set the lower_case_table_names to 2.

Unfortunately this isn't possible in version 8.0 (the default option) of MySQL in Azure (Microsoft Docs)

So either this works without it on 8, or the docs should ask the user to use ~5.7

P.S. Azure is saying they are going to stop support of 5.7 in Sept 2025 -- plenty of time -- but eventually there will need to be a workaround.

Additional information

No response

@jordanskole jordanskole added content When the bug is about content that needs to get fixed triage labels Sep 21, 2023
@jordanskole
Copy link
Author

jordanskole commented Sep 21, 2023

Ugh, sorry going through this a bit more. Azure is also depriciating Single Servers and only allowing creation of "Flexible Servers" going forward. Flexible Servers don't let you modify the lower_case_table_names parameter even on 5.7.

However, azure does have some documentation on how to "set the parameter at the connection level using init_connect" Setting non-modifiable server parameters

Edit: and it does appear that this is possible in both 8.0 and 5.7

@pwseg pwseg self-assigned this Sep 22, 2023
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the stale label Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content When the bug is about content that needs to get fixed stale triage
Projects
None yet
Development

No branches or pull requests

2 participants