[SERVER-8264] Startup with textSearchEnabled=True fails Created: 22/Jan/13  Updated: 16/Oct/15  Resolved: 01/Feb/13

Status: Closed
Project: Core Server
Component/s: Usability
Affects Version/s: 2.3.2
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Alvin Richards (Inactive) Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

Failure case
mongod --setParameter textSearchEnabled=True
Bad value for parameter "textSearchEnabled": can't convert string to bool

Successful case
mongod --setParameter textSearchEnabled=true
about to fork child process, waiting until server is ready for connections.

Participants:

 Description   

Problem:
Startup mongod with

--setParameter textSearchEnabled=True

Fails with

Bad value for parameter "textSearchEnabled": can't convert string to bool

Workaround:
Use

--setParameter textSearchEnabled=true

Solution:
Parameter parsing should be case insensitive



 Comments   
Comment by Andy Schwerin [ 01/Feb/13 ]

Docs should be updated to reflect that boolean arguments to --setParameter on the command line can use 0 or "false" and 1 or "true", only.

That is, for a boolean parameter, --setParameter a=true is OK, but --setParameter a=True is not.

Comment by Alvin Richards (Inactive) [ 01/Feb/13 ]

At least documentation, i've always through for booleans and flay they should be case insensitive, but that's your call. Its a "nit".

Comment by Andy Schwerin [ 01/Feb/13 ]

alvin We went with "true" because it's the literal for truth in JavaScript. If you allow True, do you also allow TRUE? What about TrUe? I'm inclined to close this as "works as designed", and maybe mark it "documentation needed." What do you think?

Generated at Thu Feb 08 03:16:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.