You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Ivan Habunek (JIRA)" <ji...@apache.org> on 2013/03/18 19:46:16 UTC

[jira] [Closed] (LOG4PHP-207) Support for MongoClient and replica sets

     [ https://issues.apache.org/jira/browse/LOG4PHP-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Habunek closed LOG4PHP-207.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0
         Assignee: Ivan Habunek

Applied patch. Tests pass.

Thanks for the work, everyone.
                
> Support for MongoClient and replica sets
> ----------------------------------------
>
>                 Key: LOG4PHP-207
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-207
>             Project: Log4php
>          Issue Type: Improvement
>          Components: Code
>    Affects Versions: 2.3.0
>            Reporter: Richard Safran
>            Assignee: Ivan Habunek
>            Priority: Minor
>              Labels: patch,
>             Fix For: 2.3.0
>
>         Attachments: 0001-Fix-BC-issue-with-host-parameter.patch, 0001-LOG4PHP-207-Fix-BC-issue-with-host-parameter.patch, 0001-LOG4PHP-207-Using-class-MongoClient-instead-of-Mongo.patch, 0001-Mongo-appender-documentation-update.patch, patch.txt, patch.txt
>
>
> Having a MongoDB appender for log4php has been great! Thanks.
> I had some difficulty deploying it to my production environment due to the driver version and replica set config, so here are the changes I made.  I did my best to make these changes transparent so that they would not break existing installs.
> The Mongo PHP client is deprecated and replaced by the MongoClient class.  This is an improved driver and has support for new options including write concerns.
> This patch will use MongoClient if it is available and will fall back to Mongo if it is not.
> Support for multiple hosts has been added to the connect string.  If the connect string is not a valid MongoDB url, then one will be created from the host and port properties.
> New properties:
> writeConcern - What the driver should wait for when writing to the database (if supported).
> writeConcernTimeout - How long the driver should wait to satisfy the writeConcern (if supported).
> replicaSet - The name of the replica set to connect to (if any).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira