[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

JIRA jira@apache.org

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

ASF GitHub Bot commented on LOG4J2-1864:

Github user jvz 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 isCapped,
    --- End diff --
    What we've been doing with old factory methods is removing the annotations from them and marking them deprecated. That way it doesn't break custom configurations, but only the new builder is used for normal configuration (although builders are used before factory methods regardless).

> 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 size.
> 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: [hidden email]
For additional commands, e-mail: [hidden email]