Skip to content
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.

docs: Updates "unit" description: changes "KBy" to "kBy" #99

Merged
merged 2 commits into from Feb 16, 2021
Merged

docs: Updates "unit" description: changes "KBy" to "kBy" #99

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
585d0bd
docs: Updates "unit" description: changes "KBy" to "kBy"; updates an …
yoshi-automation Jan 21, 2021
6b0e145
Merge branch 'master' into autosynth-googleapis
chingor13 Feb 16, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
84 changes: 42 additions & 42 deletions proto-google-common-protos/src/main/java/com/google/api/MetricDescriptor.java
View file
Open in desktop
Expand Up @@ -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
Neenu1995 marked this conversation as resolved.
Show resolved Hide resolved
* 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.
Neenu1995 marked this conversation as resolved.
Show resolved Hide resolved
* 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
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand All @@ -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
Expand Down
24 changes: 12 additions & 12 deletions proto-google-common-protos/src/main/java/com/google/api/MetricDescriptorOrBuilder.java
View file
Open in desktop
Expand Up @@ -222,11 +222,11 @@ public interface MetricDescriptorOrBuilder
* 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
Expand All @@ -236,7 +236,7 @@ public interface MetricDescriptorOrBuilder
* `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
Expand Down Expand Up @@ -316,11 +316,11 @@ public interface MetricDescriptorOrBuilder
* 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
Expand All @@ -330,7 +330,7 @@ public interface MetricDescriptorOrBuilder
* `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
Expand Down
6 changes: 3 additions & 3 deletions synth.metadata
View file
Open in desktop
Expand Up @@ -4,15 +4,15 @@
"git": {
"name": ".",
"remote": "https://github.com/googleapis/java-common-protos.git",
"sha": "f58036be0edcc3d60181b11cc080ffd5a9af55e5"
"sha": "ad6beb636c6fbd6ede923db4b2132cc2b1c2b5b3"
}
},
{
"git": {
"name": "googleapis",
"remote": "https://github.com/googleapis/googleapis.git",
"sha": "468a94a87b9f80d22d1f5e3076d5bab73a5c996f",
"internalRef": "346664095"
"sha": "e8ed994d7c7941f7be74f1e7c6a5a03648d04192",
"internalRef": "352919477"
}
},
{
Expand Down