[
https://issues.apache.org/jira/browse/KNOX-2693?focusedWorklogId=708956&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-708956
]
ASF GitHub Bot logged work on KNOX-2693:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jan/22 10:08
Start Date: 14/Jan/22 10:08
Worklog Time Spent: 10m
Work Description: smolnar82 opened a new pull request #531:
URL: https://github.com/apache/knox/pull/531
## What changes were proposed in this pull request?
If there are subsequent changes to a topology and Knox still processes the
one that came earlier it might happen that the second change is disregarded due
to timing issues.
The solution is to make sure Knox always triggers an `UPDATE` event
regardless of
- the topology file's timestamp
- or the `is change required` condition.
## How was this patch tested?
Updated and ran unit tests as well as conducted manual testing.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 708956)
Remaining Estimate: 0h
Time Spent: 10m
> When topology is updated twice consecutively with 275ms delay then redeployed
> topology doesnt have 2nd updates
> --------------------------------------------------------------------------------------------------------------
>
> Key: KNOX-2693
> URL: https://issues.apache.org/jira/browse/KNOX-2693
> Project: Apache Knox
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: J.Andreina
> Assignee: Sandor Molnar
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *ENV:*
> Have a custom topology_1.xml with below provider
> {noformat}
> <provider>
> <role>authorization</role>
> <name>CompositeAuthz</name>
> <enabled>true</enabled>
> <param>
> <name>AclsAuthz.atlas-api.acl</name>
> <value>user1;group1;10.10.10.10</value>
> </param>
> </provider>{noformat}
> *Steps:*
> 1. Replace acl "user1" value to "guest" using sed
> sed -i -e 's#user1#guest#g' topology_1.xml
> 2. Within 250 ms issue another sed command to replace acl "group1" value to
> "analyst"
> sed -i -e 's#group1#analyst#g' topology_1.xml
> *{color:red}Issue:{color}*
> After 5 mins redeployed topology_1.xml still have "group1" as acl value
> instead of having analyst.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
