This is an automated email from the ASF dual-hosted git repository.
ahmedabualsaud pushed a commit to branch release-2.57.0
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/release-2.57.0 by this push:
new 6cbf144f21b fix managed doc (#31521)
6cbf144f21b is described below
commit 6cbf144f21b46a1b3d181ea340eba8ef2d3d21bc
Author: Ahmed Abualsaud <[email protected]>
AuthorDate: Wed Jun 5 19:34:05 2024 -0400
fix managed doc (#31521)
---
.../managed/src/main/java/org/apache/beam/sdk/managed/Managed.java | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
a/sdks/java/managed/src/main/java/org/apache/beam/sdk/managed/Managed.java
b/sdks/java/managed/src/main/java/org/apache/beam/sdk/managed/Managed.java
index 6f95290e6ee..911e25cdda1 100644
--- a/sdks/java/managed/src/main/java/org/apache/beam/sdk/managed/Managed.java
+++ b/sdks/java/managed/src/main/java/org/apache/beam/sdk/managed/Managed.java
@@ -62,7 +62,8 @@ import
org.apache.beam.vendor.guava.v32_1_2_jre.com.google.common.collect.Immuta
* }</pre>
*
* <p>Instead of specifying configuration arguments directly in the code, one
can provide the
- * location to a YAML file that contains this information. Say we have the
following YAML file:
+ * location to a YAML file that contains this information. Say we have the
following {@code
+ * config.yaml} file:
*
* <pre>{@code
* foo: "abc"
@@ -74,7 +75,7 @@ import
org.apache.beam.vendor.guava.v32_1_2_jre.com.google.common.collect.Immuta
* <pre>{@code
* PCollection<Row> inputRows = pipeline.apply(Create.of(...));
*
- * input.apply(Managed.write(ICEBERG).withConfigUrl(<config path>));
+ *
inputRows.apply(Managed.write(ICEBERG).withConfigUrl("path/to/config.yaml"));
* }</pre>
*/
public class Managed {
