[JBoss JIRA] Created: (TEIID-1545) Order By not pushed down
by Mark Addleman (JIRA)
Order By not pushed down
------------------------
Key: TEIID-1545
URL: https://issues.jboss.org/browse/TEIID-1545
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Reporter: Mark Addleman
Assignee: Steven Hawkins
ORDER BY is not pushed down in the following query:
SELECT J0.APPNAME, B.\"SYSID\", B.\"USERID\",
(select count(*) from (select * from notes.RETRIEVE_NOTES where OBJECT_PKEY = B.USERID) as foo) as C_notesForObject
FROM \"SECURITY.BASEUSER\" as B left join security.sysinfo J0 on J0.sysid=B.sysid ORDER BY J0.APPNAME ASC
SECURITY comes from the DB2 translator
notes comes from a programmatic translator which does not support ORDER BY
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Closed: (TEIID-1488) EDS adminshell fails to connect to server with IBM JDK
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1488?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-1488.
---------------------------------
> EDS adminshell fails to connect to server with IBM JDK
> ------------------------------------------------------
>
> Key: TEIID-1488
> URL: https://issues.jboss.org/browse/TEIID-1488
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.1.1
> Environment: SOA-P 5.1 ER7 build
> java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pxi3260sr8-20100409_01(SR8))
> IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr8-20100401_55940 (JIT enabled, AOT enabled)
> J9VM - 20100401_055940
> JIT - r9_20100401_15339
> GC - 20100308_AA)
> JCL - 20100408_01
> uname -a
> Linux soa3.qa.atl2.redhat.com 2.6.18-128.4.1.el5 #1 SMP Thu Jul 23 19:59:17 EDT 2009 i686 athlon i386 GNU/Linux
> Reporter: Len DiMaggio
> Labels: ibm-jvm, ssl
> Fix For: 7.4
>
>
> export JAVA_HOME=/opt/ibm-java-i386-60/jre
> export PATH=/opt/ibm-java-i386-60/jre/bin/:$PATH
> sh ./adminshell.sh
> ======================================================================
> Teiid AdminShell Bootstrap Environment
> TEIID_HOME = /qa/hudson_ws/workspace/teiidAdminShell/BITS/PLATFORM/jdk/openjdk-local/label/RHEL5_x86/jbosssoa/eds/teiid/adminshell
> CLASSPATH = /qa/hudson_ws/workspace/teiidAdminShell/BITS/PLATFORM/jdk/openjdk-local/label/RHEL5_x86/jbosssoa/eds/teiid/adminshell/lib/patches/*:/qa/hudson_ws/workspace/teiidAdminShell/BITS/PLATFORM/jdk/openjdk-local/label/RHEL5_x86/jbosssoa/eds/teiid/adminshell/lib/teiid-adminshell-7.1.1.jar:/qa/hudson_ws/workspace/teiidAdminShell/BITS/PLATFORM/jdk/openjdk-local/label/RHEL5_x86/jbosssoa/eds/teiid/adminshell/lib/*
> JAVA = /opt/ibm-java-i386-60/jre/bin/java
> ======================================================================
> ===> [import static org.teiid.adminshell.AdminShell.*; import static org.teiid.adminshell.GroovySqlExtensions.*; import org.teiid.adminapi.*;]
> Groovy Shell (1.7.2, JVM: 1.6.0)
> Type 'help' or '\h' for help.
> ------------------------------------------------------------------------------------------------------------------------------------------
> groovy:000> connectAsAdmin("mms://localhost:31443", "admin", "admin", "testing")
> ERROR java.lang.AssertionError:
> Assertion failed.
> at org.teiid.core.util.Assertion.failed (Assertion.java:73)
> at org.teiid.core.util.Assertion.assertTrue (Assertion.java:68)
> at org.teiid.core.util.Assertion.assertTrue (Assertion.java:60)
> at org.teiid.net.socket.SocketUtil.addCipherSuite (SocketUtil.java:135)
> at org.teiid.net.socket.SocketUtil$SSLSocketFactory.getSocket (SocketUtil.java:85)
> at org.teiid.net.socket.OioOjbectChannelFactory.createObjectChannel (OioOjbectChannelFactory.java:165)
> at org.teiid.net.socket.SocketServerInstanceImpl.connect (SocketServerInstanceImpl.java:91)
> at org.teiid.net.socket.SocketServerConnectionFactory.getServerInstance (SocketServerConnectionFactory.java:276)
> at org.teiid.net.socket.SocketServerConnection.connect (SocketServerConnection.java:172)
> at org.teiid.net.socket.SocketServerConnection.selectServerInstance (SocketServerConnection.java:124)
> at org.teiid.net.socket.SocketServerConnection.<init> (SocketServerConnection.java:94)
> at org.teiid.net.socket.SocketServerConnectionFactory.getConnection (SocketServerConnectionFactory.java:312)
> at org.teiid.net.socket.SocketServerConnectionFactory.getConnection (SocketServerConnectionFactory.java:71)
> at org.teiid.adminapi.AdminFactory$AdminProxy.<init> (AdminFactory.java:53)
> at org.teiid.adminapi.AdminFactory.createAdmin (AdminFactory.java:159)
> at org.teiid.adminapi.AdminFactory.createAdmin (AdminFactory.java:149)
> at org.teiid.adminapi.AdminFactory.createAdmin (AdminFactory.java:120)
> at org.teiid.adminshell.AdminShell.connectAsAdmin (AdminShell.java:71)
> at org.teiid.adminshell.AdminShell$connectAsAdmin.callStatic (Unknown Source)
> at groovysh_evaluate.run (groovysh_evaluate:3)
> ...
> groovy:000>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Closed: (TEIID-1470) Deploying VDB XML file before data sources leads to failed deployment
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1470?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-1470.
---------------------------------
> Deploying VDB XML file before data sources leads to failed deployment
> ---------------------------------------------------------------------
>
> Key: TEIID-1470
> URL: https://issues.jboss.org/browse/TEIID-1470
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.1.1
> Reporter: Paul Nittel
> Assignee: Steven Hawkins
> Fix For: 7.4
>
>
> Using the dynamic portfolio example, the readme instructs the user to:
> Copy the following files to the <jboss.home>/server/default/deploy directory.
> - portfolio-vdb.xml
> - marketdata-file-ds.xml
> If the user, in fact, deploys the files in that order, and waits to see the VDB deploy before copying the data source, here's what happens.
> The VDB deploys (inactive state)
> The data source deploys successfully
> The VDB status changes to active.
> Queries will fail however as the VDB does not have access to the metadata. Had the file been copied in the reverse order, it would have all worked.
> Issues at play are:
> 1) The readme's copying instructions are backwards, and
> 2) The VDB is marked as active when it should not be
> Both should be corrected.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months