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 Sun, 02 Apr 2017 18:58:41 GMT

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

ASF GitHub Bot commented on LOG4J2-1864:

Github user codescale commented on the issue:

    Hi @jvz, Thanks that you're interested in this feature.
    I added a `feature request` to [jira](https://issues.apache.org/jira/browse/LOG4J2-1864).
And I will take a look at your remarks as soon as possible. Cheers

> 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