Skip to content
This repository has been archived by the owner on Jan 20, 2023. It is now read-only.

mlUndeploy deleted all forests for DHF FINAL database #27

Open
lifan0127 opened this issue Jun 28, 2019 · 2 comments
Open

mlUndeploy deleted all forests for DHF FINAL database #27

lifan0127 opened this issue Jun 28, 2019 · 2 comments

Comments

@lifan0127
Copy link

I have an existing DHF project with the standard setup of STAGING and FINAL databases. I followed this procedure (https://marklogic-community.github.io/grove/guides/data-hub-framework/) to set up a grove project to consume data from the DHF FINAL database. More specifically I deleted everything except the module-database.json in the ml-config/databases folder so the Grove project only has its own module database.

Delete content-database.json, schemas-database.json, and triggers-database.json from marklogic/ml-config/databases/

It all worked fine and my Grove React app was up and running. However, when I finished my exploration and ran mlUndeploy from the Grove project, it reported an error saying the FINAL database was in use. Then I realized that the undeploy task has deleted all the forests (and the data) associated with my DHF FINAL database. Why would this happen? Isn't it supposed to only remove Grove related artifacts?

Run ./gradlew mlUndeploy from marklogic if you ran mlDeploy previously, to get rid of Grove-specific artifacts.

@grtjn
Copy link
Contributor

grtjn commented Jul 1, 2019

Thanks for reporting this, i'll need to check this with the ml-gradle project..

@grtjn
Copy link
Contributor

grtjn commented Jul 1, 2019

Created a ticket against ml-gradle: marklogic/ml-gradle#479

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants