logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider
Date Mon, 03 Apr 2017 08:49:42 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953145#comment-15953145

ASF GitHub Bot commented on LOG4J2-1864:

Github user codescale commented on a diff in the pull request:

    --- Diff: log4j-nosql/src/main/java/org/apache/logging/log4j/nosql/appender/mongodb/MongoDbProvider.java
    @@ -97,6 +103,8 @@ public String toString() {
         public static MongoDbProvider createNoSqlProvider(
                 @PluginAttribute("collectionName") final String collectionName,
    +            @PluginAttribute(value = "capped", defaultBoolean = false) final Boolean
    --- End diff --
    Hi @jvz, I changed the `Boolean` member to be a primitive type. But I don't know what
kind of Builder you mean for the attributes? Does this builder exist for the MongoDbProvider?
Cheers Matt

> Support capped collection for MongoDB Log-Provider
> --------------------------------------------------
>                 Key: LOG4J2-1864
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1864
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Appenders
>            Reporter: Matt
> MongoDB supports sth. called capped collections. If the nosql-mongodb-appender supports
this feature, the mongodb-collection could never "overflow" and stick to a defined maximum
> see [pull request 62|https://github.com/apache/logging-log4j2/pull/62] for more details.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message