March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3405) Continuation of teiid-3368, pushing changes upstream and aligning with bom version 6.0.0.CR26

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3405?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3405: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Continuation of teiid-3368, pushing changes upstream and aligning with bom version 6.0.0.CR26 > --------------------------------------------------------------------------------------------- > > Key: TEIID-3405 > URL: https://issues.jboss.org/browse/TEIID-3405 > Project: Teiid > Issue Type: Enhancement > Components: Tools > Reporter: Van Halbert > Assignee: Van Halbert > > This is a continuation of TEIID-3368 (fixing the jar name using version), also doing the following: > - update to version 1.0.0 > - update IP Bom to 6.0.0.CR26 > - update settings.xml > - push scripts changes upstream -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3405) Continuation of teiid-3368, pushing changes upstream and aligning with bom version 6.0.0.CR26

by Van Halbert (JIRA)

Van Halbert created TEIID-3405: ---------------------------------- Summary: Continuation of teiid-3368, pushing changes upstream and aligning with bom version 6.0.0.CR26 Key: TEIID-3405 URL: https://issues.jboss.org/browse/TEIID-3405 Project: Teiid Issue Type: Enhancement Components: Tools Reporter: Van Halbert Assignee: Steven Hawkins This is a continuation of TEIID-3368 (fixing the jar name using version), also doing the following: - update to version 1.0.0 - update IP Bom to 6.0.0.CR26 - update settings.xml - push scripts changes upstream -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2786) ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2786?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2786: ------------------------------------------------ Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1048948|https://bugzilla.redhat.com/show_bug.cgi?id=1048948] from ASSIGNED to CLOSED > ModeShape ExecutionFactory.getMetadata fails with java.sql.SQLFeatureNotSupportedException > ------------------------------------------------------------------------------------------ > > Key: TEIID-2786 > URL: https://issues.jboss.org/browse/TEIID-2786 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7 > > Attachments: mode.patch > > > When trying to use the Teiid Designer feature of importing using a Teiid Connection fails when the connection is to ModeShape. The following exception: > 08:33:44,914 ERROR [stderr] (teiid-async-threads - 2) java.sql.SQLFeatureNotSupportedException > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.modeshape.jdbc.JcrMetaData.getTypeInfo(JcrMetaData.java:1656) > 08:33:44,915 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:107) > 08:33:44,915 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "importVDB-vdb.xml" (runtime-name : "importVDB-vdb.xml") > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:280) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.translator.jdbc.modeshape.ModeShapeExecutionFactory.getMetadata(ModeShapeExecutionFactory.java:62) > 08:33:44,916 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:61) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$6.run(VDBService.java:397) > 08:33:44,917 ERROR [stderr] (teiid-async-threads - 2) at org.teiid.jboss.VDBService$7.run(VDBService.java:444) > 08:33:44,918 ERROR [stderr] (teiid-async-threads - 2) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > My guess is the local modeshape jdbc driver hasn't been fully vetted in this area, as the remote JDBC version has been the one used when using the Modeshape eclipse plugin for importing the metadata. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3033: ------------------------------------------------ Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1048948|https://bugzilla.redhat.com/show_bug.cgi?id=1048948] from ASSIGNED to CLOSED > Importing metadata thru Designer versus using dynamic VDB is different > ---------------------------------------------------------------------- > > Key: TEIID-3033 > URL: https://issues.jboss.org/browse/TEIID-3033 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Van Halbert > > The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name. However, in the mode shape translator, this logic isn't being applied -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3133) Impala Time/Date/Timestamp handling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3133?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3133: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1141685, https://bugzilla.redhat.com/show_bug.cgi?id=1207220 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1141685) > Impala Time/Date/Timestamp handling > ----------------------------------- > > Key: TEIID-3133 > URL: https://issues.jboss.org/browse/TEIID-3133 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > Impala supports only TIMESTAMP datatype (see here http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/lates...) > Converted everything into timestamp and now I am trying to get Date and Time parts of the timestamp in Teiid e.g. > SELECT DISTINCT convert(Source.SmallA.TimeValue, time) as TimeValue FROM Source.SmallA ORDER BY TimeValue > But I get TranslatorException: Unexpected exception while translating results: Method not supported > Tried to workaround this but with limited success. For Date it is possible to use to_date function that returns string reprsentation of the date part. For Time I wasn't able to find the solution (have not yet figured out how to use extract function through Teiid). > http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/lates... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3187) Error Casting TimeStamp to Date using Impala

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3187?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3187: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1141685, https://bugzilla.redhat.com/show_bug.cgi?id=1207220 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1141685) > Error Casting TimeStamp to Date using Impala > -------------------------------------------- > > Key: TEIID-3187 > URL: https://issues.jboss.org/browse/TEIID-3187 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9.1, 8.10 > > > With ER3 getting [1] for the conversion of a timestamp to a Date: > convert(Source.smalla.DATEVALUE, date) AS DateValue > [1] > org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0] > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:515) > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135) > at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40) > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79) > at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:264) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:302) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98) > at com.sun.proxy.$Proxy1.read(Unknown Source) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:401) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:524) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:393) > at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:327) > at JDBCClient.execute(JDBCClient.java:80) > at JDBCClient.main(JDBCClient.java:46) > Caused by: org.teiid.core.TeiidProcessingException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0] > at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:381) > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:154) > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.teiid.core.TeiidException: 0 Remote org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT DISTINCT cast(g_0.DATEVALUE AS date) AS c_0 FROM smalla g_0 ORDER BY c_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:325) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > ... 6 more > Caused by: java.sql.SQLException: Remote java.sql.SQLException: AnalysisException: Invalid type cast of g_0.DATEVALUE from TIMESTAMP to DATE -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3324) Boolean fields with null are evaluated to false

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3324?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3324: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1206576|https://bugzilla.redhat.com/show_bug.cgi?id=1206576] from NEW to MODIFIED > Boolean fields with null are evaluated to false > ----------------------------------------------- > > Key: TEIID-3324 > URL: https://issues.jboss.org/browse/TEIID-3324 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.1 > Reporter: Salvatore R > Assignee: Steven Hawkins > Fix For: 8.10, 6.2-8.7.2 > > > I have a source table defined as follows (e.g. in PostgreSQL): > {code:sql} > CREATE TABLE public.test > ( > id integer, > iscustomer boolean > ) > {code} > and the table contains these rows: > {code:sql} > insert into public.test values(1, null); > insert into public.test values(2, true); > insert into public.test values(3, false); > {code} > > When I try to get data from this table in Teiid, the "null" value is evaluated as false: > ||id||iscustomer|| > |1|false| > |2|true| > |3|false| -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3296) Some criteria are missing when indexes are used on the source tables

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3296?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3296: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1206573|https://bugzilla.redhat.com/show_bug.cgi?id=1206573] from NEW to MODIFIED > Some criteria are missing when indexes are used on the source tables > -------------------------------------------------------------------- > > Key: TEIID-3296 > URL: https://issues.jboss.org/browse/TEIID-3296 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Reporter: Salvatore R > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.10, 6.2-8.7.2 > > > The following two tables are defined in two different datasources (PostgreSQL and MySQL): > {code:sql} > CREATE TABLE "pg"."tx1" > ( > a varchar(2147483647), > b varchar(2147483647), > c integer, > d integer, > e integer > ); > CREATE INDEX tx1_b ON "pg"."tx1"(b); > CREATE INDEX tx1_a ON "pg"."tx1"(a); > CREATE INDEX tx1_e ON "pg"."tx1"(e); > CREATE INDEX tx1_d ON "pg"."tx1"(d); > CREATE INDEX tx1_c ON "pg"."tx1"(c); > > CREATE TABLE "my"."tx2" > ( > a integer, > b integer, > c integer, > d integer, > e integer > ); > insert into tx1 VALUES(1,1,1,1,1) ; > insert into tx1 VALUES(1,2,2,2,2) ; > insert into tx1 VALUES(1,2,3,3,3) ; > insert into tx1 VALUES(1,2,3,4,4) ; > insert into tx1 VALUES(1,2,3,4,5) ; > insert into tx2 VALUES(1,2,3,4,5) ; > {code} > Running the following query: > {code:sql} > select tx1.* from pg.tx1 as tx1 join my.tx2 as tx2 on tx1.a=tx2.a and tx1.b=tx2.b and tx1.c=tx2.c and tx1.d=tx2.d and tx1.e!=tx2.e; > {code} > a wrong result is returned: > ||a||b||c||d||e|| > |1|2|2|2|2| > |1|2|3|3|3| > |1|2|3|4|4| > If indexes are removed from the source table, the expected result is correctly returned: > ||a||b||c||d||e|| > |1|2|3|4|4| -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3344) Querying server-generated REST WAR fails with NPE when parameter is of type string

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3344?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3344: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1193822|https://bugzilla.redhat.com/show_bug.cgi?id=1193822] from NEW to MODIFIED > Querying server-generated REST WAR fails with NPE when parameter is of type string > ---------------------------------------------------------------------------------- > > Key: TEIID-3344 > URL: https://issues.jboss.org/browse/TEIID-3344 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.10, 6.2-8.7.2 > > Attachments: stacktrace, virtualrest-vdb.xml > > > When the attached dynamic VDB is deployed, querying http://localhost:8080/sample_1/view/proc1/1 causes a NullPointerException (stacktrace from log attached). > Querying the other procedures in the VDB (proc2 - proc4, which are identical except for the type of the parameter) works as expected. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3279) SOLR: Error when date, time or timestamp literal is in where clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3279?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3279: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1180107|https://bugzilla.redhat.com/show_bug.cgi?id=1180107] from NEW to MODIFIED > SOLR: Error when date,time or timestamp literal is in where clause > ------------------------------------------------------------------ > > Key: TEIID-3279 > URL: https://issues.jboss.org/browse/TEIID-3279 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.10 > > > Query fails when time,date or timestamp literal is used in where clause. > Examples: > Query: > {code}select intkey from smalla where timevalue = '11:30:20'{code} > Error: > {code} > '11:30:20'org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'11-30-20' > at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491) > {code} > Query: > {code}select intkey from smalla where datevalue = '2002-02-02'{code} > Error: > {code} > org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'11-30-20' > at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491) > {code} > Query: > {code}select intkey from smalla where timestampvalue = '2000-01-01 00:00:04'{code} > Error: > {code} org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Invalid Date String:'2000-01-01T00-00-04' > at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:491) > {code} > SOLR supports only timestamps (YYYY-mm-ddThh:mm:ssZ) so date and time types should be converted into timestamp before a query is send to SOLR. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015