July 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3359) Allow more control over odata layer caching

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3359?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3359: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1227333|https://bugzilla.redhat.com/show_bug.cgi?id=1227333] from MODIFIED to ON_QA > Allow more control over odata layer caching > ------------------------------------------- > > Key: TEIID-3359 > URL: https://issues.jboss.org/browse/TEIID-3359 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1.6_2, 8.11 > > > The caching is always performed at a user level and for each query. Consumers may need to localize the caching affect only to paging results and scope only to that interaction, rather than for all users. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3557) Can't reload VDB in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3557?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3557: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1234822|https://bugzilla.redhat.com/show_bug.cgi?id=1234822] from MODIFIED to ON_QA > Can't reload VDB in domain mode > ------------------------------- > > Key: TEIID-3557 > URL: https://issues.jboss.org/browse/TEIID-3557 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > > Can't reload VDB in domain mode, get the following error: > Server throws the following exception: > [Server:server-one] 12:26:45,678 ERROR [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40088 Could not replicate object org.teiid.query.tempdata.GlobalTableStoreImpl@4e6c9a30: java.lang.IllegalStateException: cluster 'ModeShape.1' is already connected to singleton transport: [dummy-1435055090515, loopback.1, ModeShape.1, loopback-dynamic.1, $TEIID_BM$, dummy-1435055090188, dummy-1435055205654, $TEIID_ED$, teiid-cache, ddl2-vdb.1] > [Server:server-one] at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:919) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.startStack(JChannel.java:827) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel._preConnect(JChannel.java:525) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:277) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.jgroups.JChannel.connect(JChannel.java:268) [jgroups-3.2.13.Final-redhat-1.jar:3.2.13.Final-redhat-1] > [Server:server-one] at org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:563) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.CompositeGlobalTableStore.createInstance(CompositeGlobalTableStore.java:57) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$1.finishedDeployment(VDBService.java:156) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.VDBRepository.notifyFinished(VDBRepository.java:352) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.deployers.VDBRepository.finishDeployment(VDBRepository.java:308) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.runtime.AbstractVDBDeployer.metadataLoaded(AbstractVDBDeployer.java:202) [teiid-runtime-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService.access$1100(VDBService.java:85) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$6.run(VDBService.java:411) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at org.teiid.jboss.VDBService$7.run(VDBService.java:442) [teiid-jboss-integration-8.7.1.6_2-redhat-2.jar:8.7.1.6_2-redhat-2] > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > [Server:server-one] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:122) > VDB reload works fine in standalone mode. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3547) Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3547?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3547: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1233212|https://bugzilla.redhat.com/show_bug.cgi?id=1233212] from MODIFIED to ON_QA > Oracle and postgres translators - date/time format letters are not translated correctly if pattern ends with non-pattern/non-letter character > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-3547 > URL: https://issues.jboss.org/browse/TEIID-3547 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > Oracle translator seems to support translation of patterns from SimpleDateFormat to oracle's patterns [1], but not for all of them [2]. If Teiid is not able to translate format then it retrieves date/time/timestamp field and format it [2]. However, if pattern ends with non-pattern/non-letter character, pattern is translated only partially and passed to Oracle DB [3] - I have tried number, *, /, \, etc. Similar behavior with postgresql translator > [1] > *Query:* select formattimestamp(timestampvalue, 'y') from bqt1.smalla where intkey=1; > *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'YYYY') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1 > [2] > *Query:* select formattimestamp(timestampvalue, 'D') from bqt1.smalla where intkey=1; > *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1 > [3] > *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s') from bqt1.smalla where intkey=1; > *Source-specific command:* SELECT g_0."TIMESTAMPVALUE" FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1 > *Query:* select formattimestamp(timestampvalue, 'G-y-M-w-W-D-d-F-E-a-H-k-K-h-m-s-') from bqt1.smalla where intkey=1; > *Source-specific command:* SELECT TO_CHAR(g_0."TIMESTAMPVALUE", 'AD-YYYY-------Dy-AM-------') FROM "DV"."SMALLA" g_0 WHERE trunc(g_0."INTKEY") = 1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3474) Inconsistent results of RIGHT function for different datasources

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3474?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3474: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1221051|https://bugzilla.redhat.com/show_bug.cgi?id=1221051] from MODIFIED to ON_QA > Inconsistent results of RIGHT function for different datasources > ---------------------------------------------------------------- > > Key: TEIID-3474 > URL: https://issues.jboss.org/browse/TEIID-3474 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Environment: OS: Fedora 20 > arch: x86_64 > java: oracle 1.8 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > The RIGHT function returns different results for different datasources. Some of those results are inconsistent with definition of the RIGHT(x,y) function. > ======= > +*Query: SELECT intkey, RIGHT(intkey, 1) FROM table ORDER BY intkey*+ > *Teradata, SQLServer, Sybase, Ingres, MySQL, Oracle (this result is OK):* > 0 0 > 1 1 > 2 2 > ... > 10 0 > 11 1 > ... > 100 0 > 101 1 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " > ===== > +*Query:SELECT intkey, RIGHT(intkey, 2) FROM table ORDER BY intkey*+ > *SQLServer, Sybase, Ingress, MySQL, Teradata (this result is OK):* > 0 0 > 1 1 > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Oracle:* > 0 <null> > 1 <null> > 2 <null> > ... > 10 10 > 11 11 > ... > 100 00 > 101 01 > *Postgres:* > 0 0 > 1 1 > 2 2 > ... > 10 10 > 11 11 > ... > 100 100 > 101 101 > *DB2:* > 0 " " > 1 " " > 2 " " > ... > 10 " " > 11 " " > ... > 100 " " > 101 " " -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

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 MODIFIED to ON_QA > 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 > Fix For: 8.7.1.6_2, 8.11 > > > 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.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3524) Database Logging not working

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3524?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3524: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1231050|https://bugzilla.redhat.com/show_bug.cgi?id=1231050] from MODIFIED to ON_QA > Database Logging not working > ---------------------------- > > Key: TEIID-3524 > URL: https://issues.jboss.org/browse/TEIID-3524 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Van Halbert > Fix For: 8.7.1.6_2, 8.11 > > > When using db logging in Teiid, nothing gets inserted into the db. Logs appear at server.log, but not in the db. > I set up the logging as follows: > Created java:/teiid-log-ds datasource. > Added these to logging subsystem: > {code:xml} > <async-handler name="TEIID_COMMAND_LOG"> > <level name="DEBUG"/> > <queue-length value="50"/> > <overflow-action value="block"/> > <subhandlers> > <handler name="TEIID_JPA_LOG"/> > </subhandlers> > </async-handler> > <async-handler name="TEIID_AUDIT_LOG"> > <level name="DEBUG"/> > <queue-length value="50"/> > <overflow-action value="block"/> > <subhandlers> > <handler name="TEIID_JPA_LOG"/> > </subhandlers> > </async-handler> > <custom-handler name="TEIID_JPA_LOG" class="org.teiid.logger.DatabaseAppender" module="org.jboss.teiid.extensions"> > <level name="DEBUG"/> > </custom-handler> > <logger category="org.teiid.COMMAND_LOG"> > <level name="DEBUG"/> > <handlers> > <handler name="TEIID_COMMAND_LOG"/> > </handlers> > </logger> > <logger category="org.teiid.AUDIT_LOG"> > <level name="DEBUG"/> > <handlers> > <handler name="TEIID_AUDIT_LOG"/> > </handlers> > </logger> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3538) Make OData V2 compatible with LINQPad

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3538?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3538: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1233383|https://bugzilla.redhat.com/show_bug.cgi?id=1233383] from MODIFIED to ON_QA > Make OData V2 compatible with LINQPad > ------------------------------------- > > Key: TEIID-3538 > URL: https://issues.jboss.org/browse/TEIID-3538 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Final > Fix For: 8.7.1.6_2, 8.11 > > > Current OData V2 implementation is not able to load in LINQPad https://www.linqpad.net/ > Couple issues found > - List(Edm.xxx) based collections are not supported. V2 Spec did not specify any List based collections. Only Collection(Edm.xxx) type. So, part of TEIID-3471 need to be rolled back and fix with Collection(Edm.xxx) type > - Explicit definition of "not null" in Entity's key property. > - TEIID-3471 did not go far enough to define accepts header to have "application/xml", "application/atom+xml" and "application/json" without "chaset=utf-8" appended to it. TEIID-3471 only added $metadata and service document. BTW, I was under the impression that I did add all the required places, and was surprised not see in commit :( -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3408) Update the quickstarts that refer to using user .properties files and user roles files

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3408?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3408: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1190678|https://bugzilla.redhat.com/show_bug.cgi?id=1190678] from MODIFIED to ON_QA > Update the quickstarts that refer to using user .properties files and user roles files > -------------------------------------------------------------------------------------- > > Key: TEIID-3408 > URL: https://issues.jboss.org/browse/TEIID-3408 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > Update the quoickstarts that still refer to using user security .properties and user roles files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3407) Clarify in the README's for each quickstart regarding how to start the server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3407?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3407: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1190678|https://bugzilla.redhat.com/show_bug.cgi?id=1190678] from MODIFIED to ON_QA > Clarify in the README's for each quickstart regarding how to start the server > ----------------------------------------------------------------------------- > > Key: TEIID-3407 > URL: https://issues.jboss.org/browse/TEIID-3407 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Trivial > > Change the start command in the README's to be the following: > To start the server, open a command line and navigate to the "bin" directory under the root directory of the JBoss server and run: > > For Linux: ./standalone.sh > for Windows: standalone.bat > append the following to the command to indicate which configuration to use if Teiid isn't configured in the default configuration > > -c standalone-teiid.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3544) teiid-odata-*.war not deploying in EAP when using domain

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3544?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3544: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1233001|https://bugzilla.redhat.com/show_bug.cgi?id=1233001] from MODIFIED to ON_QA > teiid-odata-*.war not deploying in EAP when using domain > -------------------------------------------------------- > > Key: TEIID-3544 > URL: https://issues.jboss.org/browse/TEIID-3544 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 8.7.1.6_2 > > > The Teiid odata war, located: > modules/system/layers/dv/org/jboss/teiid/main/deployments/teiid-odata-8.7.1.6_2-redhat-2.war > was not being deployed. It's working in standalone. > The workaround in domain mode is to re-deploy the war using the admin console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015