[
https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088614#comment-16088614
]
ASF GitHub Bot commented on LOG4J2-1864:
----------------------------------------
Github user mikaelstaldal commented on the issue:
https://github.com/apache/logging-log4j2/pull/62
@jvz I have no experience with our MongoDB appender, and only limited
experience with MongoDB in general. Maybe better that you, or someone else with
more experience, merge this.
> 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
(v6.4.14#64029)
