You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2019/02/11 18:33:00 UTC
[jira] [Commented] (SENTRY-2494) Fix
TestRollingFileWithoutDeleteAppender test case testFileNamePattern
[ https://issues.apache.org/jira/browse/SENTRY-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765251#comment-16765251 ]
Hadoop QA commented on SENTRY-2494:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12958280/SENTRY-2494.01.patch against master.
{color:red}Overall:{color} -1 due to 2 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: org.apache.sentry.hdfs.TestSentryHDFSServiceProcessor
Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/4373/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.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)