damccorm opened a new issue, #21212:
URL: https://github.com/apache/beam/issues/21212

   
[Unlike](https://github.com/apache/beam/blob/a92965969fda3d7be5b65996d1a9a5b7dd373119/sdks/python/apache_beam/io/fileio.py#L476-L483)
 [FileIO 
module](https://beam.apache.org/releases/pydoc/2.32.0/apache_beam.io.fileio.html),
 theĀ 
[FileBasedSink](https://beam.apache.org/releases/pydoc/2.32.0/apache_beam.io.filebasedsink.html)
 module [doesn't 
respect](https://github.com/apache/beam/blob/2c619c81082839e054f16efee9311b9f74b6e436/sdks/python/apache_beam/io/filebasedsink.py#L164-L177)
 the 
_[temp_location](https://beam.apache.org/releases/pydoc/2.32.0/_modules/apache_beam/options/pipeline_options.html)_
 pipeline option. This isn't expected and documented properly in the respective 
module's documentation.
   
   I do understand that the _temp_location_ [is technically a pipeline option 
that's only required by the 
DataflowRunner](https://github.com/apache/beam/blob/cf8e08f51bc9b1b25f6ee8007dfcc0fa04322e15/sdks/python/apache_beam/options/pipeline_options.py#L626-L631)
 but I think it might be worth it to pluck it out of the DataflowRunner and 
make it be a global pipeline option.
   
   In addition, I couldn't info on what is the difference between 
[WriteToFiles](https://beam.apache.org/releases/pydoc/2.32.0/apache_beam.io.fileio.html)
 and 
[WriteToText](https://beam.apache.org/releases/pydoc/2.32.0/apache_beam.io.textio.html)
 transforms. It seems that the former uses the FileBasedSink and thus correctly 
writes temporary files to the temp_location when specified but the latter 
doesn't do that.
   
   Imported from Jira 
[BEAM-12932](https://issues.apache.org/jira/browse/BEAM-12932). Original Jira 
may contain additional context.
   Reported by: mareksuscak.


-- 
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