July 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2500) Rewrite of case with true condition is not correct

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2500?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2500: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=989747 > Rewrite of case with true condition is not correct > -------------------------------------------------- > > Key: TEIID-2500 > URL: https://issues.jboss.org/browse/TEIID-2500 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4 > > > If a secondary searched case condition is always true, then the case will be inappropriately rewritten as just the then expression: > case when ... when true then x else y end > becomes just > x > However the prior cases should still be considered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2591) Incorrect values returned from system table on dependent side of join

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2591?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2591: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=989746 > Incorrect values returned from system table on dependent side of join > --------------------------------------------------------------------- > > Key: TEIID-2591 > URL: https://issues.jboss.org/browse/TEIID-2591 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5 > > > If a system table is marked as the dependent side of a join (should be rarely planned, but can be forced with a makedep) the system table access is not corrected for the projection and may return values that are not matched to the columns requested. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2598) 7.4 compatibility

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2598?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2598. ----------------------------------- Resolution: Done Marking as resolved as internal testing has passed. > 7.4 compatibility > ----------------- > > Key: TEIID-2598 > URL: https://issues.jboss.org/browse/TEIID-2598 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 7.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > Exception result messages from a 7.4 and prior server are not handled correctly by 7.5+ clients and cause the connection to be dropped since the client assumes that it is not compatible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2598) 7.4 compatibility

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2598?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2598: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=989744 > 7.4 compatibility > ----------------- > > Key: TEIID-2598 > URL: https://issues.jboss.org/browse/TEIID-2598 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Affects Versions: 7.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > Exception result messages from a 7.4 and prior server are not handled correctly by 7.5+ clients and cause the connection to be dropped since the client assumes that it is not compatible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2604) ODBC string error response message is incorrect

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2604: ------------------------------------- Summary: ODBC string error response message is incorrect Key: TEIID-2604 URL: https://issues.jboss.org/browse/TEIID-2604 Project: Teiid Issue Type: Enhancement Components: ODBC Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.4.1, 8.5 The null termination character is missing from the error response message options. This is typically only thrown for internal/protocol errors. Clients may not behave as expected to this response. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2603) Support larger statistic values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2603?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2603: --------------------------------------- One possible approach that would even maintain backward serialized compatibility without too much head ache would be to use negative int values to indicate float values. There would be a loss of precision, but the range would be much greater. Otherwise we'd have to look at using longs. Either way surrounding logic needs to be changed appropriately. > Support larger statistic values > ------------------------------- > > Key: TEIID-2603 > URL: https://issues.jboss.org/browse/TEIID-2603 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > The table/column stats are currently limited to max int (2^31 -1) values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2603) Support larger statistic values

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2603: ------------------------------------- Summary: Support larger statistic values Key: TEIID-2603 URL: https://issues.jboss.org/browse/TEIID-2603 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.5 The table/column stats are currently limited to max int (2^31 -1) values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2597) Allow Salesforce COnnection timeouts to be easily adjusted

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2597?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2597: --------------------------------------- I went ahead and pulled 8.4.x forward. I also expect 8.5 Beta1 to be available by Wednesday. > Allow Salesforce COnnection timeouts to be easily adjusted > ---------------------------------------------------------- > > Key: TEIID-2597 > URL: https://issues.jboss.org/browse/TEIID-2597 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.4 > Reporter: Graeme Gillies > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > Currently it is possible via an easy configuration option to set the http and other time-outs of ws connections. Can a similar option be made available to salesforce connections, so timeouts can be changed easily without a custom cxf setup > Thanks, > Graeme -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2602) Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2602?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2602: --------------------------------------- Yes, that is what I believe he's talking about as well. I just want to make sure he clarifies what he means by "no JNDI specified" and "the server doesn't like". > Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb > ------------------------------------------------------------------------------------------- > > Key: TEIID-2602 > URL: https://issues.jboss.org/browse/TEIID-2602 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > Created a sample VDB in designer, for which the model is to use the loopback connector. Did not specify a JNDI reference, because it doesn't need one. However, the VDB can't be deployed from Designer because there's no connection info for this model. So I hand deployed, but the server doesn't like it that there's no JNDI specified (if I add the JNDI reference, it deploys fine). You get this error: > 08:10:17,265 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."Sample.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Sample.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Sample.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for java > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186) > at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:300) > at org.teiid.jboss.VDBDeployer.addDataSourceListener(VDBDeployer.java:245) > at org.teiid.jboss.VDBDeployer.dataSourceDependencies(VDBDeployer.java:267) > at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:153) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > ... 5 more > Can Teiid preempt this and produce a clearer message that its because there's no JNDI specified? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2602) Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2602?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2602: ------------------------------------- I believe the VDB may have defined like {code} <source name="local" translator-name="loopback" connection-jndi-name=""/> {code} > Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb > ------------------------------------------------------------------------------------------- > > Key: TEIID-2602 > URL: https://issues.jboss.org/browse/TEIID-2602 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > Created a sample VDB in designer, for which the model is to use the loopback connector. Did not specify a JNDI reference, because it doesn't need one. However, the VDB can't be deployed from Designer because there's no connection info for this model. So I hand deployed, but the server doesn't like it that there's no JNDI specified (if I add the JNDI reference, it deploys fine). You get this error: > 08:10:17,265 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."Sample.vdb".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."Sample.vdb".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "Sample.vdb" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for java > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186) > at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:300) > at org.teiid.jboss.VDBDeployer.addDataSourceListener(VDBDeployer.java:245) > at org.teiid.jboss.VDBDeployer.dataSourceDependencies(VDBDeployer.java:267) > at org.teiid.jboss.VDBDeployer.deploy(VDBDeployer.java:153) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > ... 5 more > Can Teiid preempt this and produce a clearer message that its because there's no JNDI specified? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2013