September 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4426) Teiid modules have invalid module descriptor (module.xml)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4426?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4426: -------------------------------- Component/s: Build/Kits > Teiid modules have invalid module descriptor (module.xml) > --------------------------------------------------------- > > Key: TEIID-4426 > URL: https://issues.jboss.org/browse/TEIID-4426 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > More than half of all modules \[1\] in Teiid layer have invalid module.xml file. Each of them states to use XMLNS for module of version 1.0 (_urn:jboss:module:1.0_), but they use _properties_ element, which is available since 1.1. > {code:plain|title=\[1\] Affected modules (module:slot)} > org.jboss.teiid.translator.hbase:main > org.jboss.teiid.translator.simpledb:main > org.jboss.teiid.translator.salesforce:main > org.jboss.teiid.admin:main > org.jboss.teiid.translator.jpa:main > org.jboss.teiid.translator.olap:main > io.swagger:main > org.jboss.teiid.common-core:main > com.fasterxml.jackson:main > com.fasterxml.jackson.dataformat.yaml:main > org.jboss.teiid.translator.cassandra:main > org.jboss.teiid.translator.google.api:main > com.force.api:22 > org.reflections:main > org.jboss.teiid.translator.google:main > org.antlr:4.5 > org.jboss.teiid.translator.jdbc:main > org.osgeo.proj4j:main > org.apache.xmlbeans:main > org.apache.olingo:main > com.google.code.findbugs:main > org.apache.commons.lang:3.3.2 > org.jboss.teiid.translator.simpledb.api:main > org.jboss.teiid.translator.mongodb.api:main > org.jboss.teiid.api:main > org.jboss.teiid.translator.excel:main > com.datastax.cassandra.driver.core:main > com.fasterxml.aalto-xml:main > org.jboss.teiid:main > org.jboss.teiid.translator.ldap:main > org.jboss.teiid.translator.odata:main > com.facebook.presto:main > com.vividsolutions.jts:main > org.jboss.oreva:main > com.fasterxml.jackson.datatype:main > nux.nux:main > org.jboss.teiid.translator.ws:main > org.jboss.teiid.translator.salesforce:34 > dom4j:main > org.jboss.teiid.translator.object:main > org.jboss.teiid.security:main > org.jboss.teiid.translator.infinispan.cache:main > org.jboss.teiid.translator.hive:main > org.jboss.teiid.translator.mongodb:main > org.jboss.teiid.olingo.common:main > net.sf.saxon:main > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4426) Teiid modules have invalid module descriptor (module.xml)

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4426?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4426: -------------------------------- Summary: Teiid modules have invalid module descriptor (module.xml) (was: More than halt of Teiid's modules have invalid module descriptor (module.xml)) > Teiid modules have invalid module descriptor (module.xml) > --------------------------------------------------------- > > Key: TEIID-4426 > URL: https://issues.jboss.org/browse/TEIID-4426 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > More than half of all modules \[1\] in Teiid layer have invalid module.xml file. Each of them states to use XMLNS for module of version 1.0 (_urn:jboss:module:1.0_), but they use _properties_ element, which is available since 1.1. > {code:plain|title=\[1\] Affected modules (module:slot)} > org.jboss.teiid.translator.hbase:main > org.jboss.teiid.translator.simpledb:main > org.jboss.teiid.translator.salesforce:main > org.jboss.teiid.admin:main > org.jboss.teiid.translator.jpa:main > org.jboss.teiid.translator.olap:main > io.swagger:main > org.jboss.teiid.common-core:main > com.fasterxml.jackson:main > com.fasterxml.jackson.dataformat.yaml:main > org.jboss.teiid.translator.cassandra:main > org.jboss.teiid.translator.google.api:main > com.force.api:22 > org.reflections:main > org.jboss.teiid.translator.google:main > org.antlr:4.5 > org.jboss.teiid.translator.jdbc:main > org.osgeo.proj4j:main > org.apache.xmlbeans:main > org.apache.olingo:main > com.google.code.findbugs:main > org.apache.commons.lang:3.3.2 > org.jboss.teiid.translator.simpledb.api:main > org.jboss.teiid.translator.mongodb.api:main > org.jboss.teiid.api:main > org.jboss.teiid.translator.excel:main > com.datastax.cassandra.driver.core:main > com.fasterxml.aalto-xml:main > org.jboss.teiid:main > org.jboss.teiid.translator.ldap:main > org.jboss.teiid.translator.odata:main > com.facebook.presto:main > com.vividsolutions.jts:main > org.jboss.oreva:main > com.fasterxml.jackson.datatype:main > nux.nux:main > org.jboss.teiid.translator.ws:main > org.jboss.teiid.translator.salesforce:34 > dom4j:main > org.jboss.teiid.translator.object:main > org.jboss.teiid.security:main > org.jboss.teiid.translator.infinispan.cache:main > org.jboss.teiid.translator.hive:main > org.jboss.teiid.translator.mongodb:main > org.jboss.teiid.olingo.common:main > net.sf.saxon:main > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Mark Tawk updated TEIID-4427: ----------------------------- Issue Type: Bug (was: Feature Request) > Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal > ----------------------------------------------------------------------------------------- > > Key: TEIID-4427 > URL: https://issues.jboss.org/browse/TEIID-4427 > Project: Teiid > Issue Type: Bug > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Blocker > > After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server. > when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal. > If we go back to Teiid 8.11.3, the same materialized views fetch without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4263) StringToTimestamp in convert fails during DST transition hour

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4263?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4263: ---------------------------------- Fix Version/s: 9.0.4 > StringToTimestamp in convert fails during DST transition hour > ------------------------------------------------------------- > > Key: TEIID-4263 > URL: https://issues.jboss.org/browse/TEIID-4263 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 8.7.7.6_2 > Reporter: Guy Davis > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.4 > > Attachments: ArgentinaTest.java > > > Issue is due to [https://github.com/teiid/teiid/blob/master/common-core/src/main/java/org/... | this line] in StringToTimestampTransform.java. In particular, if you pass in a string date for a timestamp at the beginning of the DST transition hour, the result will be an hour in the future or past, so this string comparison fails, throwing TEIID10060 exception. > Examples include: > * America/Edmonton 2016-03-13 02:00:00 > * America/Argentina/Buenos_Aires 1991-10-20 00:00:00 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4428) Timestamp having 02:XX:XX as time cannot be cast to timestamp when timezone is CET and summertime

by dalex dalex (JIRA)

[ https://issues.jboss.org/browse/TEIID-4428?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-4428: ------------------------------------ [~shawkins] I'm very sorry that I didn't notice duplicate of the issue, thx. > Timestamp having 02:XX:XX as time cannot be cast to timestamp when timezone is CET and summertime > ------------------------------------------------------------------------------------------------- > > Key: TEIID-4428 > URL: https://issues.jboss.org/browse/TEIID-4428 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA > teiid-9.0.3 on WildFly Full 9.0.2.Final > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > > Running the following query: > {code:sql} > select cast ( '2015-03-29 02:20:09' as timestamp ) > {code} > I get such exception: > {code} > 2016-09-06 14:33:08,868 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue15) dxYkAB2TdWA6 TEIID30020 Processing exception for request dxYkAB2TdWA6.5 'TEIID30328 Unable to evaluate convert('2015-03-29 02:20:09', timestamp): TEIID30384 Error while evaluating function convert'. Originally ExpressionEvaluationException 'TEIID10060 The string representation '2 > 015-03-29 02:20:09' of a Timestamp value is not valid.' StringToTimestampTransform.java:67. Enable more detailed logging to see the entire stacktrace. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4428) Timestamp having 02:XX:XX as time cannot be cast to timestamp when timezone is CET and summertime

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4428?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4428. ----------------------------------- Resolution: Duplicate Issue Duplicate of TEIID-4263 - which I'll go ahead and add to 9.0.4. > Timestamp having 02:XX:XX as time cannot be cast to timestamp when timezone is CET and summertime > ------------------------------------------------------------------------------------------------- > > Key: TEIID-4428 > URL: https://issues.jboss.org/browse/TEIID-4428 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA > teiid-9.0.3 on WildFly Full 9.0.2.Final > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Blocker > > Running the following query: > {code:sql} > select cast ( '2015-03-29 02:20:09' as timestamp ) > {code} > I get such exception: > {code} > 2016-09-06 14:33:08,868 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue15) dxYkAB2TdWA6 TEIID30020 Processing exception for request dxYkAB2TdWA6.5 'TEIID30328 Unable to evaluate convert('2015-03-29 02:20:09', timestamp): TEIID30384 Error while evaluating function convert'. Originally ExpressionEvaluationException 'TEIID10060 The string representation '2 > 015-03-29 02:20:09' of a Timestamp value is not valid.' StringToTimestampTransform.java:67. Enable more detailed logging to see the entire stacktrace. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4428) Timestamp having 02:XX:XX as time cannot be cast to timestamp when timezone is CET and summertime

by dalex dalex (JIRA)

dalex dalex created TEIID-4428: ---------------------------------- Summary: Timestamp having 02:XX:XX as time cannot be cast to timestamp when timezone is CET and summertime Key: TEIID-4428 URL: https://issues.jboss.org/browse/TEIID-4428 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.12.x Environment: teiid-8.12-Beta1 on Red Hat JBoss Enterprise Application Platform - Version 6.3.0.GA teiid-9.0.3 on WildFly Full 9.0.2.Final Reporter: dalex dalex Assignee: Steven Hawkins Priority: Blocker Running the following query: {code:sql} select cast ( '2015-03-29 02:20:09' as timestamp ) {code} I get such exception: {code} 2016-09-06 14:33:08,868 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue15) dxYkAB2TdWA6 TEIID30020 Processing exception for request dxYkAB2TdWA6.5 'TEIID30328 Unable to evaluate convert('2015-03-29 02:20:09', timestamp): TEIID30384 Error while evaluating function convert'. Originally ExpressionEvaluationException 'TEIID10060 The string representation '2 015-03-29 02:20:09' of a Timestamp value is not valid.' StringToTimestampTransform.java:67. Enable more detailed logging to see the entire stacktrace. {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Mark Tawk updated TEIID-4427: ----------------------------- Description: After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server. when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal. If we go back to Teiid 8.11.3, the same materialized views fetch without any problem. was: After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server. when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year", we are getting the error : Expected integer, but was bigdecimal. If we go back to Teiid 8.11.3, the same materialized views fetch without any problem. > Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal > ----------------------------------------------------------------------------------------- > > Key: TEIID-4427 > URL: https://issues.jboss.org/browse/TEIID-4427 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Blocker > > After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server. > when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal. > If we go back to Teiid 8.11.3, the same materialized views fetch without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Mark Tawk (JIRA)

Mark Tawk created TEIID-4427: -------------------------------- Summary: Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal Key: TEIID-4427 URL: https://issues.jboss.org/browse/TEIID-4427 Project: Teiid Issue Type: Feature Request Reporter: Mark Tawk Assignee: Steven Hawkins Priority: Blocker After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server. when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year", we are getting the error : Expected integer, but was bigdecimal. If we go back to Teiid 8.11.3, the same materialized views fetch without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4426) More than halt of Teiid's modules have invalid module descriptor (module.xml)

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4426?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4426: ------------------------------------ I suggest change to larger than 1.3, since swarm build depend on moduleparser which base on 1.3 > More than halt of Teiid's modules have invalid module descriptor (module.xml) > ----------------------------------------------------------------------------- > > Key: TEIID-4426 > URL: https://issues.jboss.org/browse/TEIID-4426 > Project: Teiid > Issue Type: Bug > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > More than half of all modules \[1\] in Teiid layer have invalid module.xml file. Each of them states to use XMLNS for module of version 1.0 (_urn:jboss:module:1.0_), but they use _properties_ element, which is available since 1.1. > {code:plain|title=\[1\] Affected modules (module:slot)} > org.jboss.teiid.translator.hbase:main > org.jboss.teiid.translator.simpledb:main > org.jboss.teiid.translator.salesforce:main > org.jboss.teiid.admin:main > org.jboss.teiid.translator.jpa:main > org.jboss.teiid.translator.olap:main > io.swagger:main > org.jboss.teiid.common-core:main > com.fasterxml.jackson:main > com.fasterxml.jackson.dataformat.yaml:main > org.jboss.teiid.translator.cassandra:main > org.jboss.teiid.translator.google.api:main > com.force.api:22 > org.reflections:main > org.jboss.teiid.translator.google:main > org.antlr:4.5 > org.jboss.teiid.translator.jdbc:main > org.osgeo.proj4j:main > org.apache.xmlbeans:main > org.apache.olingo:main > com.google.code.findbugs:main > org.apache.commons.lang:3.3.2 > org.jboss.teiid.translator.simpledb.api:main > org.jboss.teiid.translator.mongodb.api:main > org.jboss.teiid.api:main > org.jboss.teiid.translator.excel:main > com.datastax.cassandra.driver.core:main > com.fasterxml.aalto-xml:main > org.jboss.teiid:main > org.jboss.teiid.translator.ldap:main > org.jboss.teiid.translator.odata:main > com.facebook.presto:main > com.vividsolutions.jts:main > org.jboss.oreva:main > com.fasterxml.jackson.datatype:main > nux.nux:main > org.jboss.teiid.translator.ws:main > org.jboss.teiid.translator.salesforce:34 > dom4j:main > org.jboss.teiid.translator.object:main > org.jboss.teiid.security:main > org.jboss.teiid.translator.infinispan.cache:main > org.jboss.teiid.translator.hive:main > org.jboss.teiid.translator.mongodb:main > org.jboss.teiid.olingo.common:main > net.sf.saxon:main > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2016