[ https://issues.redhat.com/browse/TEIIDSB-227?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-227: ---------------------------------------- I needed to review more of this. My assumption about what was going on here was not correct. It should then be imported as a teiid geometry type. Calling st_geomfromwkb on something that is already a geometry value is expected fail as there is no implicit conversion from geometry to blob. That confirms that the value is being imported as a teiid geometry and that you can apply the st_ conversion function to text. Our GeometryType values are serializable, but based upon https://stackoverflow.com/questions/48946230/java-io-streamcorruptedexcep... that seems similar to issues hibernate has had with serdes and geometry types in the past. It shouldn't be a classloading issue as teiid spring boot and hibernate spatial are both depending upon org.locationtech.jts:jts-core 1.16 However Teiid is only providing a regular dialect, not a SpatialDialect. Some of the other comments on stackoverflow post and related indicate that the postgis dialect is required, so we may similarly need to provide a SpatialDialect. -- This message was sent by Atlassian Jira (v7.13.8#713008)