November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3788) Enable setting on JDG translator for controlling timezone setting for Date and Timestamp columns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3788?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3788. ----------------------------------- Fix Version/s: (was: 8.12.x) Resolution: Incomplete Description The same line of reasoning applies here as with TEIID-3789 - all source dates are effectively UTC which means that it's expected that they will display differently if the teiid server timezone changes. > Enable setting on JDG translator for controlling timezone setting for Date and Timestamp columns > ------------------------------------------------------------------------------------------------ > > Key: TEIID-3788 > URL: https://issues.jboss.org/browse/TEIID-3788 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > > Timezone of DV server has influence on Date and Timestamp columns in some data sources -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3763) WS connector oauth security setting not work in Embedded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3763?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3763: ---------------------------------- Fix Version/s: 8.13 8.12.1 (was: 8.12.x) > WS connector oauth security setting not work in Embedded > -------------------------------------------------------- > > Key: TEIID-3763 > URL: https://issues.jboss.org/browse/TEIID-3763 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.12.1, 8.13 > > Attachments: jca-ra-outbound.png > > > In WSConnectionImpl setDispatchProperties setting depend on Security Subject: > {code} > else if (this.mcf.getAsSecurityType() == WSManagedConnectionFactory.SecurityType.OAuth) { > Subject subject = ConnectionContext.getSubject(); > if (subject != null) { > } > ... > } > {code} > Note if run WS connector with security in Embedded, ConnectionContext.getSubject() return null, the cause exception throw. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3827) multi-source view insert throwing TEIID30492 error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3827?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3827: ---------------------------------- Component/s: Query Engine Fix Version/s: 8.13 8.12.3 > multi-source view insert throwing TEIID30492 error > -------------------------------------------------- > > Key: TEIID-3827 > URL: https://issues.jboss.org/browse/TEIID-3827 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.3 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > MySQL 5.7 and Postgres 9.4 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.3 > > Attachments: joined_vdb.vdb > > > I'm trying to POC this multi-source INSERT. I have a MySQL DB and Postgres DB on my local machine. Added the drivers, datasource, and created a VBL with 1:1 mapping to my test tables. I created an EBL that is a join of my two tables. Both VBLs and EBL are set to support updates. I'm trying to work through this error. > {quote} > insert into "Joined_EBL"."joined2"(idtestm, randomstring, idtestp, randomint) values(0, 'randomstring', 0, 12345) > org.teiid.runtime.client.TeiidClientException: org.teiid.api.exception.query.QueryValidatorException: Remote TEIID30492 A multi-source table, Joined_EBL.joined2, cannot be used in an INSERT with query expression or SELECT INTO statement. > {quote} > I updated my INSERT tab on the EBL transformation page with the following. > {code}FOR EACH ROW > BEGIN ATOMIC > INSERT INTO Postgres_VBL.testp (Postgres_VBL.testp.idtestp, Postgres_VBL.testp.randomint) VALUES (0, "NEW".randomint); > INSERT INTO MySQL_VBL.testm (MySQL_VBL.testm.idtestm, MySQL_VBL.testm.randomstring) VALUES (0, "NEW".randomstring); > END > {code} > Postgres table > {code} > CREATE TABLE testp > ( > idtestp integer NOT NULL, > randomint integer, > CONSTRAINT pk_id PRIMARY KEY (idtestp) > ) > WITH ( > OIDS=FALSE > ); > ALTER TABLE testp > OWNER TO postgres; > {code} > MySQL table > {code} > CREATE TABLE `testm` ( > `idtestm` int(11) NOT NULL AUTO_INCREMENT, > `randomstring` varchar(45) DEFAULT NULL, > PRIMARY KEY (`idtestm`), > UNIQUE KEY `idtestm_UNIQUE` (`idtestm`) > ) ENGINE=InnoDB DEFAULT CHARSET=tis620; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3827) multi-source view insert throwing TEIID30492 error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3827?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3827. ----------------------------------- Resolution: Done There were still changes I wanted to make for this before resolving. I updated the server to ignore the multi-source property on view models and updated the validation message to cover the all the validation cases as we were only referencing select into / insert with query expression. > multi-source view insert throwing TEIID30492 error > -------------------------------------------------- > > Key: TEIID-3827 > URL: https://issues.jboss.org/browse/TEIID-3827 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.3 > Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version 6.4.3, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > MySQL 5.7 and Postgres 9.4 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.3 > > Attachments: joined_vdb.vdb > > > I'm trying to POC this multi-source INSERT. I have a MySQL DB and Postgres DB on my local machine. Added the drivers, datasource, and created a VBL with 1:1 mapping to my test tables. I created an EBL that is a join of my two tables. Both VBLs and EBL are set to support updates. I'm trying to work through this error. > {quote} > insert into "Joined_EBL"."joined2"(idtestm, randomstring, idtestp, randomint) values(0, 'randomstring', 0, 12345) > org.teiid.runtime.client.TeiidClientException: org.teiid.api.exception.query.QueryValidatorException: Remote TEIID30492 A multi-source table, Joined_EBL.joined2, cannot be used in an INSERT with query expression or SELECT INTO statement. > {quote} > I updated my INSERT tab on the EBL transformation page with the following. > {code}FOR EACH ROW > BEGIN ATOMIC > INSERT INTO Postgres_VBL.testp (Postgres_VBL.testp.idtestp, Postgres_VBL.testp.randomint) VALUES (0, "NEW".randomint); > INSERT INTO MySQL_VBL.testm (MySQL_VBL.testm.idtestm, MySQL_VBL.testm.randomstring) VALUES (0, "NEW".randomstring); > END > {code} > Postgres table > {code} > CREATE TABLE testp > ( > idtestp integer NOT NULL, > randomint integer, > CONSTRAINT pk_id PRIMARY KEY (idtestp) > ) > WITH ( > OIDS=FALSE > ); > ALTER TABLE testp > OWNER TO postgres; > {code} > MySQL table > {code} > CREATE TABLE `testm` ( > `idtestm` int(11) NOT NULL AUTO_INCREMENT, > `randomstring` varchar(45) DEFAULT NULL, > PRIMARY KEY (`idtestm`), > UNIQUE KEY `idtestm_UNIQUE` (`idtestm`) > ) ENGINE=InnoDB DEFAULT CHARSET=tis620; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3828) Build failed due to artifact 'org.jboss.oreva:odata-core:jar:0.8.11-SNAPSHOT' can not be resolved

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3828?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3828: -------------------------------- Parent: TEIID-3519 Issue Type: Sub-task (was: Bug) > Build failed due to artifact 'org.jboss.oreva:odata-core:jar:0.8.11-SNAPSHOT' can not be resolved > ------------------------------------------------------------------------------------------------- > > Key: TEIID-3828 > URL: https://issues.jboss.org/browse/TEIID-3828 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.13 > Reporter: Kylin Soong > Assignee: Ramesh Reddy > Fix For: 8.13 > > > translator-odata use a SNAPSHOT dependency > {code} > <dependency> > <groupId>org.jboss.oreva</groupId> > <artifactId>odata-core</artifactId> > </dependency> > {code} > which can not be resolved, with the folllowing erros: > {code} > [ERROR] Failed to execute goal on project translator-odata: Could not resolve dependencies for project org.jboss.teiid.connectors:translator-odata:bundle:8.13.0.Alpha1-SNAPSHOT: The following artifacts could not be resolved: org.jboss.oreva:odata-core:jar:0.8.11-SNAPSHOT, org.jboss.oreva:common:jar:0.8.11-SNAPSHOT: Failure to find org.jboss.oreva:odata-core:jar:0.8.11-SNAPSHOT in ... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3829) olingo module junit test failed

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3829?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3829: -------------------------------- Parent: TEIID-3519 Issue Type: Sub-task (was: Bug) > olingo module junit test failed > ------------------------------- > > Key: TEIID-3829 > URL: https://issues.jboss.org/browse/TEIID-3829 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.13 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Fix For: 8.13 > > > olingo module junit test failed: > {code} > Results : > Failed tests: > TestODataSQLBuilder.testEq:431->te:400->helpTest:227 expected:<...g0 WHERE g0.e1 = {t'[04]:20:02'} ORDER BY g0...> but was:<...g0 WHERE g0.e1 = {t'[16]:20:02'} ORDER BY g0...> > TestODataSQLBuilder.testTimeMethods:552->te:400->helpTest:227 expected:<...YEAR({ts'2008-10-13 [04]:20:02.0'}) = 2008 O...> but was:<...YEAR({ts'2008-10-13 [16]:20:02.0'}) = 2008 O...> > Tests run: 109, Failures: 2, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3830) Install script executed failed due to threads subsystem be removed

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3830?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3830: -------------------------------- Parent: TEIID-3519 Issue Type: Sub-task (was: Bug) > Install script executed failed due to threads subsystem be removed > ------------------------------------------------------------------ > > Key: TEIID-3830 > URL: https://issues.jboss.org/browse/TEIID-3830 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.13 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.13 > > > According to WFLY-462, the central thread pool configuration(threads subsystem) already be removed since 9.0.0.CR2, these two scripts: > * teiid-standalone-mode-install.cli > * teiid-domain-mode-install.cli > be affected, specifically the following lines cli can not executed: > {code} > /subsystem=threads/unbounded-queue-thread-pool=teiid-async:add(max-threads=4) > /subsystem=teiid:add(async-thread-pool=teiid-async, resultset-cache-infinispan-container=teiid-cache, preparedplan-cache-infinispan-container=teiid-cache, policy-decider-module=org.jboss.teiid) > {code} > The corresponding error looks > {code} > Failed to get the list of the operation properties: "WFLYCTL0030: No resource definition is registered for address [ > ("subsystem" => "threads"), > ("unbounded-queue-thread-pool" => "teiid-async") > ]" > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3462) Add support for semantic versioning of VDBs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3462: --------------------------------------- I should add there is no support for a qualifier and the odata urls must fully specify the version if using the semantic version. > Add support for semantic versioning of VDBs > ------------------------------------------- > > Key: TEIID-3462 > URL: https://issues.jboss.org/browse/TEIID-3462 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.0 > > > Semantic versioning [1] should be supported in the VDB versioning in order to be able to easier determine whether there are breaking changes from the client perspective and to more easily establish a link between client software versions and the VDBs they rely upon. > [1] http://semver.org/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3462) Add support for semantic versioning of VDBs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3462: --------------------------------------- The initial commits are in that implement the approach above. If it seems acceptable, then I'd like to proceed to deprecate the old version mechanism. > Add support for semantic versioning of VDBs > ------------------------------------------- > > Key: TEIID-3462 > URL: https://issues.jboss.org/browse/TEIID-3462 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.0 > > > Semantic versioning [1] should be supported in the VDB versioning in order to be able to easier determine whether there are breaking changes from the client perspective and to more easily establish a link between client software versions and the VDBs they rely upon. > [1] http://semver.org/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3627) Infinispan-dsl-cache translator: comparison operators(GE, LE) problem with string

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3627?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3627: ------------------------------------------------ Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1254053|https://bugzilla.redhat.com/show_bug.cgi?id=1254053] from MODIFIED to ON_QA > Infinispan-dsl-cache translator: comparison operators(GE,LE) problem with string > -------------------------------------------------------------------------------- > > Key: TEIID-3627 > URL: https://issues.jboss.org/browse/TEIID-3627 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Van Halbert > Fix For: 8.7.1.6_2, 8.12 > > > Comparison of string values provides wrong results for GE and LE operators. I provide example queries, notice the number of rows returned by the queries. > For query: {code:sql}SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA WHERE BQT1.SmallA.StringNum <= -22 ORDER BY StringNum{code} > * Process Tree: > {code:plain} > LimitNode(0) output=[g_0.stringNum] limit 100 > AccessNode(1) output=[g_0.stringNum] SELECT g_0.stringNum FROM SmallAs.smallARemotecache AS g_0 WHERE g_0.stringNum <= '-22' ORDER BY g_0.stringNum > {code} > * SRC CMD: {code:sql}SELECT g_0.stringNum FROM SmallAs.smallARemotecache AS g_0 WHERE g_0.stringNum <= '-22' ORDER BY g_0.stringNum{code} > * result 0 rows > But for query: {code:sql}SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA WHERE BQT1.SmallA.StringNum < -22 ORDER BY StringNum{code} > * Process Tree: > {code:plain}ProjectNode(0) output=[c.stringNum AS StringNum] [c.stringNum AS StringNum] > LimitNode(1) output=[c.stringNum] limit 100 > SortNode(2) output=[c.stringNum] [SORT] [c.stringNum] > SelectNode(3) output=[c.stringNum] c.stringNum < '-22' > AccessNode(4) output=[c.stringNum] SELECT g_0.stringNum FROM SmallAs.smallARemotecache AS g_0{code} > * SRC CMD: {code:sql}SELECT g_0.stringNum FROM SmallAs.smallARemotecache AS g_0{code} > * result 14 rows > And query: {code:sql}SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA WHERE BQT1.SmallA.StringNum = -22 ORDER BY StringNum{code} > * Process Tree: > {code:plain}LimitNode(0) output=[c.stringNum AS StringNum] limit 100 > AccessNode(1) output=[c.stringNum AS StringNum] SELECT g_0.stringNum FROM SmallAs.smallARemotecache AS g_0 WHERE g_0.stringNum = '-22' ORDER BY g_0.stringNum{code} > * SRC CMD: {code:sql}SELECT g_0.stringNum FROM SmallAs.smallARemotecache AS g_0 WHERE g_0.stringNum = '-22' ORDER BY g_0.stringNum{code} > * result 1 row > The first query should then return 15 rows instead of 0. Also the queries differ in a way they are processed, the first one is pushed down to infinispan, the other two are processed by teiid, which is probably a regression originally tracked here: TEIID-3424 > The same cause introduces problems with similar queries: > {code:sql}Select IntKey, StringKey From BQT1.SmallA WHERE NOT(StringKey > 10 AND IntKey < 47) ORDER BY IntKey{code} > Which is processed as: > * Process Tree: > {code:plain}LimitNode(0) output=[c.intKey AS IntKey, c.stringKey AS StringKey] limit 100 > AccessNode(1) output=[c.intKey AS IntKey, c.stringKey AS StringKey] SELECT g_0.intKey, g_0.stringKey FROM SmallAs.smallARemotecache AS g_0 WHERE (g_0.stringKey <= '10') OR (g_0.intKey >= 47) ORDER BY g_0.intKey{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015