February 2019 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5425) Concurrency/timing issues observed with travis builds

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5425?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5425 at 2/22/19 3:25 PM: ---------------------------------------------------------------- After the basepom changes I have not observed the materialization related issue - disregard it's still occurring. was (Author: shawkins): After the basepom changes I have not observed the materialization related issue. > Concurrency/timing issues observed with travis builds > ----------------------------------------------------- > > Key: TEIID-5425 > URL: https://issues.jboss.org/browse/TEIID-5425 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Several unit tests have been observed to fail during travis builds occasionally: > 1. TestODBCSocketTransport.testRegClass:757 Â» PSQL ResultSet not positioned prope... > 2. TestExternalMatViews.testLazyUpdate:930 expected:<2> but was:<1> (see https://api.travis-ci.org/v3/job/405801976/log.txt) > 3. [ERROR] TestLocalConnections.testWaitForLoadTimeout:475 > 4. From https://api.travis-ci.org/v3/job/415138409/log.txt > [ERROR] testReplication(org.teiid.systemmodel.TestReplication) Time elapsed: 35.21 s <<< FAILURE! > java.lang.AssertionError: expected:<0.9164140964242746> but was:<0.18750528722359294> > at org.teiid.systemmodel.TestReplication.testReplication(TestReplication.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5582) xml format option is ignored by odata crossjoin

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5582?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5582: --------------------------------------- This affects both crossJoin and results produced by a function. I'm fine with resolving in EdmComplexResponse.getInstance with a check for xml format and throwing an exception. > xml format option is ignored by odata crossjoin > ----------------------------------------------- > > Key: TEIID-5582 > URL: https://issues.jboss.org/browse/TEIID-5582 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Since we have a custom serializer that is only implemented for json, the use of a format option is ignored for cross join queries. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5582) xml format option is ignored by odata crossjoin

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5582?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5582: ------------------------------------- IMO, the majority of users use JSON. There is been talk about removing the XML altogether from spec too, may not be worth the time unless someone explicitly asks. > xml format option is ignored by odata crossjoin > ----------------------------------------------- > > Key: TEIID-5582 > URL: https://issues.jboss.org/browse/TEIID-5582 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Since we have a custom serializer that is only implemented for json, the use of a format option is ignored for cross join queries. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5656) DDL based import statement incorrectly parses the foreign schema name

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5656?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5656: --------------------------------------- > What do you recommend here? Can we not use exact name as a pattern to match? No, you cannot interchange the two without risking weird scenarios involving the meta / escaping characters. So if we want to match a name exactly, we need to add support for that in the translator. Either as a post operation, or as the pattern - but with the appropriate escaping which needs to consult https://docs.oracle.com/javase/7/docs/api/java/sql/DatabaseMetaData.html#... > DDL based import statement incorrectly parses the foreign schema name > --------------------------------------------------------------------- > > Key: TEIID-5656 > URL: https://issues.jboss.org/browse/TEIID-5656 > Project: Teiid > Issue Type: Bug > Components: VDB > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.1 > > > The DDL import statement like > {code} > IMPORT FOREIGN SCHEMA public FROM SERVER sampledb INTO accounts OPTIONS("importer.useFullSchemaName" 'false'); > {code} > does not set the "importer.schemaPattern" to "public" instead it sets to "importer.schemaName" property to "public" in runtime thus invalidating its use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5656) DDL based import statement incorrectly parses the foreign schema name

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5656?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5656: ------------------------------------- What do you recommend here? Can we not use exact name as a pattern to match? > DDL based import statement incorrectly parses the foreign schema name > --------------------------------------------------------------------- > > Key: TEIID-5656 > URL: https://issues.jboss.org/browse/TEIID-5656 > Project: Teiid > Issue Type: Bug > Components: VDB > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.1 > > > The DDL import statement like > {code} > IMPORT FOREIGN SCHEMA public FROM SERVER sampledb INTO accounts OPTIONS("importer.useFullSchemaName" 'false'); > {code} > does not set the "importer.schemaPattern" to "public" instead it sets to "importer.schemaName" property to "public" in runtime thus invalidating its use. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5619) Provide tables representing admin information

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5619?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5619: ------------------------------------- +1, in general, we need to go towards removing the Admin API altogether for core Teiid IMO, but there may not much incentive in doing so. Maybe as you mention remove monitoring/management ones out and keep the configuration stuff in. > Provide tables representing admin information > --------------------------------------------- > > Key: TEIID-5619 > URL: https://issues.jboss.org/browse/TEIID-5619 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.1 > > > Information provided over the admin api about sessions, requests, transactions, etc. should also be available via system tables. > Similarly many of the admin operations could be provided as system procedures - kill session, flush cache, etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4051: ------------------------------------- I would like to close this as won't fix and focus on TEIIDSB-4 variants. > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4051) Swagger metadata includes internal java constructs

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-4051?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4051: -------------------------------- Fix Version/s: 12.2 (was: 12.1) > Swagger metadata includes internal java constructs > -------------------------------------------------- > > Key: TEIID-4051 > URL: https://issues.jboss.org/browse/TEIID-4051 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.12.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.2 > > > From IntegrationTestRestWarGeneration the swagger metadata includes definitions for Statement, ResultSet, StreamingOutput, etc.: > ... > InputStream: > type: "object" > Statement: > type: "object" > properties: > queryTimeout: > type: "integer" > format: "int32" > closed: > type: "boolean" > default: false > resultSet: > $ref: "#/definitions/ResultSet" > ... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5607) Update the jboss dockerfile to Teiid 12

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5607?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-5607. --------------------------------- Resolution: Done Updated to 12.0.0 with WF 14.0.1.Final > Update the jboss dockerfile to Teiid 12 > --------------------------------------- > > Key: TEIID-5607 > URL: https://issues.jboss.org/browse/TEIID-5607 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.1 > > > https://github.com/jboss-dockerfiles/teiid/blob/master/Dockerfile needs updated to latest. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5607) Update the jboss dockerfile to Teiid 12

by Ramesh Reddy (Jira)

[ https://issues.jboss.org/browse/TEIID-5607?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-5607: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Update the jboss dockerfile to Teiid 12 > --------------------------------------- > > Key: TEIID-5607 > URL: https://issues.jboss.org/browse/TEIID-5607 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Major > Fix For: 12.1 > > > https://github.com/jboss-dockerfiles/teiid/blob/master/Dockerfile needs updated to latest. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2019