[
https://issues.apache.org/jira/browse/IGNITE-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475963#comment-15475963
]
Igor Rudyak commented on IGNITE-3172:
-------------------------------------
Alexey,
I guess you are proposing to use this:
https://maven.apache.org/guides/mini/guide-attached-tests.html right? For this
solution to work you should first do "mvn install" and then "mvn deploy" to
build tests jar for "ignite-cassandra-store" module (according to the doc and I
also checked this as well). It looks bad - you can't compile and build Ignite
project until you do this two steps which are only needing for this tiny
serialisers module. Thus I just created two simple unit tests for Kryo
serializer - think this will be enough.
Regarding your concern that somebody already using Cassandra module and have
special logic to handle IgniteException. It looks very unlikely to me, cause
it's server code which is running on Ignite server nodes, while users just
using IgniteCache API on client side to talk with Ignite. Besides that, I don't
think that it's a good approach to prevent fixing issues in design (even if
they rather minor) just to support backward compatibility with previous
versions.
Anyway I pushed unit tests for serializers module to "ignite-3172" branch and
they are available for your review.
> Ignite-Cassandra serializers
> ----------------------------
>
> Key: IGNITE-3172
> URL: https://issues.apache.org/jira/browse/IGNITE-3172
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Reporter: Igor Rudyak
> Assignee: Igor Rudyak
>
> Ignite-Cassandra module should contain only "standard" serializer based on
> Java serialization mechanism.
> It should be a separate module in Ignite project for all other alternative
> implementations of serializers (based on Kryo, providing compression,
> encryption and etc.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
