rohdesamuel commented on a change in pull request #17232:
URL: https://github.com/apache/beam/pull/17232#discussion_r840010216



##########
File path: CHANGES.md
##########
@@ -150,6 +152,8 @@
 
 * DataFrame API now supports pandas 1.4.x 
([BEAM-13605](https://issues.apache.org/jira/browse/BEAM-13605)).
 * Go SDK DoFns can now observe trigger panes directly 
([BEAM-13757](https://issues.apache.org/jira/browse/BEAM-13757)).
+* Added option to specify a caching directory (Python) 
([BEAM-13685](https://issues.apache.org/jira/browse/BEAM-13685)).
+* Added support for caching batch pipelines to GCS (Python) 
([BEAM-13734](https://issues.apache.org/jira/browse/BEAM-13734)).

Review comment:
       Please specify that these improvements were specific to Interactive Beam

##########
File path: CHANGES.md
##########
@@ -103,6 +104,7 @@
 
 * Pipeline dependencies supplied through `--requirements_file` will now be 
staged to the runner using binary distributions (wheels) of the PyPI packages 
for linux_x86_64 platform 
([BEAM-4032](https://issues.apache.org/jira/browse/BEAM-4032)). To restore the 
behavior to use source distributions, set pipeline option 
`--requirements_cache_only_sources`. To skip staging the packages at submission 
time, set pipeline option `--requirements_cache=skip` (Python).
 * The Flink runner now supports Flink 1.14.x 
([BEAM-13106](https://issues.apache.org/jira/browse/BEAM-13106)).
+* The Interactive runner now supports remotely executing pipelines on Dataproc 
when the underlying runner is the Flink runner (Python) 
([BEAM-14071](https://issues.apache.org/jira/browse/BEAM-14071)).

Review comment:
       This can be shortened to: 
   "Interactive Beam now supports remotely executing Flink pipelines on 
Dataproc"




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to