Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/82
committing each time is very affecting performance.
The practice now is to commit once per minute, commit too often, will lead
to performance degradation, the submission interval is too long
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/82
https://www.zybuluo.com/liyuj/note/825932
I wrote a document. Can the community help me check?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/82
I can provide, but what does it contain? In what format?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/82
This PR does not have a corresponding issue.
The code is used within our company and we think he has reusability, so it
contributes to the community.
The functionality has been tested
GitHub user liyuj opened a pull request:
https://github.com/apache/logging-log4j2/pull/82
Add a new LuceneAppender which writes logging events to a lucene index
library.
Add a new LuceneAppender which writes logging events to a lucene index
library.The log4j2.xml configuration is
Github user liyuj closed the pull request at:
https://github.com/apache/logging-log4j2/pull/74
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/74
We found a bug that is being corrected and then resubmitted in the form of
a new module.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/74
Lucene5 API and lucene6 are incompatible.
I think the future is divided into multiple modules is more reasonable,
such as log4j-lucene5 and log4j-lucene6.
---
If your project is set up for
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/74
Lucene 6 and later versions require Java 8 or later.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user liyuj opened a pull request:
https://github.com/apache/logging-log4j2/pull/74
Add a new LuceneAppender which writes logging events to a lucene index
library.
Add a new LuceneAppender which writes logging events to a lucene index
library.The log4j2.xml configuration is
Github user liyuj closed the pull request at:
https://github.com/apache/logging-log4j2/pull/73
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/73
If so, I think it is more reasonable to put it in the log4j-nosql module.
We rearrange the code and submit it again.
---
If your project is set up for it, you can reply to this email and
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/73
If so, I think it is more reasonable to put it in the log4j-nosql module.
We rearrange the code and submit it again.
---
If your project is set up for it, you can reply to this email and
13 matches
Mail list logo
