Skip to content

Commit

Permalink
Bump hard-wired version to 0.7
Browse files Browse the repository at this point in the history
  • Loading branch information
elibarzilay committed Aug 17, 2017
1 parent 8f7f01b commit 1d9f3ad
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 10 deletions.
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,13 +85,13 @@ notebooks. See the [documentation](docs/docker.md) for more on Docker use.
MMLSpark can be conveniently installed on existing Spark clusters via the
`--packages` option, examples:

spark-shell --packages com.microsoft.ml.spark:mmlspark_2.11:0.6 \
spark-shell --packages com.microsoft.ml.spark:mmlspark_2.11:0.7 \
--repositories https://mmlspark.azureedge.net/maven

pyspark --packages com.microsoft.ml.spark:mmlspark_2.11:0.6 \
pyspark --packages com.microsoft.ml.spark:mmlspark_2.11:0.7 \
--repositories https://mmlspark.azureedge.net/maven

spark-submit --packages com.microsoft.ml.spark:mmlspark_2.11:0.6 \
spark-submit --packages com.microsoft.ml.spark:mmlspark_2.11:0.7 \
--repositories https://mmlspark.azureedge.net/maven \
MyApp.jar

Expand All @@ -106,7 +106,7 @@ script actions, see [this
guide](https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-hadoop-customize-cluster-linux#use-a-script-action-during-cluster-creation).

The script action url is:
<https://mmlspark.azureedge.net/buildartifacts/0.6/install-mmlspark.sh>.
<https://mmlspark.azureedge.net/buildartifacts/0.7/install-mmlspark.sh>.

If you're using the Azure Portal to run the script action, go to `Script
actions``Submit new` in the `Overview` section of your cluster blade. In the
Expand All @@ -122,7 +122,7 @@ To install MMLSpark on the
[library from Maven coordinates](https://docs.databricks.com/user-guide/libraries.html#libraries-from-maven-pypi-or-spark-packages)
in your workspace.

For the coordinates use: `com.microsoft.ml.spark:mmlspark:0.6`. Then, under
For the coordinates use: `com.microsoft.ml.spark:mmlspark:0.7`. Then, under
Advanced Options, use `https://mmlspark.azureedge.net/maven` for the repository.
Ensure this library is attached to all clusters you create.

Expand All @@ -137,7 +137,7 @@ your `build.sbt`:

```scala
resolvers += "MMLSpark Repo" at "https://mmlspark.azureedge.net/maven"
libraryDependencies += "com.microsoft.ml.spark" %% "mmlspark" % "0.6"
libraryDependencies += "com.microsoft.ml.spark" %% "mmlspark" % "0.7"
```

### Building from source
Expand Down
8 changes: 4 additions & 4 deletions docs/docker.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ You can now select one of the sample notebooks and run it, or create your own.
In the above, `microsoft/mmlspark` specifies the project and image name that you
want to run. There is another component implicit here which is the *tag* (=
version) that you want to use — specifying it explicitly looks like
`microsoft/mmlspark:0.6` for using the `0.6` tag.
`microsoft/mmlspark:0.7` for using the `0.7` tag.

Leaving `microsoft/mmlspark` by itself has an implicit `latest` tag, so it is
equivalent to `microsoft/mmlspark:latest`. The `latest` tag is identical to the
Expand All @@ -42,7 +42,7 @@ that you will probably want to use can look as follows:
-e ACCEPT_EULA=y \
-p 127.0.0.1:80:8888 \
-v ~/myfiles:/notebooks/myfiles \
microsoft/mmlspark:0.6
microsoft/mmlspark:0.7

In this example, backslashes are used to break things up for readability; you
can enter it as one long like. Note that in powershell, the `myfiles` local
Expand All @@ -52,7 +52,7 @@ path and line breaks looks a little different:
-e ACCEPT_EULA=y `
-p 127.0.0.1:80:8888 `
-v C:\myfiles:/notebooks/myfiles `
microsoft/mmlspark:0.6
microsoft/mmlspark:0.7

Let's break this command and go over the meaning of each part:

Expand Down Expand Up @@ -133,7 +133,7 @@ Let's break this command and go over the meaning of each part:
...
model.write().overwrite().save('myfiles/myTrainedModel.mml')

* **`microsoft/mmlspark:0.6`**
* **`microsoft/mmlspark:0.7`**

Finally, this specifies an explicit version tag for the image that we want to
run.
Expand Down

0 comments on commit 1d9f3ad

Please sign in to comment.