[
https://issues.apache.org/jira/browse/SENTRY-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765382#comment-16765382
]
Hadoop QA commented on SENTRY-2494:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12958288/SENTRY-2494.001.patch
against master.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/4374/console
This message is automatically generated.
> Fix TestRollingFileWithoutDeleteAppender test case testFileNamePattern
> ----------------------------------------------------------------------
>
> Key: SENTRY-2494
> URL: https://issues.apache.org/jira/browse/SENTRY-2494
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.0.1
> Reporter: Arjun Mishra
> Assignee: Arjun Mishra
> Priority: Major
> Attachments: SENTRY-2494.001.patch, SENTRY-2494.01.patch
>
>
> The log size is set to 10 bytes. However if the message size is 15 bytes, it
> creates a 15, 15 and 0 byte file ( which is sometimes flaky)
> Explanation:
> Before we logged a string that was at 15 bytes each. The assumption was
> Logger would split that across 2 files but it never did that. It would put 15
> bytes of line on one file.
> Previously we had 2 log statements:
> debug."123456789012345";
> debug."123456789012345";
> The file being created was "123456789012345", "123456789012345", "" (LAST ONE
> empty)
> as opposed to "1234567890", "1234512345", "6789012345"
> The above output would be flaky because LOGGER.appender did not handle a LONG
> string properly. It would sometimes generate two files with
> "123456789012345", "" (LAST ONE empty)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
