[
https://issues.apache.org/jira/browse/BOOKKEEPER-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275154#comment-14275154
]
Hudson commented on BOOKKEEPER-634:
-----------------------------------
SUCCESS: Integrated in bookkeeper-master #920 (See
[https://builds.apache.org/job/bookkeeper-master/920/])
BOOKKEEPER-634: Provide admin tool to rename bookie identifier in ledger
metadata (rakeshr via ivank) (ivank: rev
99b40326fed855906b709cbe1f562f45bda79e5d)
*
bookkeeper-server/src/test/java/org/apache/bookkeeper/test/BookKeeperClusterTestCase.java
*
bookkeeper-server/src/test/java/org/apache/bookkeeper/client/UpdateLedgerOpTest.java
*
bookkeeper-server/src/test/java/org/apache/bookkeeper/client/UpdateLedgerCmdTest.java
*
bookkeeper-server/src/main/java/org/apache/bookkeeper/client/UpdateLedgerOp.java
* bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/BookieShell.java
* CHANGES.txt
> Provide admin tool to rename bookie identifier in ledger metadata
> -----------------------------------------------------------------
>
> Key: BOOKKEEPER-634
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-634
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server
> Affects Versions: 4.2.1
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.4.0
>
> Attachments:
> 0001-BOOKKEEPER-634-Provide-admin-tool-to-rename-bookie-i.patch,
> 0001-BOOKKEEPER-634-initial-draft-version.patch,
> 001-BOOKKEEPER-634-rename-bookieid-in-ledger.patch,
> 002-BOOKKEEPER-634-rename-bookieid-in-ledger.patch,
> 003-BOOKKEEPER-634-update-bookieid-in-ledger.patch,
> 004-BOOKKEEPER-634-update-bookieid-in-ledger.patch,
> 005-BOOKKEEPER-634-update-bookieid-in-ledger.patch,
> 006-BOOKKEEPER-634-update-bookieid-in-ledger.patch,
> 007-BOOKKEEPER-634-update-bookieid-in-ledger.patch,
> BOOKKEEPER-634-rename-bookieid-in-ledger.patch, BOOKKEEPER-634.patch,
> BOOKKEEPER-634.patch
>
>
> This JIRA to discuss about admin tool for changing the bookie's IP to
> hostname.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)