[jira] [Commented] (SENTRY-2388) Preparing for 2.2.0-SNAPSHOT release
[
https://issues.apache.org/jira/browse/SENTRY-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615465#comment-16615465
]
Hadoop QA commented on SENTRY-2388:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12939769/SENTRY-2388.001.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.tests.e2e.hdfs.TestHDFSIntegrationWithHA
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/4122/console
This message is automatically generated.
> Preparing for 2.2.0-SNAPSHOT release
>
>
> Key: SENTRY-2388
> URL: https://issues.apache.org/jira/browse/SENTRY-2388
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
>Affects Versions: 2.1.0
>Reporter: Na Li
>Assignee: Na Li
>Priority: Major
> Attachments: SENTRY-2388.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SENTRY-2402) REVOKE GRANT OPTION also revokes privileges with no grant option
[
https://issues.apache.org/jira/browse/SENTRY-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615442#comment-16615442
]
Hadoop QA commented on SENTRY-2402:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12939767/SENTRY-2402.1.patch
against master.
{color:red}Overall:{color} -1 due to 3 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.tests.e2e.dbprovider.TestPrivilegeWithGrantOption
{color:red}ERROR:{color} Failed:
org.apache.sentry.tests.e2e.dbprovider.TestPrivilegeWithGrantOption
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/4121/console
This message is automatically generated.
> REVOKE GRANT OPTION also revokes privileges with no grant option
>
>
> Key: SENTRY-2402
> URL: https://issues.apache.org/jira/browse/SENTRY-2402
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
>Affects Versions: 2.1.0
>Reporter: Sergio Peña
>Assignee: Sergio Peña
>Priority: Major
> Attachments: SENTRY-2402.1.patch
>
>
> The REVOKE GRANT OPTION command is also revoking the privilege that does not
> have a grant option. The correct behavior is that the only the grant option
> is set to false on the specified privilege.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (SENTRY-387) Thrift APIs seem to return "0" status code for some failed operations
[ https://issues.apache.org/jira/browse/SENTRY-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Morio Ramdenbourg reassigned SENTRY-387: Assignee: (was: Morio Ramdenbourg) > Thrift APIs seem to return "0" status code for some failed operations > - > > Key: SENTRY-387 > URL: https://issues.apache.org/jira/browse/SENTRY-387 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Sravya Tirukkovalur >Priority: Major > > For example, if serverName or action is null/empty, operation fails but we > still return 0 status code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SENTRY-386) Provide a default log4j file for Sentry service which logs to the console
[ https://issues.apache.org/jira/browse/SENTRY-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Morio Ramdenbourg reassigned SENTRY-386: Assignee: (was: Morio Ramdenbourg) > Provide a default log4j file for Sentry service which logs to the console > - > > Key: SENTRY-386 > URL: https://issues.apache.org/jira/browse/SENTRY-386 > Project: Sentry > Issue Type: Task >Affects Versions: 1.5.0 >Reporter: Sravya Tirukkovalur >Priority: Minor > Labels: newbie > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SENTRY-330) Update Derby schema script to enforce non-null constraint
[ https://issues.apache.org/jira/browse/SENTRY-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Morio Ramdenbourg reassigned SENTRY-330: Assignee: (was: Morio Ramdenbourg) > Update Derby schema script to enforce non-null constraint > - > > Key: SENTRY-330 > URL: https://issues.apache.org/jira/browse/SENTRY-330 > Project: Sentry > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Prasad Mujumdar >Priority: Major > Labels: newbie > Attachments: SENTRY-330.patch > > > Currently Derby schema script is not consistent with setting bunch of columns > as non-null. We need to keep this in sync with other schema scripts. Since > derby is used for unit test, this can cause issues to got through unit tests > and fail in the real deployments. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SENTRY-59) Doc that ResourceAuthorizationProvider checks actions as ORs, add support for AND
[
https://issues.apache.org/jira/browse/SENTRY-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Morio Ramdenbourg reassigned SENTRY-59:
---
Assignee: (was: Morio Ramdenbourg)
> Doc that ResourceAuthorizationProvider checks actions as ORs, add support for
> AND
> -
>
> Key: SENTRY-59
> URL: https://issues.apache.org/jira/browse/SENTRY-59
> Project: Sentry
> Issue Type: Improvement
>Affects Versions: 1.3.0
>Reporter: Gregory Chanan
>Priority: Major
>
> Currently, it is not clear from the javadoc how multiple actions are handled
> in the function:
> {code}
> /***
>* Returns validate subject privileges on given Authorizable object
>*
>* @param subject: UserID to validate privileges
>* @param authorizableHierarchy : List of object accroding to namespace
> hierarchy.
>*eg. Server->Db->Table or Server->Function
>*The privileges will be validated from the higher to lower scope
>* @param actions : Privileges to validate
>* @return
>*True if the subject is authorized to perform requested action on
> the given object
>*/
> public boolean hasAccess(Subject subject, List
> authorizableHierarchy, Set actions);
> {code}
> but at least in ResourceAuthorizationProvider, OR semantics are used. We
> should document this and perhaps add an interface for AND semantics.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SENTRY-2388) Preparing for 2.2.0-SNAPSHOT release
[ https://issues.apache.org/jira/browse/SENTRY-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-2388: -- Resolution: Fixed Status: Resolved (was: Patch Available) commit https://github.com/apache/sentry/commit/e38d8b017d046174c8c056c58fcf03762a669773 > Preparing for 2.2.0-SNAPSHOT release > > > Key: SENTRY-2388 > URL: https://issues.apache.org/jira/browse/SENTRY-2388 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Na Li >Assignee: Na Li >Priority: Major > Attachments: SENTRY-2388.001.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SENTRY-2388) Preparing for 2.2.0-SNAPSHOT release
[ https://issues.apache.org/jira/browse/SENTRY-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-2388: -- Summary: Preparing for 2.2.0-SNAPSHOT release (was: Update the pom file in master branch) > Preparing for 2.2.0-SNAPSHOT release > > > Key: SENTRY-2388 > URL: https://issues.apache.org/jira/browse/SENTRY-2388 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Na Li >Assignee: Na Li >Priority: Major > Attachments: SENTRY-2388.001.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SENTRY-2388) Update the pom file in master branch
[ https://issues.apache.org/jira/browse/SENTRY-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-2388: -- Status: Patch Available (was: Open) > Update the pom file in master branch > > > Key: SENTRY-2388 > URL: https://issues.apache.org/jira/browse/SENTRY-2388 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Na Li >Assignee: Na Li >Priority: Major > Attachments: SENTRY-2388.001.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SENTRY-2388) Update the pom file in master branch
[ https://issues.apache.org/jira/browse/SENTRY-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li updated SENTRY-2388: -- Attachment: SENTRY-2388.001.patch > Update the pom file in master branch > > > Key: SENTRY-2388 > URL: https://issues.apache.org/jira/browse/SENTRY-2388 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Na Li >Assignee: Na Li >Priority: Major > Attachments: SENTRY-2388.001.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SENTRY-2402) REVOKE GRANT OPTION also revokes privileges with no grant option
[ https://issues.apache.org/jira/browse/SENTRY-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergio Peña updated SENTRY-2402: Attachment: SENTRY-2402.1.patch > REVOKE GRANT OPTION also revokes privileges with no grant option > > > Key: SENTRY-2402 > URL: https://issues.apache.org/jira/browse/SENTRY-2402 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Sergio Peña >Priority: Major > Attachments: SENTRY-2402.1.patch > > > The REVOKE GRANT OPTION command is also revoking the privilege that does not > have a grant option. The correct behavior is that the only the grant option > is set to false on the specified privilege. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SENTRY-2402) REVOKE GRANT OPTION also revokes privileges with no grant option
[ https://issues.apache.org/jira/browse/SENTRY-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergio Peña reassigned SENTRY-2402: --- Assignee: Sergio Peña > REVOKE GRANT OPTION also revokes privileges with no grant option > > > Key: SENTRY-2402 > URL: https://issues.apache.org/jira/browse/SENTRY-2402 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Sergio Peña >Assignee: Sergio Peña >Priority: Major > Attachments: SENTRY-2402.1.patch > > > The REVOKE GRANT OPTION command is also revoking the privilege that does not > have a grant option. The correct behavior is that the only the grant option > is set to false on the specified privilege. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SENTRY-2402) REVOKE GRANT OPTION also revokes privileges with no grant option
[ https://issues.apache.org/jira/browse/SENTRY-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergio Peña updated SENTRY-2402: Status: Patch Available (was: Open) > REVOKE GRANT OPTION also revokes privileges with no grant option > > > Key: SENTRY-2402 > URL: https://issues.apache.org/jira/browse/SENTRY-2402 > Project: Sentry > Issue Type: Bug > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Sergio Peña >Assignee: Sergio Peña >Priority: Major > Attachments: SENTRY-2402.1.patch > > > The REVOKE GRANT OPTION command is also revoking the privilege that does not > have a grant option. The correct behavior is that the only the grant option > is set to false on the specified privilege. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SENTRY-2381) create a branch for 2.1.0
[ https://issues.apache.org/jira/browse/SENTRY-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li resolved SENTRY-2381. --- Resolution: Fixed Fix Version/s: 2.1.0 https://github.com/apache/sentry/tree/branch-2.1.0 > create a branch for 2.1.0 > - > > Key: SENTRY-2381 > URL: https://issues.apache.org/jira/browse/SENTRY-2381 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Na Li >Assignee: Na Li >Priority: Major > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SENTRY-2378) create a jira release version 2.1.0
[ https://issues.apache.org/jira/browse/SENTRY-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li resolved SENTRY-2378. --- Resolution: Fixed Fix Version/s: 2.1.0 jira is created as SENTRY-2377 > create a jira release version 2.1.0 > --- > > Key: SENTRY-2378 > URL: https://issues.apache.org/jira/browse/SENTRY-2378 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Na Li >Assignee: Na Li >Priority: Major > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SENTRY-2379) update the version in pom file to 2.1.0
[ https://issues.apache.org/jira/browse/SENTRY-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Na Li resolved SENTRY-2379. --- Resolution: Fixed commit in branch-2.1.0 https://github.com/apache/sentry/commit/c5af6f0b81481b640b29d6ed9dde2ad1a399e882 > update the version in pom file to 2.1.0 > --- > > Key: SENTRY-2379 > URL: https://issues.apache.org/jira/browse/SENTRY-2379 > Project: Sentry > Issue Type: Sub-task > Components: Sentry >Affects Versions: 2.1.0 >Reporter: Na Li >Assignee: Na Li >Priority: Major > > Updated the pom file to 2.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SENTRY-2404) Fetch configurable number of events from HMS on each fetch
[ https://issues.apache.org/jira/browse/SENTRY-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615080#comment-16615080 ] Na Li commented on SENTRY-2404: --- [~kkalyan] Ajun already did it in https://issues.apache.org/jira/browse/SENTRY-2324 > Fetch configurable number of events from HMS on each fetch > -- > > Key: SENTRY-2404 > URL: https://issues.apache.org/jira/browse/SENTRY-2404 > Project: Sentry > Issue Type: Improvement > Components: Sentry >Affects Versions: 2.1.0 >Reporter: kalyan kumar kalvagadda >Priority: Major > > Currently sentry fetches 2147483647 every time regardless. This effects the > performance of HMS when there are huge number of events in notification_log > table. With the latest improvements in HMS it would be good to limit the > number to smaller one which is configurable. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SENTRY-2088) Use common SLF4J APIs instead of LOG4J directly to allow support of different LOG4J versions
[
https://issues.apache.org/jira/browse/SENTRY-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615056#comment-16615056
]
Benito Kestelman commented on SENTRY-2088:
--
Some of the classes using log4j call Logger.getEffectiveLevel(), which is not
available in slf4j.
How should this be handled?
> Use common SLF4J APIs instead of LOG4J directly to allow support of different
> LOG4J versions
>
>
> Key: SENTRY-2088
> URL: https://issues.apache.org/jira/browse/SENTRY-2088
> Project: Sentry
> Issue Type: Improvement
> Components: Sentry
>Affects Versions: 2.0.0
>Reporter: Sergio Peña
>Priority: Major
> Labels: newbie
>
> Sentry uses a couple of different APIs to log messages, some are from SLF4J
> and others are from LOG4J dependencies.
> For instance:
> {noformat}
> SLF4J api:
>Logger LOGGER = LoggerFactory.getLogger(GMAuditMetadataLogEntity.class);
> LOG4J api:
>Logger LOGGER = LogManager.getLogger(className);
> {noformat}
> The use of getLogger() is not consistent on Sentry and causes conflicts when
> someone puts a Log4j v2 on the classpath. SLF4J is an interface that uses the
> Log4j implementation detected at runtime. We should use Slf4j APIs to verify
> Sentry can work with any version of Log4j.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614903#comment-16614903
]
Hadoop QA commented on SENTRY-2403:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12939716/SENTRY-2403.002.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/4120/console
This message is automatically generated.
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch, SENTRY-2403.002.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SENTRY-2404) Fetch configurable number of events from HMS on each fetch
kalyan kumar kalvagadda created SENTRY-2404: --- Summary: Fetch configurable number of events from HMS on each fetch Key: SENTRY-2404 URL: https://issues.apache.org/jira/browse/SENTRY-2404 Project: Sentry Issue Type: Improvement Components: Sentry Affects Versions: 2.1.0 Reporter: kalyan kumar kalvagadda Currently sentry fetches 2147483647 every time regardless. This effects the performance of HMS when there are huge number of events in notification_log table. With the latest improvements in HMS it would be good to limit the number to smaller one which is configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614867#comment-16614867
]
Hadoop QA commented on SENTRY-2403:
---
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12939709/SENTRY-2403.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/4119/console
This message is automatically generated.
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch, SENTRY-2403.002.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614816#comment-16614816
]
Sergio Peña commented on SENTRY-2403:
-
[~psomogyi] Can you submit your patch to review board and add a link in this
jira?
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch, SENTRY-2403.002.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergio Peña reassigned SENTRY-2403:
---
Assignee: Peter Somogyi
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch, SENTRY-2403.002.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614697#comment-16614697
]
Peter Somogyi commented on SENTRY-2403:
---
I used an incorrect patch format in version 1. Uploaded a correct one using
{{git diff > SENTRY-2403.001.patch.}}
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch, SENTRY-2403.002.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi updated SENTRY-2403:
--
Attachment: SENTRY-2403.002.patch
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch, SENTRY-2403.002.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614676#comment-16614676
]
Peter Somogyi commented on SENTRY-2403:
---
Could someone assign me to this issue? I don't have an option for this.
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi updated SENTRY-2403:
--
Status: Patch Available (was: Open)
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
[
https://issues.apache.org/jira/browse/SENTRY-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi updated SENTRY-2403:
--
Attachment: SENTRY-2403.001.patch
> Incorrect naming in RollingFileWithoutDeleteAppender
>
>
> Key: SENTRY-2403
> URL: https://issues.apache.org/jira/browse/SENTRY-2403
> Project: Sentry
> Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Peter Somogyi
>Priority: Major
> Labels: log
> Attachments: SENTRY-2403.001.patch
>
>
> RollingFileWithoutDeleteAppender names the log files incorrectly. The current
> timestamp is appended to the end of the current log file when rollOver() is
> called and the previous timestamp is not removed.
> The following files are generated:
> {noformat}
> auditLog.log.1536920157248
> auditLog.log.1536920157248.1536920157256
> auditLog.log.1536920157248.1536920157256.1536920157265
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
> auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
> {noformat}
> This can cause problem on certain filesystems (e.g. ext4) when the filename
> reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SENTRY-2403) Incorrect naming in RollingFileWithoutDeleteAppender
Peter Somogyi created SENTRY-2403:
-
Summary: Incorrect naming in RollingFileWithoutDeleteAppender
Key: SENTRY-2403
URL: https://issues.apache.org/jira/browse/SENTRY-2403
Project: Sentry
Issue Type: Bug
Affects Versions: 1.6.0
Reporter: Peter Somogyi
RollingFileWithoutDeleteAppender names the log files incorrectly. The current
timestamp is appended to the end of the current log file when rollOver() is
called and the previous timestamp is not removed.
The following files are generated:
{noformat}
auditLog.log.1536920157248
auditLog.log.1536920157248.1536920157256
auditLog.log.1536920157248.1536920157256.1536920157265
auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268
auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270
auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272
auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274
auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276
auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278
auditLog.log.1536920157248.1536920157256.1536920157265.1536920157268.1536920157270.1536920157272.1536920157274.1536920157276.1536920157278.1536920157279
{noformat}
This can cause problem on certain filesystems (e.g. ext4) when the filename
reaches 255 characters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
