[
https://issues.apache.org/jira/browse/CAMEL-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214616#comment-17214616
]
Jiri Ondrusek commented on CAMEL-15679:
---------------------------------------
[~davsclaus] I'm investigating possibilities for the solution.
Would it be acceptable to change serialization mechanism completely? I see only
one disadvantage, if user has already some data in db file, after upgrade,
changed mechanism won't be able to deserialize data back. Is this scenario
relevant? If so, current mechanism has to stay and only user can define to use
another one.
There are several ways of fixing this:
# it would be nice to use jackson to serialize all except payload. In case
that payload is binary, it would be saved as is, in case of object, it would be
serialized by Jackson with possible customization by allowing
objectMapperCustomizer. (e.g. for the case that serialized object contains some
binary parts)
# Use different mechanism which is working with quarkus as well (I haven't try
any to be 100% sure, but there are some serializers like bson, msgpack, ...)
>From my POV it would be nice to try option 1 - to serialize all except payload
>as json and content save as binary or serialize into json.
WDYT?
> LevelDB: Consider replacing of serizalization via
> org.fusesource.hawtbuf:hawtbuf with Jackson
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-15679
> URL: https://issues.apache.org/jira/browse/CAMEL-15679
> Project: Camel
> Issue Type: Improvement
> Components: camel-leveldb
> Affects Versions: 3.5.0
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Priority: Major
> Fix For: 3.7.0
>
>
> Current implementation of serialization is based on
> `org.fusesource.hawtbuf:hawtbuf` and java object serialization. It would be
> better to use Jackson instead. Here are some reasons:
> # Serialization with Jackson is faster (see
> [http://rick-hightower.blogspot.com/2014/04/which-is-faster-java-object.html])
> # Camel-quarkus can not use java object serialization in native (see
> [https://github.com/oracle/graal/issues/460]) Current workaround uses Jackson
> instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
