[JBoss JIRA] (TEIID-2608) Increase pg odbc client compatibility
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2608:
-------------------------------------
Summary: Increase pg odbc client compatibility
Key: TEIID-2608
URL: https://issues.jboss.org/browse/TEIID-2608
Project: Teiid
Issue Type: Quality Risk
Components: ODBC
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.5
Using a 9.0 level odbc client we see errors with the following:
set x TO y - since we don't expect TO
'foo'::regclass - which is shorthand for an oid lookup
pg_index.indpred - is used by some metadata queries
--
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, 4 months
[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:
---------------------------------------
Ramesh, what do you mean? I can reproduce the above exception if I use an empty jndi name. So it seems valid that we could perform a more intuitive validation - or allow the deployment to proceed (similar to a missing jndi) rather than this being seen as a hard error.
> 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, 4 months
[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:
-------------------------------------
Even the empty JNDI name is error is fixed on Teiid side, we should also log a JIRA on Designer side as to why it sent a blank JNDI name.
> 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, 4 months
[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:
---------------------------------------
The stacktrace shown is only reproducible with an empty jndi name. I was just trying to clarify what you meant by:
> but the server doesn't like it that there's no JNDI specified
As it does not seem reproducible if you fully remove the JNDI attribute.
> 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, 4 months
[JBoss JIRA] (TEIID-2602) Add clearer message that a VDB cannot be deployed without a JNDI name specified in the .vdb
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2602?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2602:
------------------------------------
I took an existing VDB and removed the JNDI name. I should have attached the vdb when I had the issue, but I can't find it now. If you can't reproduce in the case where the jndi name is not specified or an empty string, I would consider this closed.
> 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, 4 months
[JBoss JIRA] (TEIID-2568) Order by is omitted when projection is raised above ordering with grouping
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2568?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-2568:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=990301
> Order by is omitted when projection is raised above ordering with grouping
> --------------------------------------------------------------------------
>
> Key: TEIID-2568
> URL: https://issues.jboss.org/browse/TEIID-2568
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Environment: Windows and teiid 8.1
> Reporter: RAKESH BALGURI
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 8.4.1, 8.5
>
> Attachments: Query_Plan_SQL_1.txt, Query_Plan_SQL_2.txt
>
>
> I have a SQL which contain constants in the Select clause and also it contains Group By, Order By and Limit clauses in the SQL.
> When I execute the SQL, the Order By clause is not being pushed to the underlying translator. My translator doesn't support "SelectExpressions" i.e. supportsSelectExpression() returns false.
> When I remove the constant from the Select clause then the Order By is pushed to the translator.
>
> Is this a bug in Teiid's query Optimizer?
>
> The following are the sample queries and attached are the Query Plans for both the SQL's.
>
> Query1: This SQL doesn't push the Order By clause to the translator.
>
> SELECT B.RESCLASS, COUNT(*) AS GROUPING_COUNT, 'SECURITY.BASERULE' AS "__objecttype__" FROM
> SECURITY.BASERULE AS B GROUP BY B.RESCLASS ORDER BY B.RESCLASS DESC LIMIT 22
>
> Query2: This SQL pushes the Order By to the translator.
>
> SELECT B.RESCLASS, COUNT(*) AS GROUPING_COUNT FROM
> SECURITY.BASERULE AS B GROUP BY B.RESCLASS ORDER BY B.RESCLASS DESC LIMIT 22
--
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, 4 months
[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 resolved TEIID-2603.
-----------------------------------
Resolution: Done
Added support for long stat values using the existing integer field (for serialization compatibility) using a negative float encoding. The only downside is the loss of significant digits - but since this is an approximate value that doesn't seem like an issue. The only truly breaking change is from an api perspective with the TableStats and ColStats classes. The stat getter methods now return Number rather than Integer. However given that the usage of the classes should be limited that seems acceptable. Also proactively ported just the the breaking change to 8.4.1 for continuity from a product perspective.
> 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, 4 months