Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-8056

Ignite Cassandra integration doesn't correctly handle Inet4Address and Inet6Address objects

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.4
    • None
    • cache, cassandra
    • None

    Description

      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?

      Attachments

        Activity

          People

            Unassigned Unassigned
            lokkju Loki Coyote
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: