Sounds correct to me; it's not a POJO so it is treated as a generic
type, which go through Kryo.
If you want to be doubly-sure that your serializer is in fact used, add
a log statement to the read/write methods.
On 09/03/2022 08:10, guoliubi...@foxmail.com wrote:
Hi,
I have an entity
Hi,
I have an entity class built by Google Flatbuf, to raise the performance, I
have tried written a serializer class.
public class TransactionSerializer extends Serializer {
@Override
public void write(Kryo kryo, Output output, Transaction transaction) {
ByteBuffer
ote:
Hi,
I'm trying to write a Flink job (with the Python streaming API)
that handles a custom type that needs a custom Kryo serializer.
When we implemented a similar job in Scala we used
addDefaultKryoSerializer, similar to the instructions in
https://ci.apache.org/projects/flin
4, 2018, at 7:30 PM, Joe Malt wrote:
>
> Hi,
>
> I'm trying to write a Flink job (with the Python streaming API) that
> handles a custom type that needs a custom Kryo serializer.
>
> When we implemented a similar job in Scala we used
> addDefaultKryoSerializer, similar to the
Hi Joe,
Probably Chesnay (cc’ed) may have a better idea on why this is happening.
Cheers,
Kostas
> On Sep 14, 2018, at 7:30 PM, Joe Malt wrote:
>
> Hi,
>
> I'm trying to write a Flink job (with the Python streaming API) that handles
> a custom type that needs a cust
Hi,
I'm trying to write a Flink job (with the Python streaming API) that
handles a custom type that needs a custom Kryo serializer.
When we implemented a similar job in Scala we used addDefaultKryoSerializer,
similar to the instructions in
https://ci.apache.org/projects/flink/flink-docs-release
lightbend.com/
Begin forwarded message:
*From: *Boris Lublinsky <boris.lublin...@lightbend.com
<mailto:boris.lublin...@lightbend.com>>
*Subject: **Re: Custom Kryo serializer*
*Date: *July 19, 2017 at 8:28:16 AM CDT
*To: *user@flink.apache.org <mailto:user@flink.apache.org>
/ <https://www.lightbend.com/>
>>
>>> Begin forwarded message:
>>>
>>> From: Boris Lublinsky <boris.lublin...@lightbend.com
>>> <mailto:boris.lublin...@lightbend.com>>
>>> Subject: Re: Custom Kryo serializer
>>> Date:
linsky <boris.lublin...@lightbend.com
<mailto:boris.lublin...@lightbend.com>>
*Subject: **Re: Custom Kryo serializer*
*Date: *July 19, 2017 at 8:28:16 AM CDT
*To: *user@flink.apache.org <mailto:user@flink.apache.org>,
ches...@apache.org <mailto:ches...@apache.org>
Is there a chance, this can be answered?
Boris Lublinsky
FDP Architect
boris.lublin...@lightbend.com
https://www.lightbend.com/
> Begin forwarded message:
>
> From: Boris Lublinsky <boris.lublin...@lightbend.com>
> Subject: Re: Custom Kryo serializer
> Date: July 19, 2
Wed, Jul 19, 2017 at 1:34 PM
Subject: Re: Custom Kryo serializer
To: user@flink.apache.org <mailto:user@flink.apache.org>
Hello,
I assume you're passing the class of your serializer in a
StateDescriptor constructor.
If so, you could add a breakpoint in
Statedescriptor#initializeSerial
e.org <mailto:ches...@apache.org>>
> Date: Wed, Jul 19, 2017 at 1:34 PM
> Subject: Re: Custom Kryo serializer
> To: user@flink.apache.org <mailto:user@flink.apache.org>
>
>
> Hello,
>
> I assume you're passing the class of your serializer in a StateDescript
Hello,
I assume you're passing the class of your serializer in a
StateDescriptor constructor.
If so, you could add a breakpoint in
Statedescriptor#initializeSerializerUnlessSet,
and check what typeInfo is created and which serializer is created as a
result.
One thing you could try right
Hi
I have several implementations of my Model trait,
trait Model {
def score(input : AnyVal) : AnyVal
def cleanup() : Unit
def toBytes() : Array[Byte]
def getType : Long
}
neither one of them are serializable, but are used in the state definition.
So I implemented custom serializer
14 matches
Mail list logo
