I thought there may be some additional logging with the coder id since the
message just said "accumulator coder id %s". It looks like this is just a
bad set of arguments in checkArgument, I put up a fix in [1].
So in fact "external_1HolderCoder" is the coder id. This looks like it
could be an
Hi Piotr,
Are you using the beam master head to dev? Can you share your code? The
x-lang transform can be tested with Flink runner, where SDF is also
supported, such as
https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/portability/flink_runner_test.py#L205-L261
On Tue,
Is there a simple way to register the splittable dofn for cross-language usage?
It's a bit a black box to me right now.
The most meaningful logs for Flink are the ones I pasted and the following:
apache_beam.utils.subprocess_server: INFO: b'[grpc-default-executor-0] WARN
The DirectRunner error looks like it's because the FnApiRunner doesn't
support SDF.
What is the coder id for the Flink error? It looks like the full stack
trace should contain it.
On Mon, Aug 3, 2020 at 10:09 AM Piotr Szuberski
wrote:
> I'm Writing SpannerIO.Write cross-language transform and
I'm Writing SpannerIO.Write cross-language transform and when I try to run it
from python I receive errors:
On Flink:
apache_beam.utils.subprocess_server: INFO: b'Caused by:
java.lang.IllegalArgumentException: Transform external_1HolderCoder uses
unknown accumulator coder id %s'
