June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-1093) Request addition of ODC file connections

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1093?page=com.atlassian.jira.plugin.s... ] Steve Hawkins commented on TEIID-1093: -------------------------------------- What are we supposed to be doing with the ODC files? We can consume them as XML. It is also possible to create datasources based upon ODBC connection information, but OLEDB I would guess presumes the use of windows. To act as a full ODC runtime seems far fetched. Do we have any more information on this? > Request addition of ODC file connections > ---------------------------------------- > > Key: TEIID-1093 > URL: https://jira.jboss.org/browse/TEIID-1093 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > > Customer is requesting to include a standard connection to work with MicroSoft "Office Data Connection"(ODC)files -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-977) ENHANCEMENT: Sending Oracle specific commands to the data source.

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-977?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-977. --------------------------------- Resolution: Duplicate Issue See TEIID-669 > ENHANCEMENT: Sending Oracle specific commands to the data source. > ----------------------------------------------------------------- > > Key: TEIID-977 > URL: https://jira.jboss.org/browse/TEIID-977 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Steven Hawkins > Priority: Optional > > ENHANCEMENT: Sending Oracle-specific commands to the data source. The customer wants to send Oracle-specific commands to the data source through MMx. > Example: ALTER SESSION SET DB_FILE_MULTIBLOCK_READ_COUNT = 128. > This setting ensures that Oracle reads data extent-by-extent, which is faster, rather than block-by-block, which is slower. This is on a per session basis. > Tested successfully in Squirrel but unsuccessful using QueryBuilder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-980) Add ability to apply XSLT stylesheets at the datasource level

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-980?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-980. --------------------------------- Fix Version/s: 7.0 Resolution: Out of Date Marking as out of date since the old xml connector logic no longer exists. The xsltransform function should be used to apply xslt. > Add ability to apply XSLT stylesheets at the datasource level > ------------------------------------------------------------- > > Key: TEIID-980 > URL: https://jira.jboss.org/browse/TEIID-980 > Project: Teiid > Issue Type: Feature Request > Components: XML Connector > Reporter: Marc Shirley > Fix For: 7.0 > > > XML data source contains a varying unknown number of "word" elements inside a "segment" that they wish to convert to a single string on the data source side. XQuery did not meet their needs and trying to do a concat fails due to the unknown number of elements. They would like to be able to apply the stylesheet before querying against the file to be able to retrieve a single paragraph, rather than attempt to piece together an unknown number of elements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-964) Must pushdown functions in select clause

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-964?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-964: -------------------------------- Fix Version/s: 8.0 > Must pushdown functions in select clause > ---------------------------------------- > > Key: TEIID-964 > URL: https://jira.jboss.org/browse/TEIID-964 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 8.0 > > > (F_ATM_REPORT_TYPE is a DB function) > SELECT F_ATM_REPORT_TYPE (BUS_LINE_CODE) FROM ... > Will not have the function pushed down if it only appears in the select clause. The planner must check if a function is pushdown only when it appears in the select clause and determine a source to push it to. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-994) Unable to execute Oracle pipelined table function as procedure

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-994?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-994: -------------------------------- Fix Version/s: 8.0 > Unable to execute Oracle pipelined table function as procedure > -------------------------------------------------------------- > > Key: TEIID-994 > URL: https://jira.jboss.org/browse/TEIID-994 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Fix For: 8.0 > > > Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db. > Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1000) Dependent Join in Virtual Model not pushing criteria to both sources

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-1000?page=com.atlassian.jira.plugin.s... ] Steve Hawkins updated TEIID-1000: --------------------------------- Fix Version/s: 8.0 > Dependent Join in Virtual Model not pushing criteria to both sources > -------------------------------------------------------------------- > > Key: TEIID-1000 > URL: https://jira.jboss.org/browse/TEIID-1000 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 8.0 > > > Sample models are attached. User query is: > SELECT * FROM v_TV_SHOWS.v_SHOWS_ACTORS2 > WHERE SHOW_NAME LIKE '%E%' AND > NOT ACTOR_SHOW_ID IN (SELECT ACTOR_SHOW_ID FROM v_TV_SHOWS.v_SHOWS_ACTORS2 WHERE ACTOR_NAME = 'MALCOLM JAMAL-WARNER') > OPTION DEBUG and MMProcess.log are attached. > Customer complaint is that the query contains criteria on ACTOR_NAME and ACTOR_SHOW_ID which is coming from Oracle and on SHOW_NAME which is coming from SQL Server. In the query plan, there is a SELECT node that does not have criteria to Oracle. Instead it is SELECT * which pulls all records. Customer tables are huge so this is an issue for them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-991) Request for support of Sybase IQ as a supported data source

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-991?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-991: -------------------------------- Fix Version/s: 8.0 > Request for support of Sybase IQ as a supported data source > ----------------------------------------------------------- > > Key: TEIID-991 > URL: https://jira.jboss.org/browse/TEIID-991 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > Fix For: 8.0 > > > Per client: > We'd like the ability to have a built-in connector type for Sybase IQ, > just the same as Sybase ASE We have been getting inquiries and we've > had to decline one project because we didn't support Sybase IQ out of > the box. We foresee that Sybase IQ will be getting some play within > important Data Warehouses and Data Marts within the firm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-886) Request for more statistical functions in Teiid

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-886?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-886. --------------------------------- Resolution: Done added support for any/some/every/stddev_pop/stddev_samp/var_pop/var_samp most jdbc sources are marked as supporting (via a new capability method supportsAggregatesEnhancedNumeric), but no compensation was added if the source doesn't support, but does support standard aggs (sum/count) agg decomposition pushdown is supported. > Request for more statistical functions in Teiid > ----------------------------------------------- > > Key: TEIID-886 > URL: https://jira.jboss.org/browse/TEIID-886 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.2.0 > Reporter: Debbie Steigner > Fix For: 7.1 > > > Please provide a richer set of aggregate functions, specifically statistical functions like population standard deviation, sample standard deviation, population standard variance, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-159) Modify our handling of BigDecimal division to use MathContext.DECIMAL128 as our rounding mode to improve scale and precision of results

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-159?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins resolved TEIID-159. --------------------------------- Resolution: Done Updated the floating to bigdecimal conversion to use a scale of 16 for doubles and 8 for floats. Updated the logic in the bigdecimal x/y to use a scale of max(16, x.scale + y.precision + 1), then the result is normalized to remove trailing zeros. > Modify our handling of BigDecimal division to use MathContext.DECIMAL128 as our rounding mode to improve scale and precision of results > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-159 > URL: https://jira.jboss.org/browse/TEIID-159 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Jerry Helbling > Fix For: 7.0 > > > Using MathContext.DECIMAL128 should give a more usable scale and precision to the results. > > Current behavior > 254403453878 / 21870000000 returns 12 > and > 254403453878.0001 / 21870000000 returns 11.6325 > > Improved behavior: > 254403453878 / 21870000000 returns 11.632531 > and > 254403453878.0001 / 21870000000 returns 11.632531 > > We should also investigate what the impact of this change will be on users who may be relying on our current behavior. > Reference: This enhancement was suggested by Issue Tracker Issue 175485, contributed by Greg Haber -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-159) Modify our handling of BigDecimal division to use MathContext.DECIMAL128 as our rounding mode to improve scale and precision of results

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-159?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins updated TEIID-159: -------------------------------- Fix Version/s: 7.0 (was: 8.0) Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] (was: [Compatibility/Configuration, Release Notes]) Moving into the 7.0 release, since this should not wait for 8 and should not be part of a dot release. Will update both the divide behavior and the conversion from floating types to bigdecimal. > Modify our handling of BigDecimal division to use MathContext.DECIMAL128 as our rounding mode to improve scale and precision of results > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-159 > URL: https://jira.jboss.org/browse/TEIID-159 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Jerry Helbling > Fix For: 7.0 > > > Using MathContext.DECIMAL128 should give a more usable scale and precision to the results. > > Current behavior > 254403453878 / 21870000000 returns 12 > and > 254403453878.0001 / 21870000000 returns 11.6325 > > Improved behavior: > 254403453878 / 21870000000 returns 11.632531 > and > 254403453878.0001 / 21870000000 returns 11.632531 > > We should also investigate what the impact of this change will be on users who may be relying on our current behavior. > Reference: This enhancement was suggested by Issue Tracker Issue 175485, contributed by Greg Haber -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010