garydgregory commented on PR #3322: URL: https://github.com/apache/logging-log4j2/pull/3322#issuecomment-2561910849
So the real problem is that the Mongo documentation could be better, like in any software. I am concerned this opens the door for more and more options to be added to "override" the connection string components, making maintenance harder. We should only, IMO, offer configuration hooks for behavior that can't be achieved otherwise. Let's review: The database as part of the connection string is documented here (where Google took me): https://www.mongodb.com/docs/manual/reference/connection-string-examples/#std-label-connections-connection-examples For example. 2 examples I picked from the page: [Self-Hosted records Database Running Locally](https://www.mongodb.com/docs/manual/reference/connection-string-examples/#self-hosted-records-database-running-locally): ``` mongodb://myDatabaseUser:D1fficultP%40ssw0rd@localhost/records ``` and fancier: [MongoDB Atlas Cluster that Authenticates with AWS IAM credentials](https://www.mongodb.com/docs/manual/reference/connection-string-examples/#mongodb-atlas-cluster-that-authenticates-with-aws-iam-credentials): ``` mongodb+srv://<aws access key id>:<aws secret access key>@cluster0.example.com/testdb?authSource=$external&authMechanism=MONGODB-AWS ``` The collection is specified as "databaseName.collectionName", see our XML configuration files. The classic problem is that we do not want to create support tickets like "My appender connects to A instead of B, why?" where we then have to say "Oh, that's because you specified the foo in both the connection string and in the other thing and this takes precedence over that, blah blah". For these use cases of double configuration, we should throw an exception. Who would port this to `log4j-mongodb4`? to `master`? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
