[
https://issues.apache.org/jira/browse/CURATOR-537?focusedWorklogId=762074&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-762074
]
ASF GitHub Bot logged work on CURATOR-537:
------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Apr/22 01:22
Start Date: 26/Apr/22 01:22
Worklog Time Spent: 10m
Work Description: cammckenzie commented on PR #414:
URL: https://github.com/apache/curator/pull/414#issuecomment-1109199154
@tisonkun The change looks fine to me. My only concern is that we're
modifying the name / function of a public API. Perhaps we should leave the
existing implementation of getOurPath and add a new getLastPathIsLeader method?
Issue Time Tracking
-------------------
Worklog Id: (was: 762074)
Time Spent: 1h (was: 50m)
> Expose ourPath in LeaderLatch readonly
> --------------------------------------
>
> Key: CURATOR-537
> URL: https://issues.apache.org/jira/browse/CURATOR-537
> Project: Apache Curator
> Issue Type: Improvement
> Components: Recipes
> Affects Versions: 4.2.0
> Reporter: Zili Chen
> Assignee: Jordan Zimmerman
> Priority: Major
> Fix For: 4.3.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Follow the discussion in user list
> [here|https://lists.apache.org/x/thread.html/b5cf2ea44fca60362262acfb8b81d02a29b34dc18a57272c2d3e8427@%3Cuser.curator.apache.org%3E]
> we found it is worth a ticket to expose ourPath in LeaderLatch readonly. The
> path of the latch is the natural fencing token for an external leader and
> also the effective checker whether contender is still the leader.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
