You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@logging.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/14 11:46:00 UTC

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

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

ASF GitHub Bot commented on LOG4J2-1864:
----------------------------------------

Github user codescale commented on the issue:

    https://github.com/apache/logging-log4j2/pull/62
  
    Thanks @jvz for extending the documentation :+1: 
    https://github.com/apache/logging-log4j2/commit/af2dd30e16cece20b4ae475da851c8538bfa8879


> 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
>            Assignee: Matt Sicker
>             Fix For: 2.9.0
>
>
> 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
(v6.4.14#64029)