[CSHARP-2594] SdamLogFilename value is lost sometimes Created: 17/Apr/19 Updated: 27/Oct/23 Resolved: 17/Apr/19 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Configuration |
| Affects Version/s: | 2.8.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Robert Stam | Assignee: | Robert Stam |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
One way to reproduce:
Check for others. |
| Comments |
| Comment by Robert Stam [ 17/Apr/19 ] |
|
I have confirmed with coworkers that this is by design. Two decisions are interacting for the above code to silently assign null to the sdamLogFilename variable:
|
| Comment by Robert Stam [ 17/Apr/19 ] |
|
This might be by design. We don't currently support sdamLogFilename=xyz.log in the connection string. So clientSettings.SdamLogFilename returned null simply because nothing has set its value yet. |