You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Nick Jacobsen (JIRA)" <ji...@apache.org> on 2018/03/27 11:13:00 UTC

[jira] [Created] (IGNITE-8056) Ignite Cassandra integration doesn't correctly handle Inet4Address and Inet6Address objects

Nick Jacobsen created IGNITE-8056:
-------------------------------------

             Summary: Ignite Cassandra integration doesn't correctly handle Inet4Address and Inet6Address objects
                 Key: IGNITE-8056
                 URL: https://issues.apache.org/jira/browse/IGNITE-8056
             Project: Ignite
          Issue Type: Bug
          Components: cache, cassandra
    Affects Versions: 2.4
            Reporter: Nick Jacobsen


PropertyMappingHelper.getCassandraType correctly handles the inet <-> java.net.InetAddress type, but not it's sub classes of java.net.Inet4Address or java.net.Inet6Address.  As there is no standard way to directly create an InetAddress, this makes it very difficult to use an inet data types for keys in cassandra.

 

In general, shouldn't Cassandra types handle any subclasses of supported classes?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)