[JBoss JIRA] (TEIID-2871) Incorrect datatype conversion for java.lang.Byte
by Patrick Deenen (JIRA)
Patrick Deenen created TEIID-2871:
-------------------------------------
Summary: Incorrect datatype conversion for java.lang.Byte
Key: TEIID-2871
URL: https://issues.jboss.org/browse/TEIID-2871
Project: Teiid
Issue Type: Bug
Components: OData
Environment: On windows 7 with JBoss DV 6 GA
Reporter: Patrick Deenen
Assignee: Steven Hawkins
Priority: Blocker
When doing a simple odata query on a view which contains a column with a data type of byte the following exception is thrown:
{quote}
10:37:46,642 WARN [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-1) TEIID16012 Could not produce a sucessful OData response. Returning status ServerErrorException with message java.lang.Byte cannot be cast to org.odata4j.core.UnsignedByte.: org.odata4j.exceptions.ServerErrorException: java.lang.Byte cannot be cast to org.odata4j.core.UnsignedByte
at org.teiid.odata.LocalClient.executeSQL(LocalClient.java:238) [classes:]
at org.teiid.odata.TeiidProducer.getNavProperty(TeiidProducer.java:90) [classes:]
at org.teiid.odata.TeiidProducer.getEntities(TeiidProducer.java:79) [classes:]
at org.odata4j.producer.resources.EntitiesRequestResource.getEntitiesImpl(EntitiesRequestResource.java:371) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
at org.odata4j.producer.resources.EntitiesRequestResource.getEntities(EntitiesRequestResource.java:266) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_45]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_45]
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:167) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:269) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:227) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:216) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:542) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:524) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:126) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at org.teiid.odata.ODataServletContainerDispatcher.service(ODataServletContainerDispatcher.java:97) [classes:]
at org.teiid.odata.ODataServlet.service(ODataServlet.java:61) [classes:]
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50) [resteasy-jaxrs-2.3.6.Final-redhat-1.jar:2.3.6.Final-redhat-1]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:91)
at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:72)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:499) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45]
Caused by: java.lang.ClassCastException: java.lang.Byte cannot be cast to org.odata4j.core.UnsignedByte
at org.odata4j.core.OSimpleObjects.create(OSimpleObjects.java:47) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
at org.odata4j.core.OProperties.simple(OProperties.java:54) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:]
at org.teiid.odata.EntityList.buildPropery(EntityList.java:105) [classes:]
at org.teiid.odata.EntityList.getEntity(EntityList.java:114) [classes:]
at org.teiid.odata.EntityList.<init>(EntityList.java:85) [classes:]
at org.teiid.odata.LocalClient.executeSQL(LocalClient.java:236) [classes:]
... 35 more
{quote}
This is probably due to the fact that in class org.teiid.translator.odata.ODataTypeManager the following is defined:
{code}
teiidkeyed.put(DataTypeManager.DefaultDataTypes.BYTE, EdmSimpleType.BYTE);
{code}
instead of
{code}
teiidkeyed.put(DataTypeManager.DefaultDataTypes.BYTE, EdmSimpleType.SBYTE);
{code}
The EdmSimpleType.BYTE tries to cast to the build in org.odata4j.core.UnsignedByte type which is not possible for a java.lang.Byte.
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2857) Build Error with Teiid POM Dependency
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2857?page=com.atlassian.jira.plugin... ]
Work on TEIID-2857 started by Van Halbert.
> Build Error with Teiid POM Dependency
> -------------------------------------
>
> Key: TEIID-2857
> URL: https://issues.jboss.org/browse/TEIID-2857
> Project: Teiid
> Issue Type: Bug
> Components: Embedded
> Affects Versions: 8.6
> Reporter: Ivan Chan
> Assignee: Van Halbert
> Labels: teiid
> Fix For: 8.7
>
>
> In the jboss public maven repository:
> https://repository.jboss.org/nexus/content/groups/public
> The teiid-parent-8.6.0.Final.pom file has two dependencies which look to be
> Teiid build/configuration bugs.
> These two issues are causing our source code build to fail.
> The pom file is located here:
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/teiid/...
> In this pom file there are two declared dependencies:
> <version.org.jboss.integration-platform>6.0.0-SNAPSHOT</version.org.jboss.integration-platform>
> <jbossas-version>7.2.0.Alpha1-redhat-4</jbossas-version>
> <dependency>
> <groupId>org.jboss.integration-platform</groupId>
> <artifactId>jboss-integration-platform-bom</artifactId>
> <version>${version.org.jboss.integration-platform}</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> <dependency>
> <groupId>org.jboss.as</groupId>
> <artifactId>jboss-as-parent</artifactId>
> <version>${jbossas-version}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> Here are the issues:
> 1) Snapshot dependency existing in the 8.6.0-FINAL Release
> - jboss-integration-platform-bom/6.0.0-SNAPSHOT
> 2) Declared dependency does not exist in the repo repository.jboss.org
> - jboss-as-parent/7.2.0.Alpha1-redhat-4
> - We see dependencies only for:
> - 7.2.0.Alpha1-SNAPSHOT
> - 7.2.0.Fina
> I'm not sure why these dependencies are needed when pulling in the Teiid artifacts, but perhaps because the <scope> of
> these dependencies is set to "import" (<scope>import</scope>)
> Our usage of the repository.jboss.org is to have snapshots disabled. So that is why the 6.0.0-SNAPSHOT fails to be found.
> For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in
> repository.jboss.org so this also fails.
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2858) Database use of char[>1] cause using Convert(x, x) and negates using an index
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2858?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2858.
-----------------------------------
Resolution: Rejected
Re-resolving as rejected. I do not see from the other issue where there is anything that Teiid is doing that is unexpected - that is the design time metadata contains typing issues and converts. Teiid does not proactively add conversions and the conversions are already present in the plan, so the translator is not involved there.
> Database use of char[>1] cause using Convert(x,x) and negates using an index
> ----------------------------------------------------------------------------
>
> Key: TEIID-2858
> URL: https://issues.jboss.org/browse/TEIID-2858
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> When a database defines a char of length greater than 1, a convert(x,x) is being used in the criteria, and thereby, negating the use of an index and causing table scans.
> Note: There is no option to change the database schemas, because they are from a COTS product.
> I would think there needs to be a solution in the translator such that if it can be detected that its for a char column and that it does not do the convert.
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2857) Build Error with Teiid POM Dependency
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2857?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2857:
----------------------------------
Fix Version/s: 8.7
> Build Error with Teiid POM Dependency
> -------------------------------------
>
> Key: TEIID-2857
> URL: https://issues.jboss.org/browse/TEIID-2857
> Project: Teiid
> Issue Type: Bug
> Components: Embedded
> Affects Versions: 8.6
> Reporter: Ivan Chan
> Assignee: Van Halbert
> Labels: teiid
> Fix For: 8.7
>
>
> In the jboss public maven repository:
> https://repository.jboss.org/nexus/content/groups/public
> The teiid-parent-8.6.0.Final.pom file has two dependencies which look to be
> Teiid build/configuration bugs.
> These two issues are causing our source code build to fail.
> The pom file is located here:
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/teiid/...
> In this pom file there are two declared dependencies:
> <version.org.jboss.integration-platform>6.0.0-SNAPSHOT</version.org.jboss.integration-platform>
> <jbossas-version>7.2.0.Alpha1-redhat-4</jbossas-version>
> <dependency>
> <groupId>org.jboss.integration-platform</groupId>
> <artifactId>jboss-integration-platform-bom</artifactId>
> <version>${version.org.jboss.integration-platform}</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> <dependency>
> <groupId>org.jboss.as</groupId>
> <artifactId>jboss-as-parent</artifactId>
> <version>${jbossas-version}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> Here are the issues:
> 1) Snapshot dependency existing in the 8.6.0-FINAL Release
> - jboss-integration-platform-bom/6.0.0-SNAPSHOT
> 2) Declared dependency does not exist in the repo repository.jboss.org
> - jboss-as-parent/7.2.0.Alpha1-redhat-4
> - We see dependencies only for:
> - 7.2.0.Alpha1-SNAPSHOT
> - 7.2.0.Fina
> I'm not sure why these dependencies are needed when pulling in the Teiid artifacts, but perhaps because the <scope> of
> these dependencies is set to "import" (<scope>import</scope>)
> Our usage of the repository.jboss.org is to have snapshots disabled. So that is why the 6.0.0-SNAPSHOT fails to be found.
> For the 7.2.0.Alpha1-redhat-4 dependency, it does not exist in
> repository.jboss.org so this also fails.
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2859) Provide identity generation for TEXTTABLE and OBJECTTABLE
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2859?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2859.
-----------------------------------
Fix Version/s: 8.7
Resolution: Done
Added for ordinality support to texttable and updated the reference. objecttable does not need language level handled as we already bind a teiid_row_number variable that can be referenced as a column value.
> Provide identity generation for TEXTTABLE and OBJECTTABLE
> ---------------------------------------------------------
>
> Key: TEIID-2859
> URL: https://issues.jboss.org/browse/TEIID-2859
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.7
>
>
> Extend the functionality FOR ORDINALITY defined on XMLTABLE, to TEXTTABLE and OBJECTTABLE.
> This will useful in providing a automatic identity key if the data is being read from sources where there is identity column provided. The faced the issue when loading a text file like
> {code}
> VA,F,1910,Mary,848
> VA,F,1911,Mary,747
> {code}
> Where name each line is a separate row, but they do not have unique identifier attached with them. Also helpful with interfaces like OData where they require a PK on a table. This provides an easier alternative.
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2870) Expand "allow-join" extension property on Foreign Key
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2870:
-----------------------------------
Summary: Expand "allow-join" extension property on Foreign Key
Key: TEIID-2870
URL: https://issues.jboss.org/browse/TEIID-2870
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.7
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Currently "allow-join" property on a Foreign Key, defines if the joins based on that Foreign Key that are valid to push to the source or not, when JOIN capability is turned on at translator level. This feature is used in the MongoDB translator to allow JOINS to pushed to source.
What I have seen is "allow-join" is blanket capability that says it supports all LEFT, RIGHT, INNER and CROSS JOINS. It is useful to define this capability in fine grained manner to allow each kind of JOIN explicitly to control the JOIN behavior.
The need came from MongoDB translator, where INNER,LEFT are possible but CROSS and RIGHT are not.
--
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
10 years, 3 months
[JBoss JIRA] (TEIID-2842) Impala/ HIVE2: Unsupported compress file
by Mike LaSpina (JIRA)
[ https://issues.jboss.org/browse/TEIID-2842?page=com.atlassian.jira.plugin... ]
Mike LaSpina commented on TEIID-2842:
-------------------------------------
I added the LZO codex to the vm, but having trouble with configuring Hive and Impala to work with them. If you have some time, I'd like to do a GTM to work on this. I'll send you my contact info via e-mail.
> Impala/ HIVE2: Unsupported compress file
> -----------------------------------------
>
> Key: TEIID-2842
> URL: https://issues.jboss.org/browse/TEIID-2842
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.6
> Environment: Impala/HIVE2 with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: teiid
> Fix For: 8.7
>
>
> Teiid makes a query call "Describe table" in HiveMetadataProcessor.addTable(....). However, if the table contains compress file, HIVE2 driver would return the following execption:
> {code}
> java.sql.SQLException: AnalysisException: Failed to load metadata for table: default.omniturelogs
> CAUSED BY: TableLoadingException: Failed to load metadata for table:
> omniturelogs
> CAUSED BY: RuntimeException: Compressed text files are not supported: hdfs://localhost.localdomain:8020/user/cloudera/omniturelogs/Omniture.0.tsv.gz
> at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:161)
> at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:149)
> at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:182)
> at org.apache.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:246)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
> at org.teiid.translator.hive.HiveMetadataProcessor.addTable(HiveMetadataProcessor.java:112)
> at org.teiid.translator.hive.HiveMetadataProcessor.getConnectorMetadata(HiveMetadataProcessor.java:48)
>
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:311)
> ... 155 more
> {code}
> Maybe Teiid should call "DESCRIBE FORMATTED table" for table that contains compress file.
> Reference:
> http://grokbase.com/t/cloudera/impala-user/13b7c9apmx/impala-failed-to-qu...
--
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
10 years, 3 months