[JBoss JIRA] (TEIID-1827) Client Recieving java.lang.IndexOutOfBoundsException when performing query
by Van Halbert (Created) (JIRA)
Client Recieving java.lang.IndexOutOfBoundsException when performing query
--------------------------------------------------------------------------
Key: TEIID-1827
URL: https://issues.jboss.org/browse/TEIID-1827
Project: Teiid
Issue Type: Bug
Components: ODBC
Affects Versions: 7.5
Environment: java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.8) (rhel-1.22.1.9.8.el5_6-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
Running on RHEL 5, teiid inside of JBoss EAP 5.1.1
Client is postgresql command line tool version postgresql-9.1.1-1.fc16.x86_64
Using the command line command
psql -h teiid-01.app.eng.bos.redhat.com -p 35432 -U teiid -d EngVDBF
Reporter: Graeme Gillies
Assignee: Steven Hawkins
Fix For: 7.6
When attempting to perform the following query using the postgres command line client connecting to teiids postgres emulation layer, we get the following error
{code}
SELECT components.name, COUNT(bug_id) FROM BugzillaS.bugs bugs, BugzillaS.components components, BugzillaS.profiles profiles WHERE (bugs.component_id =
components.id AND bugs.reporter = profiles.userid AND bugs.creation_ts>='2011-10-04') GROUP BY components.name ORDER BY components.name limit 1500;
{code}
{code}
ERROR: java.lang.IndexOutOfBoundsException
DETAIL: org.teiid.jdbc.TeiidSQLException: java.lang.IndexOutOfBoundsException
{code}
Watching the server logs we don't see any such exception reported there, so I'd need some advice on how to get you some more information.
Regards,
Graeme
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (TEIID-1826) RFE/possible optimization: push down parts of some aggregate expressions
by Van Halbert (Moved) (JIRA)
[ https://issues.jboss.org/browse/TEIID-1826?page=com.atlassian.jira.plugin... ]
Van Halbert moved SOA-3583 to TEIID-1826:
-----------------------------------------
Project: Teiid (was: JBoss Enterprise SOA Platform)
Key: TEIID-1826 (was: SOA-3583)
Component/s: Query Engine
(was: EDS)
Security: (was: Public)
> RFE/possible optimization: push down parts of some aggregate expressions
> ------------------------------------------------------------------------
>
> Key: TEIID-1826
> URL: https://issues.jboss.org/browse/TEIID-1826
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Debbie Steigner
> Assignee: Van Halbert
>
> suggestion for a potential optimization: It concerns federated queries which do expressions. This is an extremely common requirement in the banking business, the main example being when monetary amounts need to be converted into a reporting currency using a rate in another database.
> With the query below, it makes sense that despite the group by, EDS will pull back all the rows so it can multiply one by the other. Unfortunately this is often many millions of records.
> Would it be feasible to have an optimization which push-down most of the aggregation to the source, then do a further aggregation in EDS?
> * sum the tsl.func_amount, grouped by tsl.currency
> * next: get the conversion rates for all the currency codes which have been returned, then sum(total * rate)
> Of course, this can only be done for certain kinds of expressions.
> select sum(tsl.func_amount * ccy.EuroConversionLegacyRate)
> from TSL_FINANCIAL_ACCOUNT_ITEMS_T2 tsl
> join t_sdm_currency ccy on tsl.currency = ccy.currencycode
> where tsl.business_date = '2011-06-29'
> group by ccy.EuroConversionLegacyRate
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (TEIID-1752) JavaDocs for Teiid needs to contain only what's exposed.
by Steven Hawkins (Commented) (JIRA)
[ https://issues.jboss.org/browse/TEIID-1752?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-1752:
---------------------------------------
The aggregate-jar goal is causing issues with initial builds in the release profile using maven 3. The build will complain about missing dependencies and error out. There are a host of maven related issues related to this and it's not clear if we are doing something wrong of if it's maven. The workaround is to run mvn install not in the release profile first to bootstrap the local repository or to run with -Dmaven.javadoc.skip=true.
Is the product build running maven 2 and/or has it always run a non-release profile install prior to running in the release profile? Could we look at setting the skip property to true by default and having the product build explicitly set it to false?
> JavaDocs for Teiid needs to contain only what's exposed.
> --------------------------------------------------------
>
> Key: TEIID-1752
> URL: https://issues.jboss.org/browse/TEIID-1752
> Project: Teiid
> Issue Type: Enhancement
> Components: Documentation
> Affects Versions: 7.4.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 7.4.1
>
>
> Make adjustments to the pom.xml to exclude packages that don't need to be javadoc'd.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (TEIID-1817) Documentation changes for SSL configuration
by Van Halbert (Created) (JIRA)
Documentation changes for SSL configuration
-------------------------------------------
Key: TEIID-1817
URL: https://issues.jboss.org/browse/TEIID-1817
Project: Teiid
Issue Type: Bug
Components: Documentation
Affects Versions: 7.4.1
Reporter: Paul Nittel
Assignee: Steven Hawkins
While testing SSL configuration I noticed a few items in the documentation which were confusing and in need of clarification.
keymanagementAlgorithm - Type of key algorithm used. Default is based upon the VM, e.g. "SunX509"
The out-of-the-box value of keymanagementAlgorithm is "false". If SunX509 is likely to be used, let's have it in teiid-jboss-beans.xml by default.
The doc mentions the keystore "must be available in the classpath of Teiid Server." Apparently that's not just anywhere. I tried the lib directory and it failed. Ramesh suggested the conf directory and it worked. If it must be in conf, let's say so.
Lastly, a minor nit. The second paragraph under section "3.5 Configuring SSL" is: There are three socket transports, each with it's own SSL configuration. Of course the word "it's" (a contraction of "it" and "is") should be replaced by the possessive form, "its".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months