Hide Forgot
project_key: SOA Since ER4 there are new columns returned by ModeShape JDBC driver jcr:path, jcr:name, jcr:score, mode:localName, mode:depth. When ModeShape.vdb is used then mode_depth is of type long and jcr_score of type double. 10:01:25,904 INFO [STDOUT] jcr_name = of type java.lang.String, 12 10:01:25,904 INFO [STDOUT] jcr_path = / of type java.lang.String, 12 10:01:25,904 INFO [STDOUT] jcr_primaryType = mode:root of type java.lang.String, 12 10:01:25,904 INFO [STDOUT] jcr_score = 1.0 of type java.lang.Double, 8 10:01:25,904 INFO [STDOUT] mode_depth = 0 of type java.lang.Long, -5 10:01:25,904 INFO [STDOUT] mode_localName = of type java.lang.String, 12 But when plain ModeShape JDBC driver is used then all columns are of type String even of non-string values 10:01:25,063 INFO [STDOUT] jcr:primaryType = mode:root of type java.lang.String, 12 10:01:25,064 INFO [STDOUT] jcr:path = / of type java.lang.String, 12 10:01:25,064 INFO [STDOUT] jcr:name = of type java.lang.String, 12 10:01:25,064 INFO [STDOUT] jcr:score = 1.0 of type java.lang.String, 12 10:01:25,064 INFO [STDOUT] mode:localName = of type java.lang.String, 12 10:01:25,064 INFO [STDOUT] mode:depth = 0 of type java.lang.String, 12 ModeShape JDBC driver should use sensible datatypes too.
Link: Added: This issue Cloned to SOA-2565
If this is related to resultset metadata, then this is a known issue for the 5.1 release and is to be done in a future release of ModeShape. However, if this is based on the DataBaseMetadata, then this is an issue because this is what's relied upon when importing via Teiid Designer. My guess is this is a resultset metadata, otherwise, the datatypes wouldn't be working when building the ModeShape.vdb.
Just to add - the current situation is yet worse - originally MetaData reported String and returned - so it was ocnsistnent. Now the result set returns correct datatypes but incorrect metadata - so it is inconsistent - see 12:12:39,075 INFO [STDOUT] jcr:score = 1.4054651260375977 of type java.lang.Double, 12 12:12:39,075 INFO [STDOUT] mode:depth = 1 of type java.lang.Long, 12
Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2561 The Modeshape JBDC driver was reporting the wrong metadata for some of its columns: they were set as string, even when they were non-string types. A code fix has bbeen applied so that the correct metadata types are now set for these columns.
Verified in ER5