Skip to content

Conversation

@cyberflying
Copy link
Contributor

Purpose

  • add ODBC Driver 17 for sql when process custom data, same code with 03 sample data script,
  • to avoid error:
Traceback (most recent call last):
  File "/Conversation-Knowledge-Mining-Solution-Accelerator/infra/scripts/index_scripts/04_cu_process_custom_data.py", line 179, in <module>
    conn = pyodbc.connect(connection_string, attrs_before={SQL_COPT_SS_ACCESS_TOKEN: token_struct})
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pyodbc.Error: ('01000', "[01000] [unixODBC][Driver Manager]Can't open lib 'ODBC Driver 18 for SQL Server' : file not found (0) (SQLDriverConnect)")
Error: 04_cu_process_custom_data.py failed.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

@Avijit-Microsoft Avijit-Microsoft merged commit 6f493b5 into microsoft:main Jan 12, 2026
6 checks passed
@github-actions
Copy link
Contributor

🎉 This PR is included in version 3.17.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@Avijit-Microsoft
Copy link
Contributor

Hi @cyberflying,
Thanks for the PR and your efforts on this. The changes look good, and we’re happy to merge it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants