[docs] Update Presto version in example in installation/cli.rst

[steveburnett]

Description

Noticed the command example in installation/cli.rst showed 0.286 instead of 0.290.

As this doc PR, once merged, will be part of the 0.292 release, updated the example command to 0.292.

Motivation and Context

Following the current instructions, the user downloads presto-cli-0.290-executable.jar. The rename command shown in the doc is mv presto-cli-0.286-executable.jar presto which does nothing to rename the downloaded presto-cli-0.290-executable.jar.

If there's an automated way to pick up the release version of Presto and include it inside a code block, let me know, but if not then manual updates are the best current answer.

Impact

Documentation.

Test Plan

Local doc build. See screenshot in Description for local doc build result.

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

== NO RELEASE NOTE ==

[imjalpreet]

LGTM.

However, should we mention that it's important to have only one CLI JAR file in the current directory, since we're using the * wildcard now. If there are multiple CLI JAR files present, instead of renaming them, the command will attempt to move all the JARs to a directory named presto

[steveburnett]

LGTM.

However, should we mention that it's important to have only one CLI JAR file in the current directory, since we're using the * wildcard now. If there are multiple CLI JAR files present, instead of renaming them, the command will attempt to move all the JARs to a directory named presto

@imjalpreet good catch! I just tested that by downloading multiple CLI jars then manually renaming the extras to earlier version numbers so I had

presto-cli-0.288-executable.jar
presto-cli-0.289-executable.jar
presto-cli-0.290-executable.jar

in the same directory.
Then I ran the command
mv presto-cli-*-executable.jar presto

The command failed and returned the error
mv: presto is not a directory.

Honestly I think that if we need to add a comment to "only [have] one CLI JAR file in the current directory", it might be better for me to put back in the comment

(Replace ``*`` in the example with the version number of the downloaded jar file)

which would help in the case of multiple CLI JAR files.

[tdcmeehan]

SGTM, let's add back in the comment so it's less ambiguous.

[steveburnett]

SGTM, let's add back in the comment so it's less ambiguous.

Done! (Commits squashed and pushed again)