Skip to content
Permalink
Browse files
docs: Updates "unit" description: changes "KBy" to "kBy" (#99)
PiperOrigin-RevId: 352919477
Source-Link: googleapis/googleapis@e8ed994

docs: updates an "http" link to "https"
docs: changes "may" to preferred "might"
  • Loading branch information
yoshi-automation committed Feb 16, 2021
1 parent cce234c commit efb17264f970dcaecb3e59664c99e413baa8bc8f
@@ -2267,11 +2267,11 @@ public com.google.api.MetricDescriptor.ValueType getValueType() {
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -2281,7 +2281,7 @@ public com.google.api.MetricDescriptor.ValueType getValueType() {
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -2372,11 +2372,11 @@ public java.lang.String getUnit() {
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -2386,7 +2386,7 @@ public java.lang.String getUnit() {
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -4159,11 +4159,11 @@ public Builder clearValueType() {
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -4173,7 +4173,7 @@ public Builder clearValueType() {
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -4263,11 +4263,11 @@ public java.lang.String getUnit() {
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -4277,7 +4277,7 @@ public java.lang.String getUnit() {
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -4367,11 +4367,11 @@ public com.google.protobuf.ByteString getUnitBytes() {
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -4381,7 +4381,7 @@ public com.google.protobuf.ByteString getUnitBytes() {
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -4470,11 +4470,11 @@ public Builder setUnit(java.lang.String value) {
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -4484,7 +4484,7 @@ public Builder setUnit(java.lang.String value) {
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -4569,11 +4569,11 @@ public Builder clearUnit() {
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -4583,7 +4583,7 @@ public Builder clearUnit() {
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -222,11 +222,11 @@
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -236,7 +236,7 @@
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -316,11 +316,11 @@
* The units in which the metric value is reported. It is only applicable
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
* defines the representation of the stored metric values.
* Different systems may scale the values to be more easily displayed (so a
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `KBy`, then the value of the metric is always in thousands of bytes, no
* matter how it may be displayed..
* Different systems might scale the values to be more easily displayed (so a
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
* `kBy`, then the value of the metric is always in thousands of bytes, no
* matter how it might be displayed.
* If you want a custom metric to record the exact number of CPU-seconds used
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -330,7 +330,7 @@
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
* The supported units are a subset of [The Unified Code for Units of
* Measure](http://unitsofmeasure.org/ucum.html) standard:
* Measure](https://unitsofmeasure.org/ucum.html) standard:
* **Basic units (UNIT)**
* * `bit` bit
* * `By` byte
@@ -11,8 +11,8 @@
"git": {
"name": "googleapis",
"remote": "https://github.com/googleapis/googleapis.git",
"sha": "468a94a87b9f80d22d1f5e3076d5bab73a5c996f",
"internalRef": "346664095"
"sha": "e8ed994d7c7941f7be74f1e7c6a5a03648d04192",
"internalRef": "352919477"
}
},
{

0 comments on commit efb1726

Please sign in to comment.