Cool, thanks. What if the destination is not properly coded and the File naming policy then produces a duplicated path? Will it throw an exception? Overwrite?
Thanks! On Tue, Feb 13, 2018 at 6:23 PM Eugene Kirpichov <kirpic...@google.com> wrote: > Dynamic file writes generate 1 set of files (shards) for every pane firing > of every window of every destination. File naming policy is required to > produce different names for every combination of (destination, shard index, > window, pane) so you never have to append or overwrite. A new element > arriving for a destination after something for that destination has already > been written will simply be in the next pane, or in a different window. > > On Tue, Feb 13, 2018, 6:33 AM Carlos Alonso <car...@mrcalonso.com> wrote: > >> Hi everyone!! >> >> I'm wondering how a TextIO with dynamic routing knows/decides when to >> finalise a file and what happens if after it is finalised, another element >> routed for the same file appears. >> >> Thanks! >> >
