January 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2039) Support optional parameter for SOAP Web Services

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-2039: -------------------------------------- Summary: Support optional parameter for SOAP Web Services Key: TEIIDDES-2039 URL: https://issues.jboss.org/browse/TEIIDDES-2039 Project: Teiid Designer Issue Type: Feature Request Components: Web Services Support Reporter: Ramesh Reddy Provide support for optional parameters in generated SOAP web services model in designer. -- … [View More]

11 years, 1 month

1
0
0 / 0

[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 edited comment on TEIIDDES-2018 at 1/31/14 10:38 AM: ------------------------------------------------------------------ So let's walk through a couple scenarios... 1) column named *type_int* of type *int* * JDBC import ** converts to type *int* * Teiid DDL contains type = *integer* and native type = *int* ** converts to type *integer* Q: Should the Teiid Import option look at native type (i.e. *… [View More]int*) and use that instead? or map *integer* >> *int* 2) column named *type_float* * JDBC import ** converts to type *float* * Teiid DDL contains type = *double* and native type = *float* ** converts to type *double* Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float* 3) column named *type_character_10* * JDBC import ** converts to type *char(10)* * Teiid DDL contains type = *string(10)* and native type = *char* ** converts to type *string(10* Q: Should the Teiid Import option look at native type (i.e. *char*) and use that instead? Based on *string(10)* there no way to tell that this is a *char(10)* without looking at the native type was (Author: blafond): So let's walk through a couple scenarios... 1) column named *type_int* of type *int* * JDBC import ** converts to type *int* * Teiid DDL contains type = *integer* and native type = *integer* ** converts to type *integer* Q: Should the Teiid Import option look at native type (i.e. *int*) and use that instead? or map *integer* >> *int* 2) column named *type_float* * JDBC import ** converts to type *float* * Teiid DDL contains type = *double* and native type = *float* ** converts to type *double* Q: Should the Teiid Import option look at native type (i.e. *float*) and use that instead? or map *double* > *float* 3) column named *type_character_10* * JDBC import ** converts to type *char(10)* * Teiid DDL contains type = *string(10)* and native type = *char* ** converts to type *string(10* Q: Should the Teiid Import option look at native type (i.e. *char*) and use that instead? Based on *string(10)* there no way to tell that this is a *char(10)* without looking at the native type > 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: 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

1
0
0 / 0

[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: ---------------------------------------- I'm good with using our UUID (above) and moving on. There are a handful of spots in our transformation code that uses our runtime type. Would be risky at this time to change the runtime types on our side. > While importing from Deployed BQT2 VDB, JDBC type of 0 and type name NULL was returned for column with … [View More]

11 years, 1 month

1
0
0 / 0

[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: ------------------------------------------ > That is the incorrect runtime type, unless the meaning in this file is the xsd/xml representation. I should add that from a runtime perspective, we ignore the runtime type set by designer and override it with the one from the datatypes.dat mapping. So if you need to leave this as string for whatever reason that would be … [View More]

11 years, 1 month

1
0
0 / 0

[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: ------------------------------------------ > Note the runtime type is string as it is for base64Binary, hexBinary and others That is the incorrect runtime type, unless the meaning in this file is the xsd/xml representation. > The UUIDs all seem to match up with your types.dat except for varbinary Yes it looks like we used different versions. The initial Teiid … [View More]

11 years, 1 month

1
0
0 / 0

[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: ---------------------------------------- Our datatype schema is here: https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org.... The varbinary is defined as: {code:xml} <xs:simpleType mmedt:UUID="mmuuid:606b7f4f-08a2-4072-86e2-9915f3952c7d" mmedt:runtimeDataType="string" mmedt:runtimeDataTypeFixed="false" name="varbinary"> <xs:… [View More]annotation> <xs:documentation> The runtime type is a byte[] wrapper called BinaryType</xs:documentation> </xs:annotation> <xs:restriction base="xs:base64Binary"/> </xs:simpleType> {code} Note the runtime type is *string* as it is for *base64Binary*, *hexBinary* and others > While importing from 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

1
0
0 / 0

[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 edited comment on TEIIDDES-2038 at 1/30/14 2:42 PM: ----------------------------------------------------------------- Our datatype schema is here: https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org.... The varbinary is defined as: {code:xml} <xs:simpleType mmedt:UUID="mmuuid:606b7f4f-08a2-4072-86e2-9915f3952c7d" mmedt:runtimeDataType="string" mmedt:… [View More]runtimeDataTypeFixed="false" name="varbinary"> <xs:annotation> <xs:documentation> The runtime type is a byte[] wrapper called BinaryType</xs:documentation> </xs:annotation> <xs:restriction base="xs:base64Binary"/> </xs:simpleType> {code} * Note the runtime type is *string* as it is for *base64Binary*, *hexBinary* and others * The UUIDs all seem to match up with your types.dat except for *varbinary* was (Author: blafond): Our datatype schema is here: https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org.... The varbinary is defined as: {code:xml} <xs:simpleType mmedt:UUID="mmuuid:606b7f4f-08a2-4072-86e2-9915f3952c7d" mmedt:runtimeDataType="string" mmedt:runtimeDataTypeFixed="false" name="varbinary"> <xs:annotation> <xs:documentation> The runtime type is a byte[] wrapper called BinaryType</xs:documentation> </xs:annotation> <xs:restriction base="xs:base64Binary"/> </xs:simpleType> {code} Note the runtime type is *string* as it is for *base64Binary*, *hexBinary* and others > While importing from 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

1
0
0 / 0

[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 edited comment on TEIIDDES-2038 at 1/30/14 2:11 PM: ------------------------------------------------------------------- > For type_varbinary column, the runtime type name is getting set as string, but the UUID is getting pulled from the varbinary EMF datatype. What bit of logic is setting the type name to string? Where are your EMF datatypes defined? > Looking at your mapping file, you … [View More]have no varbinary. The last entry represents varbinary. Are you seeing something else? I believe that it's uuid and the other values were pulled from the simple data types xmi. > Should this be mapped to object like the type_binary apparently is? No. A byte array of fixed or varying length should be mapped to varbinary - since it's the moral equivalent to our string type. What is the source type for type_binary? was (Author: shawkins): > For type_varbinary column, the runtime type name is getting set as string, but the UUID is getting pulled from the varbinary EMF datatype. What bit of logic is setting the type name to string? Where are your EMF datatypes defined? > Looking at your mapping file, you have no varbinary. The last entry represents varbinary. Are you seeing something else? I believe that it's uuid and the other values were pulled from the simple data types xmi. > Should this be mapped to object like the type_binary apparently is? No. A byte array of fixed or varying length should be mapped to varbinary - since it's the moral equivalent to our string class. What is the source type for type_binary? > While importing from 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

1
0
0 / 0

[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: ------------------------------------------ > For type_varbinary column, the runtime type name is getting set as string, but the UUID is getting pulled from the varbinary EMF datatype. What bit of logic is setting the type name to string? Where are your EMF datatypes defined? > Looking at your mapping file, you have no varbinary. The last entry represents … [View More]varbinary. Are you seeing something else? I believe that it's uuid and the other values were pulled from the simple data types xmi. > Should this be mapped to object like the type_binary apparently is? No. A byte array of fixed or varying length should be mapped to varbinary - since it's the moral equivalent to our string class. What is the source type for type_binary? > While importing from 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

1
0
0 / 0

[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 edited comment on TEIIDDES-2038 at 1/30/14 1:38 PM: ----------------------------------------------------------------- For type_varbinary column, the runtime type name is getting set as *string*, but the UUID is getting pulled from the *varbinary* EMF datatype. Looking at your mapping file, you have no *varbinary*. Should this be mapped to *object* like the *type_binary* apparently is? … [View More] was (Author: blafond): 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 > --------------------------------------------------------------------------------------------------------------------------------- > > 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2014