Hi Alexis,
For the SavepointWriter, I've briefly looked over the code and the write
operation is enforced as non-parallel.
Best,
Junrui
Alexis Sarda-Espinosa 于2024年7月6日周六 01:27写道：
> Hi Gabor,
>
> Thanks for the quick response. What about SavepointWriter? In my case I'm
> actually writing a job
Hi Gabor,
Thanks for the quick response. What about SavepointWriter? In my case I'm
actually writing a job that will read from an existing savepoint and modify
some of its data to write a new one.
Regards,
Alexis.
Am Fr., 5. Juli 2024 um 17:37 Uhr schrieb Gabor Somogyi <
gabor.g.somo...@gmail.co
Hi Alexis,
It depends. When one uses SavepointLoader to read metadata only then it's
non-parallel.
SavepointReader however is basically a normal batch job with all its
features.
G
On Fri, Jul 5, 2024 at 5:21 PM Alexis Sarda-Espinosa <
sarda.espin...@gmail.com> wrote:
> Hello,
>
> Really quick
Hello,
Really quick question, when using the state processor API, are all
transformations performed in a non-parallel fashion?
Regards,
Alexis.
Hello,
I am trying to implement a satellite image processing chain. Satellite images
are stored as rasters which are heavy, (several GBs) in a FileSystem (I am
currently using HDFS for testing purpose but will move on S3 when I'll deploy
it on the cloud). So in order to reduce the processing ti
