August 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3658) VDBs may start before transport service

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3658: ------------------------------------- Summary: VDBs may start before transport service Key: TEIID-3658 URL: https://issues.jboss.org/browse/TEIID-3658 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.12 VDBs may start before transport services, which is an issue for ODBC access as the enabled flag on the vdbrepository is toggled in by the transport. Any vdbs loaded prior to that point will not be properly accessible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3657) make makedep and related hints consistent

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3657: ------------------------------------- Summary: make makedep and related hints consistent Key: TEIID-3657 URL: https://issues.jboss.org/browse/TEIID-3657 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 There are three places where hints can be specified, in the options clause, after an item, and before in a comment block. We should ensure that the comment block supports all options max/join for makedep, and that makeind should have the same options as makedep. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3656) Maven assembly plugin moduleSet includeDependencies set to true scope too large

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3656: ---------------------------------- Summary: Maven assembly plugin moduleSet includeDependencies set to true scope too large Key: TEIID-3656 URL: https://issues.jboss.org/browse/TEIID-3656 Project: Teiid Issue Type: Quality Risk Components: Build/Kits Affects Versions: 8.12 Reporter: Kylin Soong The assembly plugin moduleSet includeDependencies configuration under "build/assembly/jboss-as7/dist.xml": {code} <moduleSet> <includeSubModules>true</includeSubModules> <useAllReactorProjects>true</useAllReactorProjects> <includes> <include>org.jboss.teiid:teiid-jboss-integration</include> </includes> <binaries> <includeDependencies>true</includeDependencies> {code} the scope of this setting(includeDependencies is true,) is to large, it scope to all modules. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3655) Generated REST Service war do not allow any no-rest url

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3655?page=com.atlassian.jira.plugin... ] Kylin Soong reassigned TEIID-3655: ---------------------------------- Assignee: Kylin Soong (was: Steven Hawkins) > Generated REST Service war do not allow any no-rest url > ------------------------------------------------------- > > Key: TEIID-3655 > URL: https://issues.jboss.org/browse/TEIID-3655 > Project: Teiid > Issue Type: Quality Risk > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Kylin Soong > Priority: Blocker > Fix For: 8.12 > > Attachments: Screenshot.png > > > Generated REST Service war have the following configuration in web.xml > {code} > <servlet-mapping> > <servlet-name>RestDataservice</servlet-name> > <url-pattern>/*</url-pattern> > </servlet-mapping> > {code} > This means all request be thought as rest request. As attached screen, all shot, > {code} > http://localhost:8080/sample_1/swagger/css/typography.css > http://localhost:8080/sample_1/swagger/lib/jquery-1.8.0.min.js > http://localhost:8080/sample_1/swagger/lib/highlight.7.3.pack.js > {code} > be thought as rest request, but no relevant api define, 404 returned. > Current design is for guarantee the rest api path like > {code} > /{vdbName_vdbVersion}/{modelName}/{procedureName}/{path} > {code} > for example > {code} > http://localhost:8080/sample_1/view/g1/1 > {code} > But, I do wonder we really need to treat all are rest request? For example, if we request http://localhost:8080/sample_1, a rude 404 page with stacktrace return, we may consider and a customized 404 page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3655) Generated REST Service war do not allow any no-rest url

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3655?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3655: ------------------------------------ For integrating swagger UI provide a api-doc in TEIID-3521, I add one html page and some js/css file: {code} sample_1.war WEB-INF web.xml swagger swagger-ui.js *.css api.html {code} As attached Schreenshot, all js/css/png/html be thought as rest request, 404 return, js not work. > Generated REST Service war do not allow any no-rest url > ------------------------------------------------------- > > Key: TEIID-3655 > URL: https://issues.jboss.org/browse/TEIID-3655 > Project: Teiid > Issue Type: Quality Risk > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.12 > > Attachments: Screenshot.png > > > Generated REST Service war have the following configuration in web.xml > {code} > <servlet-mapping> > <servlet-name>RestDataservice</servlet-name> > <url-pattern>/*</url-pattern> > </servlet-mapping> > {code} > This means all request be thought as rest request. As attached screen, all shot, > {code} > http://localhost:8080/sample_1/swagger/css/typography.css > http://localhost:8080/sample_1/swagger/lib/jquery-1.8.0.min.js > http://localhost:8080/sample_1/swagger/lib/highlight.7.3.pack.js > {code} > be thought as rest request, but no relevant api define, 404 returned. > Current design is for guarantee the rest api path like > {code} > /{vdbName_vdbVersion}/{modelName}/{procedureName}/{path} > {code} > for example > {code} > http://localhost:8080/sample_1/view/g1/1 > {code} > But, I do wonder we really need to treat all are rest request? For example, if we request http://localhost:8080/sample_1, a rude 404 page with stacktrace return, we may consider and a customized 404 page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3655) Generated REST Service war do not allow any no-rest url

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3655?page=com.atlassian.jira.plugin... ] Kylin Soong updated TEIID-3655: ------------------------------- Attachment: Screenshot.png > Generated REST Service war do not allow any no-rest url > ------------------------------------------------------- > > Key: TEIID-3655 > URL: https://issues.jboss.org/browse/TEIID-3655 > Project: Teiid > Issue Type: Quality Risk > Affects Versions: 8.12 > Reporter: Kylin Soong > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.12 > > Attachments: Screenshot.png > > > Generated REST Service war have the following configuration in web.xml > {code} > <servlet-mapping> > <servlet-name>RestDataservice</servlet-name> > <url-pattern>/*</url-pattern> > </servlet-mapping> > {code} > This means all request be thought as rest request. As attached screen, all shot, > {code} > http://localhost:8080/sample_1/swagger/css/typography.css > http://localhost:8080/sample_1/swagger/lib/jquery-1.8.0.min.js > http://localhost:8080/sample_1/swagger/lib/highlight.7.3.pack.js > {code} > be thought as rest request, but no relevant api define, 404 returned. > Current design is for guarantee the rest api path like > {code} > /{vdbName_vdbVersion}/{modelName}/{procedureName}/{path} > {code} > for example > {code} > http://localhost:8080/sample_1/view/g1/1 > {code} > But, I do wonder we really need to treat all are rest request? For example, if we request http://localhost:8080/sample_1, a rude 404 page with stacktrace return, we may consider and a customized 404 page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3655) Generated REST Service war do not allow any no-rest url

