This is an automated email from the ASF dual-hosted git repository.

damccorm pushed a commit to branch users/damccorm/pydoc
in repository https://gitbox.apache.org/repos/asf/beam.git

commit f918a069edfc95ee67426c0e66d13fceaea7c736
Author: Danny McCormick <dannymccorm...@google.com>
AuthorDate: Thu Aug 17 15:14:05 2023 -0400

    Fix produce/consume pydoc
---
 sdks/python/apache_beam/ml/transforms/base.py | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/sdks/python/apache_beam/ml/transforms/base.py 
b/sdks/python/apache_beam/ml/transforms/base.py
index 7e13fa39136..54a6bfaaea4 100644
--- a/sdks/python/apache_beam/ml/transforms/base.py
+++ b/sdks/python/apache_beam/ml/transforms/base.py
@@ -122,12 +122,13 @@ class 
MLTransform(beam.PTransform[beam.PCollection[ExampleT],
     MLTransform is a Beam PTransform that can be used to apply
     transformations to the data. MLTransform is used to wrap the
     data processing transforms provided by Apache Beam. MLTransform
-    works in two modes: produce and consume. In the produce mode,
+    works in two modes: write and read. In the write mode,
     MLTransform will apply the transforms to the data and store the
-    artifacts in the artifact_location. In the consume mode, MLTransform
-    will read the artifacts from the artifact_location and apply the
-    transforms to the data. The artifact_location should be a valid
-    storage path where the artifacts can be written to or read from.
+    artifacts in the write_artifact_location. In the read mode,
+    MLTransform will read the artifacts from the
+    read_artifact_location and apply the transforms to the data. The
+    artifact location should be a valid storage path where the artifacts
+    can be written to or read from.
 
     Note that when consuming artifacts, it is not necessary to pass the
     transforms since they are inherently stored within the artifacts

Reply via email to