[SERVER-35309] Connection string option is appname; currentOp, logs, etc. use appName Created: 31/May/18  Updated: 29/Oct/23  Resolved: 06/Jun/18

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: 4.0.0-rc1
Fix Version/s: 4.0.0-rc5, 4.1.1

Type: Bug Priority: Major - P3
Reporter: Allison Reinheimer Moore Assignee: Mark Benvenuto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to DOCS-11246 Documenting support for mongo shell t... Closed
is related to SERVER-32094 Add support for mongo shell to send c... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Platforms 2018-06-18
Participants:

 Description   

It might be more practical if these used the same string (presumably the camelcase) rather than having appname set the appName.



 Comments   
Comment by Githook User [ 07/Jun/18 ]

Author:

{'username': 'markbenvenuto', 'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com'}

Message: SERVER-35309 CamelCase appName in connection strings

(cherry picked from commit 558a8edc943709177d4a41c172515ebc3f7300ed)
Branch: v4.0
https://github.com/mongodb/mongo/commit/fb28bf379eef44681ca014b612d9088d26058675

Comment by Githook User [ 06/Jun/18 ]

Author:

{'username': 'markbenvenuto', 'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com'}

Message: SERVER-35309 CamelCase appName in connection strings
Branch: master
https://github.com/mongodb/mongo/commit/558a8edc943709177d4a41c172515ebc3f7300ed

Comment by Andrew Morrow (Inactive) [ 06/Jun/18 ]

mark.benvenuto - I believe this needs to make 4.0.0 if your argument is valid. Could you please update the fixVersion appropriately?

Comment by Mark Benvenuto [ 05/Jun/18 ]

Since 4.0 is the first release to support appName in connection strings, it is easiest to rename "appname" to "appName" without any impact.

Comment by Max Hirschhorn [ 31/May/18 ]

The driver specification for the connection string format requires that the case of keys be ignored. It was realized in the code review for SERVER-32065 to add the "retryWrites" connection string option that the MongoURI doesn't ignore the case of the keys. I don't think a ticket was ever filed to change the behavior.

Note that this also applies to existing options such as "replicaSet". I'm not sure whether the keys for TXT records should be case sensitive or not.

Keys are strings and the character case must be normalized by lower casing the uppercase ASCII characters A through Z; other characters are left as-is.

When defining and documenting keys, specifications should follow the camelCase naming convention with the first letter in lowercase, snake_case MUST not be used. Keys that aren't supported by a driver MUST be ignored.

https://github.com/mongodb/specifications/blob/0ca683b560f02b74cec5118ef91efb3742abb89a/source/connection-string/connection-string-spec.rst#keys

Generated at Thu Feb 08 04:39:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.