June 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2527) Dynamically change the sources in a multi-source model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2527?page=com.atlassian.jira.plugin... ] Work on TEIID-2527 started by Steven Hawkins. > Dynamically change the sources in a multi-source model > ------------------------------------------------------ > > Key: TEIID-2527 > URL: https://issues.jboss.org/browse/TEIID-2527 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.5 > > > As a step toward a more dynamic VDB, it would be useful to allow data sources to be dynamically added/removed from a multi-source model. For more, see https://community.jboss.org/message/821113 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2522) Let Extract(<Oracle Date field>) extract time components

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2522?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2522. ----------------------------------- Resolution: Done Updated the hour/minute/second extraction to ensure oracle date typed expressions are cast to timestamp. > Let Extract(<Oracle Date field>) extract time components > -------------------------------------------------------- > > Key: TEIID-2522 > URL: https://issues.jboss.org/browse/TEIID-2522 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Alex K. > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.5 > > > According to the Oracle's docs: > > "The DATE datatype stores point-in-time values (dates and times) in a table. The DATE datatype stores the year (including the century), the month, the day, the hours, the minutes, and the seconds (after midnight)." > > I expect to be able to extract the time parts from a date field, but when I am trying to extract the hour from an oracle's date field like: > > {code:sql} > SELECT EXTRACT(HOUR FROM a.modifieddate) > FROM oracle_db.salestaxrate a > WHERE a.salestaxrateid = 1 > {code} > > and get a TEIID30504 exception. When I look deeper in Teiid's log, i see the following Oracle's exception: > > Caused by: java.sql.SQLException: Remote java.sql.SQLException: ORA-30076: invalid extract field for extract source > That is an odd Oracle limitation - http://docs.oracle.com/cd/B28359_01/server.111/b28286/functions052.htm > > "If HOUR, MINUTE, or SECOND is requested, then expr must evaluate to an expression of datatype TIMESTAMP, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITH LOCAL TIME ZONE, or INTERVAL DAY TO SECOND. DATE is not valid here, because Oracle Database treats it as ANSI DATE datatype, which has no time fields." > *please enable extracting of time components from oracle's Date Fields* despite the Oracle's limitation -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2512) Allow chaining of Metadata Repositories with multiple <metadata> elements in vdb.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2512?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2512. ----------------------------------- Resolution: Done Instead of deprecation (since we may one day want separate metadata elements with specific text and the element text is used in all examples) opted for allowing properties to be specified by element text (rather than just attribute) and provided ddl/ddl-file with logic to look for the ddl and ddl-file model properties to perform their loads. > Allow chaining of Metadata Repositories with multiple <metadata> elements in vdb.xml > ------------------------------------------------------------------------------------ > > Key: TEIID-2512 > URL: https://issues.jboss.org/browse/TEIID-2512 > Project: Teiid > Issue Type: Enhancement > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > Currently when chaining the multiple Metadata Repositories in VDB.xml they are defined using a comma separated list on <metadata> element. Any "context" specific value is submitted via "TEXT" element under <metadata>. > However with above only one TEXT value can be defined, and if multiple repositories need to use the TEXT value there is no way to distinguish who is the owner of the data. > A Enhancement is required to be able to define multiple <metadata> elements in the vdb.xml to chain the repositories instead using the comma separated list. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2512) Allow chaining of Metadata Repositories with multiple <metadata> elements in vdb.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2512?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2512: --------------------------------------- The simplest direction is to just deprecate the usage of the metadata text and instead prefer the usage of model properties. At that point we still may want to expand upon the usage of the metadata element by allowing multiple and allowing for their own property sets. > Allow chaining of Metadata Repositories with multiple <metadata> elements in vdb.xml > ------------------------------------------------------------------------------------ > > Key: TEIID-2512 > URL: https://issues.jboss.org/browse/TEIID-2512 > Project: Teiid > Issue Type: Enhancement > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > Currently when chaining the multiple Metadata Repositories in VDB.xml they are defined using a comma separated list on <metadata> element. Any "context" specific value is submitted via "TEXT" element under <metadata>. > However with above only one TEXT value can be defined, and if multiple repositories need to use the TEXT value there is no way to distinguish who is the owner of the data. > A Enhancement is required to be able to define multiple <metadata> elements in the vdb.xml to chain the repositories instead using the comma separated list. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2562) add allow-join to the relational med

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2562?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2562: ---------------------------------- Parent: (was: TEIID-2539) Issue Type: Task (was: Sub-task) > add allow-join to the relational med > ------------------------------------ > > Key: TEIID-2562 > URL: https://issues.jboss.org/browse/TEIID-2562 > Project: Teiid > Issue Type: Task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > a boolean extension property allow-join, with a default of true should be added to the relational med and can be specified on foreign keys. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2562) add allow-join to the relational med

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2562: ------------------------------------- Summary: add allow-join to the relational med Key: TEIID-2562 URL: https://issues.jboss.org/browse/TEIID-2562 Project: Teiid Issue Type: Sub-task Reporter: Steven Hawkins Assignee: Steven Hawkins a boolean extension property allow-join, with a default of true should be added to the relational med and can be specified on foreign keys. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2539) Add "allow-join" metadata based join processing on Foreign keys

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2539?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2539. ----------------------------------- Fix Version/s: 8.5 Resolution: Done Added the allow-join property. For this to be used in the designer the built-in relational med will need to be updated. > Add "allow-join" metadata based join processing on Foreign keys > --------------------------------------------------------------- > > Key: TEIID-2539 > URL: https://issues.jboss.org/browse/TEIID-2539 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > MongoDB source generally does not support any joins between it collection of documents. However, one document can be embedded in other parent document, then those documents can be viewed as JOIN based documents. > Teiid's MongoDB translator takes the above as an approach to define each collection as a table, and provides ways to embed related tables into parent document for supporting the JOIN in SQL. > However, there may be situations, there is PK-FK relation between two tables, but they are not embeded, in those situations based on the capabilities of translator the query engine still pushes the join into translator for processing, but translator can not handle the join. In these situations, where the collections are not embedded the query engine need to behave as if translator does not support JOIN. > The proposal here is to add a extension metadata on FOREIGN KEY called "allow-joins=false", which query engine will consult along with the capabilities of the translator before it pushes the JOIN to the source translator. > This would be useful in non-relational translators to selectively support JOINS where possible. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2512) Allow chaining of Metadata Repositories with multiple <metadata> elements in vdb.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2512?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2512: ---------------------------------- Fix Version/s: 8.4.1 8.5 Affects: Documentation (Ref Guide, User Guide, etc.),Compatibility/Configuration > Allow chaining of Metadata Repositories with multiple <metadata> elements in vdb.xml > ------------------------------------------------------------------------------------ > > Key: TEIID-2512 > URL: https://issues.jboss.org/browse/TEIID-2512 > Project: Teiid > Issue Type: Enhancement > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > Currently when chaining the multiple Metadata Repositories in VDB.xml they are defined using a comma separated list on <metadata> element. Any "context" specific value is submitted via "TEXT" element under <metadata>. > However with above only one TEXT value can be defined, and if multiple repositories need to use the TEXT value there is no way to distinguish who is the owner of the data. > A Enhancement is required to be able to define multiple <metadata> elements in the vdb.xml to chain the repositories instead using the comma separated list. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2539) Add "allow-join" metadata based join processing on Foreign keys

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2539?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2539: --------------------------------------- Added the engine handling for the allow-join property using the relational med uri. The mongo metadata logic will now need to be updated as well - and more than likely the key constant should be moved onto the ForeignKey class rather than on RuleRaiseAccess. > Add "allow-join" metadata based join processing on Foreign keys > --------------------------------------------------------------- > > Key: TEIID-2539 > URL: https://issues.jboss.org/browse/TEIID-2539 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.4.1 > > > MongoDB source generally does not support any joins between it collection of documents. However, one document can be embedded in other parent document, then those documents can be viewed as JOIN based documents. > Teiid's MongoDB translator takes the above as an approach to define each collection as a table, and provides ways to embed related tables into parent document for supporting the JOIN in SQL. > However, there may be situations, there is PK-FK relation between two tables, but they are not embeded, in those situations based on the capabilities of translator the query engine still pushes the join into translator for processing, but translator can not handle the join. In these situations, where the collections are not embedded the query engine need to behave as if translator does not support JOIN. > The proposal here is to add a extension metadata on FOREIGN KEY called "allow-joins=false", which query engine will consult along with the capabilities of the translator before it pushes the JOIN to the source translator. > This would be useful in non-relational translators to selectively support JOINS where possible. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2561) Allow nested MERGE of entities in MongoDB translators

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2561?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2561: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Allow nested MERGE of entities in MongoDB translators > ----------------------------------------------------- > > Key: TEIID-2561 > URL: https://issues.jboss.org/browse/TEIID-2561 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.5 > > > Currently the MERGE (EMBEDIN) functionality can not be nested with other embeddable properties. I.e. if table defined "EMBEDIN", then it's parent can not define any embeddable properties. > 1) Rename EMBEDIN --> MERGE extension property > 2) When MERGE is on child table, Allow parent table to be participate in another "MERGE" or "EMBEDDEBLE" scenario. > This will allow greater number of tables to be collapsed into single document. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2013