by Kylin Soong (JIRA)

Kylin Soong created TEIID-3655: ---------------------------------- Summary: Generated REST Service war do not allow any no-rest url Key: TEIID-3655 URL: https://issues.jboss.org/browse/TEIID-3655 Project: Teiid Issue Type: Quality Risk Affects Versions: 8.12 Reporter: Kylin Soong Assignee: Steven Hawkins Priority: Blocker Fix For: 8.12 Generated REST Service war have the following configuration in web.xml {code} <servlet-mapping> <servlet-name>RestDataservice</servlet-name> <url-pattern>/*</url-pattern> </servlet-mapping> {code} This means all request be thought as rest request. As attached screen, all shot, {code} http://localhost:8080/sample_1/swagger/css/typography.css http://localhost:8080/sample_1/swagger/lib/jquery-1.8.0.min.js http://localhost:8080/sample_1/swagger/lib/highlight.7.3.pack.js {code} be thought as rest request, but no relevant api define, 404 returned. Current design is for guarantee the rest api path like {code} /{vdbName_vdbVersion}/{modelName}/{procedureName}/{path} {code} for example {code} http://localhost:8080/sample_1/view/g1/1 {code} But, I do wonder we really need to treat all are rest request? For example, if we request http://localhost:8080/sample_1, a rude 404 page with stacktrace return, we may consider and a customized 404 page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3628) Server socket setting issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3628?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3628: ---------------------------------- Fix Version/s: 8.11.3 > Server socket setting issues > ---------------------------- > > Key: TEIID-3628 > URL: https://issues.jboss.org/browse/TEIID-3628 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3 > > > The bootstrap settings need to be for the child rather than the parent. Also we should enable tcpNoDelay so that small messages are immediately sent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3645) Upgrade of Amazon aws sdk version

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3645?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3645: ---------------------------------- Fix Version/s: 8.11.3 > Upgrade of Amazon aws sdk version > --------------------------------- > > Key: TEIID-3645 > URL: https://issues.jboss.org/browse/TEIID-3645 > Project: Teiid > Issue Type: Component Upgrade > Components: Misc. Connectors > Affects Versions: 8.11.2 > Environment: teiid 8.11.2 > windows 8.1 > java 8 > Reporter: avinash misra > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3 > > > I was working on dynamodb connector with latest dynamodb sdk. > This sdk uses aws-java-sdk-core version 1.10.11 but teiid uses aws-java-sdk 1.5.7. internally for simple db connector. > Could you please upgrade the aws sdk version to latest? > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3654) Exception with system table subquery

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3654?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3654. ----------------------------------- Resolution: Done This doesn't affect all subquery situations, just ones in which the parent projection was pushed, it's a join child, and there's no intervening select node. Corrected by adding a NO_PROJECTION capability to indicate that the system source performs no projection. > Exception with system table subquery > ------------------------------------ > > Key: TEIID-3654 > URL: https://issues.jboss.org/browse/TEIID-3654 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > Issuing a subquery against a system table such as: > SELECT t.Name FROM SYS.Tables as t, (SELECT DISTINCT c.TableName FROM SYS.Columns AS c) AS X__1 WHERE t.Name = X__1.TableName > Results in the exception: TEIID30328 Unable to evaluate X__2.TableName: No value was available > This is due to the project not being pushed and the project columns not being updated appropriately. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 August 2015