[
https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089353#comment-16089353
]
ASF subversion and git services commented on LOG4J2-1864:
---------------------------------------------------------
Commit af2dd30e16cece20b4ae475da851c8538bfa8879 in logging-log4j2's branch
refs/heads/Lucene5 from [~jvz]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=af2dd30 ]
[LOG4J2-1864] Update manual regarding capped collection support
> 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
>
>
> 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)
