| Bug #119745 | documentation: mysql 9.6 release notes - classic_hashing | ||
|---|---|---|---|
| Submitted: | 22 Jan 10:24 | Modified: | 30 Jan 15:02 |
| Reporter: | Bernd Wahlen | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 9.6.0 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[22 Jan 10:24]
Bernd Wahlen
[22 Jan 10:34]
Bernd Wahlen
expected behavior: - install component by default, show startup warning and change default in next version - or clearly warn in release notes unclear if this component is deprecated
[27 Jan 7:03]
Harin Vadodaria
Thank you for the report.
[30 Jan 15:02]
Carlos Ortiz
1. default deactivation of classic_hashing is a breaking change and should be mentioned under Functionality Added or Changed (not just under Security notes). Release note has the important change tag added. No further updates required. 2. https://dev.mysql.com/doc/refman/9.6/en/legacy-hashing-component.html URN: file://classic_hashing is wrong (at least in ubuntu build), URN is component_classic_hashing INSTALL COMPONENT 'file://component_classic_hashing'; Updated name of component: https://dev.mysql.com/doc/refman/9.6/en/legacy-hashing-component.html additional suggestion: https://dev.mysql.com/doc/refman/9.6/en/component-loading.html should mention that component loading is server local (not replicated). Added sentence: Components are loaded in the server locally (not replicated).
