-
Notifications
You must be signed in to change notification settings - Fork 11
CDK-886: Add instructions for replacing kite-dataset in /usr/bin #76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
2c4f68e
9784cd0
d84b15c
264c770
3009b08
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,11 +3,33 @@ layout: page | |
| title: Install the Kite Command Line Interface | ||
| --- | ||
|
|
||
| These are the instructions for downloading the Kite command line interface. The most up-to-date instructions for downloading the current version of the software are always available at [http://kitesdk.org/docs/current/Install-Kite.html](http://kitesdk.org/docs/current/Install-Kite.html). | ||
|
|
||
| To download Kite with `curl`, run the following commands from a terminal window: | ||
|
|
||
| ``` | ||
| curl http://central.maven.org/maven2/org/kitesdk/kite-tools/{{site.version}}/kite-tools-{{site.version}}-binary.jar -o {{site.dataset-command}} | ||
| chmod +x {{site.dataset-command}} | ||
| ``` | ||
|
|
||
| The first command downloads the Kite tools JAR to a local file named _{{site.dataset-command}}_. The second changes the access rights on the JAR so that the classes in the JAR are executable. | ||
| The first command downloads the Kite tools JAR to a local file named `{{site.dataset-command}}`. The second changes the access rights on the JAR so that the classes in the JAR are executable. | ||
|
|
||
| ## Verifying the Version In Use | ||
|
|
||
| Some versions of CDH come with `{{site.dataset-command}}` installed. However, it might not be the latest version. To check the version, from a terminal window, enter the following command. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this should start a new section so readers have an obvious choice between installing or replacing an existing command.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, okay. The reason I hesitate to do that is that I'm pretty sure everyone will always need to do something in order to use the latest version of the software. I'll add the heading "Verifying the Version In Use," which will hopefully get them to keep reading. |
||
|
|
||
| ``` | ||
| {{site.dataset-command}} --version | ||
| ``` | ||
|
|
||
| If the version number doesn't match the version you downloaded, you have two options. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These instructions download a specific version, so you can just state the version here. There's a chance that the user is reading an old version of this guide, so it is also a good time to point them at the latest, which is always at /docs/current/Install-Kite.html
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This doesn't make sense to me in this context. These instructions are for verifying that the version installed is the version in use. |
||
|
|
||
| 1. Include the path to `{{site.dataset-command}}` when you invoke commands. For example, if the JAR file is in the current directory, use `./{{site.dataset-command}}`. | ||
|
|
||
| 1. Replace the installed version of `{{site.dataset-command}}`. | ||
| a. Download `{{site.dataset-command}}` (in this example, it is downloaded to the `~/` directory). | ||
| b. Replace the old version of `{{site.dataset-command}}` in the existing location. | ||
| 1. For packages, use `sudo cp ~/{{site.dataset-command}} /usr/lib/kite/bin/{{site.dataset-command}}`. | ||
| 1. For parcels, use `sudo cp ~/{{site.dataset-command}} /opt/cloudera/parcels/lib/kite/bin/{{site.dataset-command}}`. | ||
|
|
||
| c. To verify that the correct version is in use, enter the command `{{site.dataset-command}} --version`. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should include the version that will be installed so that the "current" link makes a bit more sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason for these revisions is that the version of kite-dataset shipped with CDH is almost always going to be an older version of the kite-dataset command than one you install. These are the instructions for installing and verifying that the latest version is in use.
I discovered this issue when I ran kite-dataset from the ~/ directory, with a new kite-dataset JAR in the ~/ directory, but when I invoked commands, they ran from an old version of the command from /usr/lib/kite/bin/ .
I added the "current" link up here in response to an earlier comment.
I'm don't refer to any specific version, because that would have to be updated with each release.