From 5b62b47b824ae6a8a725214dd6c0ed2de3aa050f Mon Sep 17 00:00:00 2001 From: Jeroen ter Heerdt Date: Wed, 27 Feb 2019 16:38:25 -0800 Subject: [PATCH] Updating readmes --- samples/features/sql-big-data-cluster/app-deploy/README.md | 4 ++-- .../features/sql-big-data-cluster/app-deploy/SSIS/README.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/samples/features/sql-big-data-cluster/app-deploy/README.md b/samples/features/sql-big-data-cluster/app-deploy/README.md index 91c87031..91713495 100644 --- a/samples/features/sql-big-data-cluster/app-deploy/README.md +++ b/samples/features/sql-big-data-cluster/app-deploy/README.md @@ -27,9 +27,9 @@ __[RollDice](RollDice/)__ This sample demonstrates the use of data frames ## MLeap -__[hello-mleap](hello-mleap/)__ +__[mleap](mleap/)__ -This sample demonstrates how you use a MLeap bundle ( a Spark model serialized in this format) and run it outside of Spark. The sample is based on the MLeap sample available here http://mleap-docs.combust.ml/mleap-serving/. We are using the MLeap Serving container that is published in Docker Hub. The MLeap Serving is deployed as container in SQL Server big data cluster as a container app with a web service that takes the Leap Frame as the input. +This sample demonstrates how you use a MLeap bundle (a Spark model serialized in this format) and run it outside of Spark. The sample is based on the MLeap sample available here http://mleap-docs.combust.ml/mleap-serving/. We are using the MLeap Serving container that is published in Docker Hub. The MLeap Serving is deployed as container in SQL Server big data cluster as a container app with a web service that takes the Leap Frame as the input. ## Sql Server Integration Services diff --git a/samples/features/sql-big-data-cluster/app-deploy/SSIS/README.md b/samples/features/sql-big-data-cluster/app-deploy/SSIS/README.md index 6bf2521d..8c477372 100644 --- a/samples/features/sql-big-data-cluster/app-deploy/SSIS/README.md +++ b/samples/features/sql-big-data-cluster/app-deploy/SSIS/README.md @@ -35,7 +35,7 @@ mssqlctl app list Once the app is listed as `Ready` the job should run within a minute. You can check if the backup is created by running: ```bash -kubectl -n test exec -it mssql-master-pool-0 -c mssql-server -- /bin/bash -c "ls /var/opt/mssql/data/*.DWConfigbak" +kubectl -n [your namespace] exec -it mssql-master-pool-0 -c mssql-server -- /bin/bash -c "ls /var/opt/mssql/data/*.DWConfigbak" ``` You should see a backup being created for every run of the job, with a maximum of 60 backups since the SSIS package cleans up backups older than one hour. You can use any of the `.DWConfigbak` files to restore the database. @@ -45,5 +45,5 @@ You can use any of the `.DWConfigbak` files to restore the database. # delete app mssqlctl app delete --name back-up-db --version v1 # delete backup files -kubectl -n test exec -it mssql-master-pool-0 -c mssql-server -- /bin/bash -c "rm /var/opt/mssql/data/*.DWConfigbak" +kubectl -n [your namespace] exec -it mssql-master-pool-0 -c mssql-server -- /bin/bash -c "rm /var/opt/mssql/data/*.DWConfigbak" ```