You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/02 18:58:41 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=15952811#comment-15952811 ]
ASF GitHub Bot commented on LOG4J2-1864:
----------------------------------------
Github user codescale commented on the issue:
https://github.com/apache/logging-log4j2/pull/62
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 size.
> see [pull request 62|https://github.com/apache/logging-log4j2/pull/62] for more details.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org