You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Anilkumar Gingade <ag...@vmware.com> on 2020/06/26 21:04:18 UTC

Re: [Proposal] Add REST command for Restore Redundancy to 1.13 (GEODE-8095)

+1 As Donal said, complete the feature with all the available APIs.

On 6/26/20, 11:50 AM, "Donal Evans" <do...@vmware.com> wrote:

    +1

    Although normally features wouldn't really count as "critical fixes" that would warrant inclusion after the release branch has been cut, in this case, the internal API and gfsh commands for restore redundancy are already in the release, and it makes much more sense to include the entire feature in one release rather than having a semi-complete feature in 1.13 and forcing the REST component to wait for a later release.
    ________________________________
    From: Mark Hanson <mh...@pivotal.io>
    Sent: Friday, June 26, 2020 10:06 AM
    To: dev@geode.apache.org <de...@geode.apache.org>
    Subject: [Proposal] Add REST command for Restore Redundancy to 1.13 (GEODE-8095)

    Hello All,

    The core of the restore redundancy call structure has been refactored to allow there to be a REST call to invoke a restore redundancy. At this point, looking forward to the 1.13 release it would be great if we could fit this into the 1.13 release.

    What do people think?

    Thanks,
    Mark