Bug #95363 There are duplicate statements in the online manual
Submitted: 14 May 2019 3:00 Modified: 16 May 2019 23:24
Reporter: yitao Xu Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Documentation Severity:S3 (Non-critical)
Version:7.5 OS:Any
Assigned to: CPU Architecture:Any

[14 May 2019 3:00] yitao Xu 
Description:
There are duplicate statements in the online manual.

PortNumber: Port used for this transporter (DEPRECATED). Removed in NDB 7.5.1.

PortNumber: Port used for this transporter (DEPRECATED). Removed in NDB 7.5.1.

PortNumber: Port used for this transporter (DEPRECATED). Removed in NDB 7.5.1.

How to repeat:
Access https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-added-deprecated-removed-7-5.html

search flow statements please.

PortNumber: Port used for this transporter (DEPRECATED). Removed in NDB 7.5.1.

PortNumber: Port used for this transporter (DEPRECATED). Removed in NDB 7.5.1.

PortNumber: Port used for this transporter (DEPRECATED). Removed in NDB 7.5.1.
[14 May 2019 4:34] MySQL Verification Team 
Hello Yitao Xu,

Thank you for the report.

regards,
Umesh
[16 May 2019 23:18] Jon Stephens 
Hi Yiato and Umesh,

This is a bug in the documentation, but the analysis is incorrect. 

The real issue: There were once four different configuration parameters, all named "PortNumber"; there was one such parameter each for the [ndb_mgmd], [tcp], [sci], and [shm] sections of the config.ini file. Three of these--all but the [ndb_mgmd] version of the parameter--were deprecated prior to NDB 7.2, and were removed in NDB 7.5.1. However, the descriptions used for these three parameters were identical. I am updating the descriptions by identifying the transporter type in each description.

As part of this changeset, I am also fixing some missing periods/run-together sentences in the Added parameters lists.

Also, there's nothing here that need be regarded as confidential/proprietary, so removing Private flag.
[16 May 2019 23:24] Jon Stephens 
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.