[JBoss JIRA] (TEIIDDES-2038) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2038?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2038:
----------------------------------------
For type_varbinary, the runtime type name is getting set as *string*, but the UUID is getting pulled from the *varbinary* EMF datatype
> While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
> ------------------------------------------…
[View More]---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2038
> URL: https://issues.jboss.org/browse/TEIIDDES-2038
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2038) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2038?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2038:
------------------------------------------
So the follow on thoughts here are:
Where is the string runtime type coming from - that is not correct.
Where is the uuid value coming from? Teiid is using https://github.com/teiid/teiid/blob/8.4.x/engine/src/main/resources/org/t... to bridge between teiid and designer.
> While importing from Deployed BQT2 …
[View More]VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2038
> URL: https://issues.jboss.org/browse/TEIIDDES-2038
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2038) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2038?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2038:
------------------------------------------
> So if the runtime type in the VDB is string why would it not have a type name when queried via JDBC after it was deployed?
Because the index logic has always associated types by the uuid not the name. And the uuid that's being used there does not match any of the known types.
> While importing from …
[View More]Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2038
> URL: https://issues.jboss.org/browse/TEIIDDES-2038
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2038) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2038?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2038:
----------------------------------------
The indexed *runtime type* for *varbinary* is "string*
The Design-time type set on straight JDBC import is *varbinary*
So if the runtime type in the VDB is *string* why would it not have a type name when queried via JDBC after it was deployed?
> While importing from Deployed BQT2 VDB, JDBC type of 0 and type …
[View More]name NULL was returned for column with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2038
> URL: https://issues.jboss.org/browse/TEIIDDES-2038
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2038) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2038?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2038:
------------------------------------------
I'm not sure if we're dealing with the same things yet. Can you provide a simple test case to highlight what you seeing? When I look at the attached project/vdb the type_varbinary column is typed as string.
> While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column …
[View More]with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2038
> URL: https://issues.jboss.org/browse/TEIIDDES-2038
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2038) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2038?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2038:
----------------------------------------
Walking through in debug, I'm in the 8.4 Teiid client's DatabaseMetadataImpl.getColumns() method for the table ALL_TYPES
When I get to the *type_varbinary* column, the value in the column data array for *type_name* == *null*.
So not sure how we can fix this on Designer side?
> While importing from Deployed …
[View More]BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2038
> URL: https://issues.jboss.org/browse/TEIIDDES-2038
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2038) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2038?page=com.atlassian.jira.plu... ]
Steven Hawkins updated TEIIDDES-2038:
-------------------------------------
Assignee: (was: Steven Hawkins)
I'm not sure what you are seeing here. From what I see both resultset metadata and database metadata look appropriate for varbinary. You'll want to dig around a little more on your side to see where things are going astray.
> While importing from Deployed BQT2 VDB, JDBC type …
[View More]of 0 and type name NULL was returned for column with design-time type varbinary
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2038
> URL: https://issues.jboss.org/browse/TEIIDDES-2038
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2038) While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2038?page=com.atlassian.jira.plu... ]
Steven Hawkins moved TEIID-2829 to TEIIDDES-2038:
-------------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-2038 (was: TEIID-2829)
> While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with design-time type varbinary
> -----------------------------------------------------------------------------------…
[View More]----------------------------------------------
>
> Key: TEIIDDES-2038
> URL: https://issues.jboss.org/browse/TEIIDDES-2038
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Assignee: Steven Hawkins
> Attachments: TEIID_2829_project.zip
>
>
> 1) Open attached project in Designer
> 2) Deploy the BQT2.vdb
> 3) Create another project
> 4) Import the VDB metadata via JDBC Importer into your second project (will end up being a read-only VDB source model)
> 5) On *finish* you'll get an exception when processing the type_varbinary column because the type returned is "0" and type name of "null"
> {code}
> java.lang.IllegalArgumentException: Expected argument to be non-null but got null
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:142)
> at org.teiid.core.designer.util.CoreArgCheck.isNotNull(CoreArgCheck.java:128)
> at org.teiid.designer.sdt.types.BuiltInTypesManager.getBuiltInDatatype(BuiltInTypesManager.java:477)
> at org.teiid.designer.sdt.types.WorkspaceDatatypeManager.getBuiltInDatatype(WorkspaceDatatypeManager.java:94)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.findType(RelationalModelProcessorImpl.java:1450)
> at org.teiid.designer.jdbc.relational.impl.RelationalModelProcessorImpl.setColumnInfo(RelationalModelProcessorImpl.java:1321)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2018:
-----------------------------------
Attachment: all_type_jdbc_import_from_vdb.png
> DDL importer creates wrong data type for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> Project: Teiid Designer
> …
[View More]Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
> Attachments: all_type_jdbc_import_from_vdb.png, types_comparison.png
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2018:
----------------------------------------
The intent is to be consistent. In this case I have a SQL Server DB with a BQT table. If I import a column type *int* via JDBC importer, I end up with a design-time type of *int*. If I import via TEiid connection/DDL, the column datatype is defined as *integer*. Currently we set the design-time type to *integer*. So the 2 …
[View More]relational columns end up with different datatypes.
I'm assuming for the moment that our JDBC importer is setting the property design-time type.
The runtime type is determined at index time via a SqlAspect.getRuntimeTypeName(EObject type) which eventually walks the datatype hiearchy to get the base type. (I'll verify that tomorrow)
> DDL importer creates wrong data type for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
> Attachments: types_comparison.png
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
11 years, 1 month