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

Commit efb1726

Browse files
yoshi-automationyoshi-automation
authored
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"
1 parent cce234c commit efb1726

File tree

3 files changed

+56
-56
lines changed

3 files changed

+56
-56
lines changed

‎proto-google-common-protos/src/main/java/com/google/api/MetricDescriptor.java

+42-42
Original file line numberDiff line numberDiff line change
@@ -2267,11 +2267,11 @@ public com.google.api.MetricDescriptor.ValueType getValueType() {
22672267
* The units in which the metric value is reported. It is only applicable
22682268
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
22692269
* defines the representation of the stored metric values.
2270-
* Different systems may scale the values to be more easily displayed (so a
2271-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
2272-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
2273-
* `KBy`, then the value of the metric is always in thousands of bytes, no
2274-
* matter how it may be displayed..
2270+
* Different systems might scale the values to be more easily displayed (so a
2271+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
2272+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
2273+
* `kBy`, then the value of the metric is always in thousands of bytes, no
2274+
* matter how it might be displayed.
22752275
* If you want a custom metric to record the exact number of CPU-seconds used
22762276
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
22772277
* `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() {
22812281
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
22822282
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
22832283
* The supported units are a subset of [The Unified Code for Units of
2284-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
2284+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
22852285
* **Basic units (UNIT)**
22862286
* * `bit` bit
22872287
* * `By` byte
@@ -2372,11 +2372,11 @@ public java.lang.String getUnit() {
23722372
* The units in which the metric value is reported. It is only applicable
23732373
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
23742374
* defines the representation of the stored metric values.
2375-
* Different systems may scale the values to be more easily displayed (so a
2376-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
2377-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
2378-
* `KBy`, then the value of the metric is always in thousands of bytes, no
2379-
* matter how it may be displayed..
2375+
* Different systems might scale the values to be more easily displayed (so a
2376+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
2377+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
2378+
* `kBy`, then the value of the metric is always in thousands of bytes, no
2379+
* matter how it might be displayed.
23802380
* If you want a custom metric to record the exact number of CPU-seconds used
23812381
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
23822382
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -2386,7 +2386,7 @@ public java.lang.String getUnit() {
23862386
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
23872387
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
23882388
* The supported units are a subset of [The Unified Code for Units of
2389-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
2389+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
23902390
* **Basic units (UNIT)**
23912391
* * `bit` bit
23922392
* * `By` byte
@@ -4159,11 +4159,11 @@ public Builder clearValueType() {
41594159
* The units in which the metric value is reported. It is only applicable
41604160
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
41614161
* defines the representation of the stored metric values.
4162-
* Different systems may scale the values to be more easily displayed (so a
4163-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
4164-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4165-
* `KBy`, then the value of the metric is always in thousands of bytes, no
4166-
* matter how it may be displayed..
4162+
* Different systems might scale the values to be more easily displayed (so a
4163+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
4164+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4165+
* `kBy`, then the value of the metric is always in thousands of bytes, no
4166+
* matter how it might be displayed.
41674167
* If you want a custom metric to record the exact number of CPU-seconds used
41684168
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
41694169
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -4173,7 +4173,7 @@ public Builder clearValueType() {
41734173
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
41744174
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
41754175
* The supported units are a subset of [The Unified Code for Units of
4176-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
4176+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
41774177
* **Basic units (UNIT)**
41784178
* * `bit` bit
41794179
* * `By` byte
@@ -4263,11 +4263,11 @@ public java.lang.String getUnit() {
42634263
* The units in which the metric value is reported. It is only applicable
42644264
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
42654265
* defines the representation of the stored metric values.
4266-
* Different systems may scale the values to be more easily displayed (so a
4267-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
4268-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4269-
* `KBy`, then the value of the metric is always in thousands of bytes, no
4270-
* matter how it may be displayed..
4266+
* Different systems might scale the values to be more easily displayed (so a
4267+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
4268+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4269+
* `kBy`, then the value of the metric is always in thousands of bytes, no
4270+
* matter how it might be displayed.
42714271
* If you want a custom metric to record the exact number of CPU-seconds used
42724272
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
42734273
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -4277,7 +4277,7 @@ public java.lang.String getUnit() {
42774277
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
42784278
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
42794279
* The supported units are a subset of [The Unified Code for Units of
4280-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
4280+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
42814281
* **Basic units (UNIT)**
42824282
* * `bit` bit
42834283
* * `By` byte
@@ -4367,11 +4367,11 @@ public com.google.protobuf.ByteString getUnitBytes() {
43674367
* The units in which the metric value is reported. It is only applicable
43684368
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
43694369
* defines the representation of the stored metric values.
4370-
* Different systems may scale the values to be more easily displayed (so a
4371-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
4372-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4373-
* `KBy`, then the value of the metric is always in thousands of bytes, no
4374-
* matter how it may be displayed..
4370+
* Different systems might scale the values to be more easily displayed (so a
4371+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
4372+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4373+
* `kBy`, then the value of the metric is always in thousands of bytes, no
4374+
* matter how it might be displayed.
43754375
* If you want a custom metric to record the exact number of CPU-seconds used
43764376
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
43774377
* `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() {
43814381
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
43824382
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
43834383
* The supported units are a subset of [The Unified Code for Units of
4384-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
4384+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
43854385
* **Basic units (UNIT)**
43864386
* * `bit` bit
43874387
* * `By` byte
@@ -4470,11 +4470,11 @@ public Builder setUnit(java.lang.String value) {
44704470
* The units in which the metric value is reported. It is only applicable
44714471
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
44724472
* defines the representation of the stored metric values.
4473-
* Different systems may scale the values to be more easily displayed (so a
4474-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
4475-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4476-
* `KBy`, then the value of the metric is always in thousands of bytes, no
4477-
* matter how it may be displayed..
4473+
* Different systems might scale the values to be more easily displayed (so a
4474+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
4475+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4476+
* `kBy`, then the value of the metric is always in thousands of bytes, no
4477+
* matter how it might be displayed.
44784478
* If you want a custom metric to record the exact number of CPU-seconds used
44794479
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
44804480
* `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) {
44844484
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
44854485
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
44864486
* The supported units are a subset of [The Unified Code for Units of
4487-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
4487+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
44884488
* **Basic units (UNIT)**
44894489
* * `bit` bit
44904490
* * `By` byte
@@ -4569,11 +4569,11 @@ public Builder clearUnit() {
45694569
* The units in which the metric value is reported. It is only applicable
45704570
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
45714571
* defines the representation of the stored metric values.
4572-
* Different systems may scale the values to be more easily displayed (so a
4573-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
4574-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4575-
* `KBy`, then the value of the metric is always in thousands of bytes, no
4576-
* matter how it may be displayed..
4572+
* Different systems might scale the values to be more easily displayed (so a
4573+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
4574+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
4575+
* `kBy`, then the value of the metric is always in thousands of bytes, no
4576+
* matter how it might be displayed.
45774577
* If you want a custom metric to record the exact number of CPU-seconds used
45784578
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
45794579
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -4583,7 +4583,7 @@ public Builder clearUnit() {
45834583
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
45844584
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
45854585
* The supported units are a subset of [The Unified Code for Units of
4586-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
4586+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
45874587
* **Basic units (UNIT)**
45884588
* * `bit` bit
45894589
* * `By` byte

‎proto-google-common-protos/src/main/java/com/google/api/MetricDescriptorOrBuilder.java

+12-12
Original file line numberDiff line numberDiff line change
@@ -222,11 +222,11 @@ public interface MetricDescriptorOrBuilder
222222
* The units in which the metric value is reported. It is only applicable
223223
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
224224
* defines the representation of the stored metric values.
225-
* Different systems may scale the values to be more easily displayed (so a
226-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
227-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
228-
* `KBy`, then the value of the metric is always in thousands of bytes, no
229-
* matter how it may be displayed..
225+
* Different systems might scale the values to be more easily displayed (so a
226+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
227+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
228+
* `kBy`, then the value of the metric is always in thousands of bytes, no
229+
* matter how it might be displayed.
230230
* If you want a custom metric to record the exact number of CPU-seconds used
231231
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
232232
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -236,7 +236,7 @@ public interface MetricDescriptorOrBuilder
236236
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
237237
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
238238
* The supported units are a subset of [The Unified Code for Units of
239-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
239+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
240240
* **Basic units (UNIT)**
241241
* * `bit` bit
242242
* * `By` byte
@@ -316,11 +316,11 @@ public interface MetricDescriptorOrBuilder
316316
* The units in which the metric value is reported. It is only applicable
317317
* if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
318318
* defines the representation of the stored metric values.
319-
* Different systems may scale the values to be more easily displayed (so a
320-
* value of `0.02KBy` _might_ be displayed as `20By`, and a value of
321-
* `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
322-
* `KBy`, then the value of the metric is always in thousands of bytes, no
323-
* matter how it may be displayed..
319+
* Different systems might scale the values to be more easily displayed (so a
320+
* value of `0.02kBy` _might_ be displayed as `20By`, and a value of
321+
* `3523kBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
322+
* `kBy`, then the value of the metric is always in thousands of bytes, no
323+
* matter how it might be displayed.
324324
* If you want a custom metric to record the exact number of CPU-seconds used
325325
* by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
326326
* `s{CPU}` (or equivalently `1s{CPU}` or just `s`). If the job uses 12,005
@@ -330,7 +330,7 @@ public interface MetricDescriptorOrBuilder
330330
* `ks{CPU}`, and then write the value `12.005` (which is `12005/1000`),
331331
* or use `Kis{CPU}` and write `11.723` (which is `12005/1024`).
332332
* The supported units are a subset of [The Unified Code for Units of
333-
* Measure](http://unitsofmeasure.org/ucum.html) standard:
333+
* Measure](https://unitsofmeasure.org/ucum.html) standard:
334334
* **Basic units (UNIT)**
335335
* * `bit` bit
336336
* * `By` byte

‎synth.metadata

+2-2
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@
1111
"git": {
1212
"name": "googleapis",
1313
"remote": "https://github.com/googleapis/googleapis.git",
14-
"sha": "468a94a87b9f80d22d1f5e3076d5bab73a5c996f",
15-
"internalRef": "346664095"
14+
"sha": "e8ed994d7c7941f7be74f1e7c6a5a03648d04192",
15+
"internalRef": "352919477"
1616
}
1717
},
1818
{

0 commit comments

Comments
 (0)