[
https://issues.apache.org/jira/browse/GEODE-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295352#comment-16295352
]
ASF GitHub Bot commented on GEODE-3799:
---------------------------------------
kirklund opened a new pull request #1177: Revert "GEODE-3799: Move backups
towards a pluggable architecture (#1…
URL: https://github.com/apache/geode/pull/1177
…109)"
The CI/CD pipeline is blocked due to lots of test failures caused by the
commit for GEODE-3799. This commit reverts that commit until it can be
reintroduced when GEODE-4106 is fixed.
If GEODE-4106 is ready now then we could potentially commit that instead(?).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Create plugin system for specifying where a backup is stored
> ------------------------------------------------------------
>
> Key: GEODE-3799
> URL: https://issues.apache.org/jira/browse/GEODE-3799
> Project: Geode
> Issue Type: Sub-task
> Components: persistence
> Reporter: Nick Reich
> Assignee: Nick Reich
> Fix For: 1.4.0
>
>
> The current logic merges the moving/copying of files with the determining of
> what to backup. To make it possible to store a backup in cloud storage or
> other locations, we need to separate these concerns, putting the variable,
> location-based logic, into a plugin architecture.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
