October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3360) Provide an option to virtualize source exceptions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3360?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3360: ---------------------------------- Fix Version/s: 9.0 (was: 8.12) > Provide an option to virtualize source exceptions > ------------------------------------------------- > > Key: TEIID-3360 > URL: https://issues.jboss.org/browse/TEIID-3360 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > Currently we'll pass the source exception along with the Teiid exception. And from source sql exceptions we'll also rely the sql state/code. When connecting to databases of different types it would be best to return a common set of codes. > There is exception mapping logic in Hibernate that we could reuse, but this could apply to the non-jdbc sources such that a predictable code will seen by Teiid clients. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3039) Add support for odata expand

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3039?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3039: ---------------------------------- Fix Version/s: 9.0 (was: 8.12) > Add support for odata expand > ---------------------------- > > Key: TEIID-3039 > URL: https://issues.jboss.org/browse/TEIID-3039 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Fix For: 9.0 > > > We should add support for odata expand. This can be done with logic similar to the xml document model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3347) Most subplans do not show node stats

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3347?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3347: ---------------------------------- Fix Version/s: 9.0 (was: 8.12) > Most subplans do not show node stats > ------------------------------------ > > Key: TEIID-3347 > URL: https://issues.jboss.org/browse/TEIID-3347 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > When looking at the node stats, only the direct nodes of the current plan have stats. Subqueries, which are executed off of a cloned plan, do not have stats. > There isn't an easy solution for this with the current design. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3511) usage of BITAND function in exists statement results in duplicate rows

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3511?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3511: ---------------------------------- Fix Version/s: (was: 8.12) There's been no progress here. Pulling out of a specific release. > usage of BITAND function in exists statement results in duplicate rows > ---------------------------------------------------------------------- > > Key: TEIID-3511 > URL: https://issues.jboss.org/browse/TEIID-3511 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.9.1 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: debugplan_bitand.txt, debugplan_bitand_correct.txt, debugplan_nobitand.txt, debugplan_nobitand_correct.txt > > > I've added the debug plan for the query without the BITAND function and with the BITAND function as an attachment. > The version without the BITAND function returns 438 rows and the version with BITAND function returns 833 rows. I can see however that rows are duplicated in this second result. I've checked this by executing the version with BITAND statement with select *. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3747: --------------------------------------- > I think we need to stop building the .VDB from Designer and just support Dynamic VDBS. Need to put in deprecation notice starting from DV 6.3. Just to clarify, that is essentially unrelated to this issue. What Van is mentioning won't trigger this issue unless there is a collision with the vdb name/version and different deployment names - and as Ramesh says that irrespective of the artifact type. Also there are the caveats that we don't yet have a ddl based replacement for xml document models nor enterprise types. > Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates > --------------------------------------------------------------------------------------- > > Key: TEIID-3747 > URL: https://issues.jboss.org/browse/TEIID-3747 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml > then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service: > 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3747: ------------------------------------- I think we need to stop building the .VDB from Designer and just support Dynamic VDBS. Need to put in deprecation notice starting from DV 6.3. Note also that, a Dynamic VDB can also be in ".vdb" format (i.e DDL based files in a ZIP file), that will have same issues as the above, as it is irrespective of the VDB type, more to do with the deployment name and VDB name. > Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates > --------------------------------------------------------------------------------------- > > Key: TEIID-3747 > URL: https://issues.jboss.org/browse/TEIID-3747 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml > then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service: > 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3747: ------------------------------------ I can see this issue coming up more as we're introducing modeling of both the dynamic VDB and the .vdb in designer. Mixing of the the 2 artifact types when using the same named VDB could definitely happen. > Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates > --------------------------------------------------------------------------------------- > > Key: TEIID-3747 > URL: https://issues.jboss.org/browse/TEIID-3747 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml > then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service: > 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3747) Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3747?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3747: --------------------------------------- > The only thing we can do in Teiid is check the current repository of deployed VDBs, then gracefully reject the deployment rather than the error you seen above. I agree. This is an ambiguous deployment scenario and it should be made clear that they are trying to create a differently named deployment with the same vdb name/version as an existing deployment. > Deploying a .vdb where a dynamic vdb has already been deployed, fails due to duplicates > --------------------------------------------------------------------------------------- > > Key: TEIID-3747 > URL: https://issues.jboss.org/browse/TEIID-3747 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > deployed a dynamic vdb using CLI: deploy teiidfiles/vdb/portfolio-vdb.xml > then in Designer, tried to deploy the same named VDB, but as a .vdb and the deployment fails with errors indicating duplicate service: > 11:26:31,301 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."Portfolio.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Portfolio.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Portfolio.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55] > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.teiid.ds-listener.Portfolio.1./accounts-ds is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3556) BufferManager reserve memory variable is decremented twice

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3556?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3556. --------------------------------- > BufferManager reserve memory variable is decremented twice > ---------------------------------------------------------- > > Key: TEIID-3556 > URL: https://issues.jboss.org/browse/TEIID-3556 > Project: Teiid > Issue Type: Bug > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1.6_2, 8.12, 8.11.1 > > > Web admin console shows negative value for Memory Used By Active Plans(KB) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3506) Move downloads off of sourceforge

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3506?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3506. --------------------------------- > Move downloads off of sourceforge > --------------------------------- > > Key: TEIID-3506 > URL: https://issues.jboss.org/browse/TEIID-3506 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > We need to move our downloads off of sourceforge onto an infrastructure we have more control over. This can be as simple as just pointing to the maven artifacts (which means that the server uber dist needs added) or we can start using the jboss.org download site. > More than likely we'll leave the old downloads in place. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015