-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Spelling #1231
Spelling #1231
Conversation
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
@@ -27,7 +27,7 @@ install-sparkctl: | sparkctl/sparkctl-darwin-amd64 sparkctl/sparkctl-linux-amd64 | |||
sudo cp sparkctl/sparkctl-linux-amd64 /usr/local/bin/sparkctl; \ | |||
sudo chmod +x /usr/local/bin/sparkctl; \ | |||
elif [ "$(UNAME)" = "darwin" ]; then \ | |||
echo "installing macos binary to /usr/local/bin/sparkctl"; \ | |||
echo "installing macOS binary to /usr/local/bin/sparkctl"; \ |
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.
brand
@@ -14,7 +14,7 @@ The connectors require certain Hadoop properties to be set properly to function. | |||
both through a custom Hadoop configuration file, namely, `core-site.xml` in a custom image, or via the `spec.hadoopConf` | |||
section in a `SparkApplication`. The example Dockerfile mentioned above shows the use of a custom `core-site.xml` and a | |||
custom `spark-env.sh` that points the environment variable `HADOOP_CONF_DIR` to the directory in the container where | |||
`core-site.xml` is located. The example `core-sitem.xml` and `spark-env.sh` can be found | |||
`core-site.xml` is located. The example `core-site.xml` and `spark-env.sh` can be found |
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.
file...
@@ -14,7 +14,7 @@ The connectors require certain Hadoop properties to be set properly to function. | |||
both through a custom Hadoop configuration file, namely, `core-site.xml` in a custom image, or via the `spec.hadoopConf` | |||
section in a `SparkApplication`. The example Dockerfile mentioned above shows the use of a custom `core-site.xml` and a | |||
custom `spark-env.sh` that points the environment variable `HADOOP_CONF_DIR` to the directory in the container where | |||
`core-site.xml` is located. The example `core-sitem.xml` and `spark-env.sh` can be found | |||
`core-site.xml` is located. The example `core-site.xml` and `spark-env.sh` can be found | |||
[here](https://github.com/GoogleCloudPlatform/spark-on-k8s-gcp-examples/tree/master/conf). |
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.
Note that here
is not good style. https://www.w3.org/TR/WCAG20-TECHS/F84.html
I may at some point send a docs PR (it's really outside the scope of this PR, the whitespace change at the end of this is really out of scope too)
@@ -447,7 +447,7 @@ Note that the mutating admission webhook is needed to use this feature. Please r | |||
### Using Security Context | |||
|
|||
A `SparkApplication` can specify a `SecurityContext` for the driver or executor containers, using the optional field `.spec.driver.securityContext` or `.spec.executor.securityContext`. | |||
`SparkApplication` can also specify a `PodSecurityContext` for the driver or executor pod, using the optional field `.spec.driver.PodsecurityContext` or `.spec.executor.PodsecurityContext`. Below is an example: | |||
`SparkApplication` can also specify a `PodSecurityContext` for the driver or executor pod, using the optional field `.spec.driver.podSecurityContext` or `.spec.executor.podSecurityContext`. Below is an example: |
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.
these reference an item 5 lines below
@@ -1,18 +1,18 @@ | |||
## Who Is Using the Kubernetes Operator for Apache Spark? | |||
|
|||
| Organization | Contact (Github User Name) | Environment | Description of Use | | |||
| Organization | Contact (GitHub User Name) | Environment | Description of Use | |
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.
brand
| ------------- | ------------- | ------------- | ------------- | | ||
| [Caicloud](https://intl.caicloud.io/) | @gaocegege | Production | Cloud-Native AI Platform | | ||
| Microsoft (MileIQ) |@dharmeshkakadia| Production | AI & Analytics | | ||
| Lightbend |@yuchaoran2011| Production | Data Infrastructure & Operations | | ||
| Microsoft (MileIQ) | @dharmeshkakadia | Production | AI & Analytics | |
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 rest of these are whitespace. The file will not be checked by my tool going forward.
@@ -177,7 +177,7 @@ func (c *Controller) Stop() { | |||
// Callback function called when a new SparkApplication object gets created. | |||
func (c *Controller) onAdd(obj interface{}) { | |||
app := obj.(*v1beta2.SparkApplication) | |||
glog.Infof("SparkApplication %s/%s was added, enqueueing it for submission", app.Namespace, app.Name) | |||
glog.Infof("SparkApplication %s/%s was added, enqueuing it for submission", app.Namespace, app.Name) |
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.
Both flavors are used in this corpus. Google Ngrams, enqueuing is winning.
@@ -26,7 +26,7 @@ rules: | |||
app_namespace: "$1" | |||
app_id: "$2" | |||
# These come from the application driver if it's a structured streaming application | |||
# Example: default/sstreaming.driver.spark.streaming.QueryName.inputRate-total | |||
# Example: default/streaming.driver.spark.streaming.QueryName.inputRate-total |
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'm assuming this is right
@@ -32,7 +32,7 @@ import ( | |||
func buildConfig(kubeConfig string) (*rest.Config, error) { | |||
// Check if kubeConfig exist | |||
if _, err := os.Stat(kubeConfig); os.IsNotExist(err) { | |||
// Try InclusterConfig for sparkctl running in a pod | |||
// Try InClusterConfig for sparkctl running in a pod |
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.
To match the next line
Thanks for fixing those! |
* spelling: additional Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: additionally Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: annotations Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: application Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: configuration Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: context Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: defaults Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: dependencies Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: details Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: enqueuing Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: existence Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: github Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: in-cluster Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: macos Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: metric Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: namespaces Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: optionally Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: package Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: period Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: podsecuritycontext Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: relative Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: scheduler Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: service Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: site Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: specifying Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: standard Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: streaming Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: successful Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: termination Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: unrelated Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: update Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: usage Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * Whitespace Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at jsoref@e647fad#commitcomment-49714646
The action reports that the changes in this PR would make it happy: jsoref@fd4491d