[
https://issues.apache.org/jira/browse/KYLIN-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414842#comment-16414842
]
ASF GitHub Bot commented on KYLIN-3305:
---
yiming187 closed pull request #121: KYLIN-3305 Fix typos
`kylin.job.run.as.remote.cmd`
URL: https://github.com/apache/kylin/pull/121
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/website/_dev/dev_env.md b/website/_dev/dev_env.md
index c16330a364..388582f058 100644
--- a/website/_dev/dev_env.md
+++ b/website/_dev/dev_env.md
@@ -87,7 +87,7 @@ Local configuration must be modified to point to your hadoop
sandbox (or CLI) ma
* In **examples/test_case_data/sandbox/kylin.properties**
* Find `sandbox` and replace with your hadoop hosts (if you're using HDP
sandbox, this can be skipped)
- * Find `kylin.job.run.as.remote.cmd` and change it to "true" (in code
repository the default is false, which assume running it on hadoop CLI)
+ * Find `kylin.job.use-remote-cli` and change it to "true" (in code
repository the default is false, which assume running it on hadoop CLI)
* Find `kylin.job.remote.cli.username` and `kylin.job.remote.cli.password`,
fill in the user name and password used to login hadoop cluster for hadoop
command execution; If you're using HDP sandbox, the default username is `root`
and password is `hadoop`.
* In **examples/test_case_data/sandbox**
diff --git a/website/_dev/howto_test.md b/website/_dev/howto_test.md
index 88b1649b3d..1d52ef2cf6 100644
--- a/website/_dev/howto_test.md
+++ b/website/_dev/howto_test.md
@@ -52,7 +52,7 @@ If your sandbox is already provisioned and your code change
will not affect the
### Cube Provision
-Environment cube provision is indeed running kylin cubing jobs to prepare
example cubes in the sandbox. These prepared cubes will be used by the ITs.
Currently provision step is bound with the maven pre-integration-test phase,
and it contains running BuildCubeWithEngine (HBase required),
BuildCubeWithStream(Kafka required) and BuildIIWithStream(Kafka Required). You
can run the mvn commands on you sandbox or your develop computer. For the
latter case you need to set kylin.job.run.as.remote.cmd=true in
__$KYLIN_HOME/examples/test_case_data/sandbox/kylin.properties__.
+Environment cube provision is indeed running kylin cubing jobs to prepare
example cubes in the sandbox. These prepared cubes will be used by the ITs.
Currently provision step is bound with the maven pre-integration-test phase,
and it contains running BuildCubeWithEngine (HBase required),
BuildCubeWithStream(Kafka required) and BuildIIWithStream(Kafka Required). You
can run the mvn commands on you sandbox or your develop computer. For the
latter case you need to set kylin.job.use-remote-cli=true in
__$KYLIN_HOME/examples/test_case_data/sandbox/kylin.properties__.
Try appending `-DfastBuildMode=true` to mvn verify command to speed up
provision by skipping incremental cubing.
## More on v1.3 Mini Cluster
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix typos 'kylin.job.run.as.remote.cmd' to 'kylin.job.use-remote-cli' for
> documents
> ---
>
> Key: KYLIN-3305
> URL: https://issues.apache.org/jira/browse/KYLIN-3305
> Project: Kylin
> Issue Type: Improvement
>Reporter: yongjie zhao
>Priority: Minor
>
> Fix typos 'kylin.job.run.as.remote.cmd' to 'kylin.job.use-remote-cli'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
