August 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3660) Add support for unnesting anti semijoins

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3660: ------------------------------------- Summary: Add support for unnesting anti semijoins Key: TEIID-3660 URL: https://issues.jboss.org/browse/TEIID-3660 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 Currently we won't perform the rewrite if it's the anit case. A subquery used as an anti semijoin can be unnested into a left outer join with a filter on the null rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3659) subquery unnesting missed

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3659: ------------------------------------- Summary: subquery unnesting missed Key: TEIID-3659 URL: https://issues.jboss.org/browse/TEIID-3659 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 A query such as: select b.SYMBOL from PRODUCT b where exists (select 1 from PRICES d where d.SYMBOL=b.SYMBOL) where there is no key between the symbol columns will not unnested when it should be eligible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3658: --------------------------------------- It has to be that way. From what I can see even the TransportAdd happens in parallel the VDBRepositoryService start, so there's no guarantee that a vdb won't start prior to the transport being added. Should I go ahead and make the change? > 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-3658) VDBs may start before transport service

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3658: ------------------------------------- I vote for #2 > 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-3658) VDBs may start before transport service

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3658: --------------------------------------- > It depends on VDB repository service, but not on VDB Service. A VDB Service represents a individual VDB. Either case that would be bad dependency to add. Sorry I was mixing up vdb service and vdbrepository service. As for adding the transports as dependencies to a vdb service that is something that seems more like a feature than a bug fix - as we could then also restrict the access of the vdb to only a subset of transports. > I think we should consider removing this restriction, this is system metadata, just in different form, can't think of good reason why we should not include all the time, considering our pg transport will give us access to various other clients. It's just continuity for those who have never enabled odbc access - then this metadata will not show up anywhere. As it could in theory cause an unintended issue for someone that previous did not have odbc access enabled and has a pg source that exposes pg system tables. Now user queries would need qualification where none was needed before. It seems like we can: 1. add a listener to the vdbrepository service based TranportAdd 2. or make the odbc metadata enabled configuration part of the teiid subsystem and default to true, so that we would preserve the option to disable it > 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-3658) VDBs may start before transport service

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3658: ------------------------------------- >Would that be circular? The transports currently depend on the vdbservice. It depends on VDB repository service, but not on VDB Service. A VDB Service represents a individual VDB. Either case that would be bad dependency to add. >If the odbc enabled flag is not set, the the odbc metadata catalog is not added to the vdb. Thus odbc clients will see exceptions when attempting to get metadata. I think we should consider removing this restriction, this is system metadata, just in different form, can't think of good reason why we should not include all the time, considering our pg transport will give us access to various other clients. > 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-3658) VDBs may start before transport service

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3658: --------------------------------------- > you can make the vdb service dependent on transport, but there more than single transport Would that be circular? The transports currently depend on the vdbservice. A thought would be that we need a listener on the vdbrepository startup based upon TransportAdd, rather than waiting for the transportservice to start. > I am not sure I understand ODBC access issue, can you explain? If the odbc enabled flag is not set, the the odbc metadata catalog is not added to the vdb. Thus odbc clients will see exceptions when attempting to get metadata. > 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-3656) Maven assembly plugin moduleSet includeDependencies set to true scope too large

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3656?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3656: ------------------------------------- It will only include the dependencies that are defined as not "provided". What is the issue you are seeing? > 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 Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3655?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3655: ------------------------------------- see http://stackoverflow.com/questions/18693446/how-to-make-resteasy-understa... to enable static content. > 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-3658) VDBs may start before transport service

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3658: ------------------------------------- Since the startup is async process this is will be hard to control, you can make the vdb service dependent on transport, but there more than single transport. IMO we need to remove this dependency you mention. I am not sure I understand ODBC access issue, can you explain? > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2015