Storing POJO's to RocksDB state backend

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Storing POJO's to RocksDB state backend

Biplob Biswas
Hi,

I had a simple query as to how POJO's are stored in a state back end like RocksDB? Is it deserialized internally(with a default serde or we have to specify something)? and if yes, is Kryo the default serde?

Thanks,
Biplob
Reply | Threaded
Open this post in threaded view
|

Re: Storing POJO's to RocksDB state backend

Timo Walther
Hi Biplob,

Flink is shipped with own serializers. POJOs and other datatypes are
analyzed automatically. Kryo is only the fallback option, if your class
does not meet the POJO criteria (see [1]). Usually, all
serialization/deserialization to e.g. RocksDB happens internally and the
user doesn't have to think about it.

Regards,
Timo

[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.4/dev/types_serialization.html#flinks-typeinformation-class

Am 02.08.17 um 11:03 schrieb Biplob Biswas:

> Hi,
>
> I had a simple query as to how POJO's are stored in a state back end like
> RocksDB? Is it deserialized internally(with a default serde or we have to
> specify something)? and if yes, is Kryo the default serde?
>
> Thanks,
> Biplob
>
>
>
> --
> View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Storing-POJO-s-to-RocksDB-state-backend-tp14628.html
> Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.