Hmm, so if there is this code that wants the $SCHEMA field, I wonder how it
ever worked. Did you try the newly rebuilt avro model against the older Flink
version (1.3.2)?
If possible, you could send the code and we could look into it? OR, could you
try running it in a debugger and set a breakpo
Hi,
It does not. Looking at the generated code, that SCHEMA$ value gets created
in the companion object for the case class (which behaves equivalently to a
static field in java).
This gets compiled down to a classfile with a $ suffix- in this case,
"AlertEvent.SCHEMA$" doesn't exist, and to get t
Hi,
can you check whether AlertEvent actually has a field called "SCHEMA$"? You can
do that via
javap path/to/AlertEvent.class
Best,
Aljoscha
> On 27. Sep 2018, at 10:03, Mark Harris wrote:
>
> Hi,
>
> I recently tried to update a flink job from 1.3.2 to 1.6.0. It deploys
> successfully as
Hi,
I recently tried to update a flink job from 1.3.2 to 1.6.0. It deploys
successfully as usual, but logs the following exception shortly after
starting:
Caused by: org.apache.avro.AvroRuntimeException:
avro.shaded.com.google.common.util.concurrent.UncheckedExecutionException:
org.apache.avro.Av
