November 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2154) Infrastructure tasks

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2154: ------------------------------------- Summary: Infrastructure tasks Key: TEIID-2154 URL: https://issues.jboss.org/browse/TEIID-2154 Project: Teiid Issue Type: Task Reporter: Steven Hawkins Assignee: Ramesh Reddy Fix For: 8.2 We should begin the switch to a git repository and convert to jboss downloads to remove the need of sf.net hosting. With the downloads copied over, we should be able to use http://www.jboss.org/help/projectpageguide/paragraphguide/directoryListing To mimic sf downloads. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] (TEIID-2308) Enhance reusable execution semantics to support throwing DataNotAvailable from reset method

by Mark Addleman (JIRA)

Mark Addleman created TEIID-2308: ------------------------------------ Summary: Enhance reusable execution semantics to support throwing DataNotAvailable from reset method Key: TEIID-2308 URL: https://issues.jboss.org/browse/TEIID-2308 Project: Teiid Issue Type: Feature Request Reporter: Mark Addleman Assignee: Steven Hawkins reset() can throw DataNotAvailable. Execution will resume at execute() method reset() should only be called once. Details, see https://community.jboss.org/message/773483#773483 -- 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

13 years, 1 month

2
2
0 / 0

[JBoss JIRA] (TEIID-2232) Update Hive translator for newer version of Hive Driver

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2232: ----------------------------------- Summary: Update Hive translator for newer version of Hive Driver Key: TEIID-2232 URL: https://issues.jboss.org/browse/TEIID-2232 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.1 Reporter: Ramesh Reddy Originally Hive translator designed for 0.7 version of the Hive JDBC driver, the current version is "30 April, 2012: release 0.9.0 available". Another important update we should do is take advantage of their direct map-reduce job submission through Hive as native command feature. -- 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

13 years, 1 month

3
3
0 / 0

[JBoss JIRA] (TEIID-2289) Create quickstart to demonstrate using Hive/Hadoop

by Van Halbert (JIRA)

Van Halbert created TEIID-2289: ---------------------------------- Summary: Create quickstart to demonstrate using Hive/Hadoop Key: TEIID-2289 URL: https://issues.jboss.org/browse/TEIID-2289 Project: Teiid Issue Type: Sub-task Components: Build/Kits Reporter: Van Halbert Assignee: Steven Hawkins Create a quick start that can demonstrate using Hive/Hadoop. This will contain instructions for setting up Hadoop. -- 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

13 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (TEIID-1131) Document/expand sequence support

by Steve Hawkins (JIRA)

Document/expand sequence support -------------------------------- Key: TEIID-1131 URL: https://jira.jboss.org/browse/TEIID-1131 Project: Teiid Issue Type: Feature Request Components: JDBC Connector, Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 Currently sequence workaround logic only exists for oracle and is undocumented. We should look at expanding sequence support - even for dynamic vdbs, see SQuriel's handling of system queries for retrieving sequence metadata. At least allowing the workaround logic to work for all sources that support sequences (Postgres, DB2, etc.) would be good. -- 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

13 years, 1 month

4
12
0 / 0

[JBoss JIRA] (TEIID-2309) Add support for "conformed" tables in Teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2309?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2309: -------------------------------- Assignee: Ramesh Reddy (was: Ken Johnson) Complexity: High Component/s: Query Engine Affects: Documentation (Ref Guide, User Guide, etc.),Release Notes > Add support for "conformed" tables in Teiid > ------------------------------------------- > > Key: TEIID-2309 > URL: https://issues.jboss.org/browse/TEIID-2309 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > > Teiid would support tables from different data sources being marked as "conformed", meaning they are the same (or perhaps a different name). When optimising a query, it would take the conformity into account and choose the appropriate copy of the table (presumably one in the same database as other tables in the query, if available). I would not regard it as a problem if Teiid *required* the dimensions to be strictly the same as opposed to permitting subsets, though as with so many areas, it would be up to the user to ensure this was really true: I would not expect the engine to do anything to verify that the tables really were conformed. > Usecase: > In Data Warehousing, it is relatively common to have multiple copies of the same dimensions spread over multiple Data Warehouses or Marts, or in the same Data Warehouse when associated with different Fact Tables. If these copies are either identical or strict subsets of an idealised dimension (and, by extension, share *exactly* the same naming and structure), then they may be said to be "conformed". It is expected that the dimension includes at least the values required to support the facts in the database in which it occurs or the Fact Table to which it is paired. > Example: > > Source S1: > > BIGBIGBIG (millions of rows) > bigkey > ccy > other_stuff > > CURRENCY (100s of rows) let's call it S1_CCY if we need to distinguish > ccy > ccy_name > > > Source S2: > > BIGGER (millions of rows) > biggerkey > bigkey > ccy > more_stuff > > CURRENCY (100s of rows) similarly, S2_CCY > ccy > ccy_name > > > When executing: > > SELECT B.* > FROM BIGBIGBIG B, > CURRENCY CCY > WHERE B.ccy = CCY.ccy > AND CCY.ccy_name LIKE "%DOLLAR%" > > Then it is clearly advantageous to use the copy of CURRENCY in S1 and re-write the query using S1_CCY. In this situation, federation is eliminated completely. > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2309) Add support for "conformed" tables in Teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2309?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2309: -------------------------------- Assignee: (was: Ramesh Reddy) > Add support for "conformed" tables in Teiid > ------------------------------------------- > > Key: TEIID-2309 > URL: https://issues.jboss.org/browse/TEIID-2309 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > > Teiid would support tables from different data sources being marked as "conformed", meaning they are the same (or perhaps a different name). When optimising a query, it would take the conformity into account and choose the appropriate copy of the table (presumably one in the same database as other tables in the query, if available). I would not regard it as a problem if Teiid *required* the dimensions to be strictly the same as opposed to permitting subsets, though as with so many areas, it would be up to the user to ensure this was really true: I would not expect the engine to do anything to verify that the tables really were conformed. > Usecase: > In Data Warehousing, it is relatively common to have multiple copies of the same dimensions spread over multiple Data Warehouses or Marts, or in the same Data Warehouse when associated with different Fact Tables. If these copies are either identical or strict subsets of an idealised dimension (and, by extension, share *exactly* the same naming and structure), then they may be said to be "conformed". It is expected that the dimension includes at least the values required to support the facts in the database in which it occurs or the Fact Table to which it is paired. > Example: > > Source S1: > > BIGBIGBIG (millions of rows) > bigkey > ccy > other_stuff > > CURRENCY (100s of rows) let's call it S1_CCY if we need to distinguish > ccy > ccy_name > > > Source S2: > > BIGGER (millions of rows) > biggerkey > bigkey > ccy > more_stuff > > CURRENCY (100s of rows) similarly, S2_CCY > ccy > ccy_name > > > When executing: > > SELECT B.* > FROM BIGBIGBIG B, > CURRENCY CCY > WHERE B.ccy = CCY.ccy > AND CCY.ccy_name LIKE "%DOLLAR%" > > Then it is clearly advantageous to use the copy of CURRENCY in S1 and re-write the query using S1_CCY. In this situation, federation is eliminated completely. > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2309) Add support for "conformed" tables in Teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2309?page=com.atlassian.jira.plugin... ] Ramesh Reddy moved PRODMGT-276 to TEIID-2309: --------------------------------------------- Project: Teiid (was: Product Management) Key: TEIID-2309 (was: PRODMGT-276) Workflow: jira (was: JBoss Platforms RFE Workflow v2) > Add support for "conformed" tables in Teiid > ------------------------------------------- > > Key: TEIID-2309 > URL: https://issues.jboss.org/browse/TEIID-2309 > Project: Teiid > Issue Type: Feature Request > Reporter: Debbie Steigner > Assignee: Ken Johnson > > Teiid would support tables from different data sources being marked as "conformed", meaning they are the same (or perhaps a different name). When optimising a query, it would take the conformity into account and choose the appropriate copy of the table (presumably one in the same database as other tables in the query, if available). I would not regard it as a problem if Teiid *required* the dimensions to be strictly the same as opposed to permitting subsets, though as with so many areas, it would be up to the user to ensure this was really true: I would not expect the engine to do anything to verify that the tables really were conformed. > Usecase: > In Data Warehousing, it is relatively common to have multiple copies of the same dimensions spread over multiple Data Warehouses or Marts, or in the same Data Warehouse when associated with different Fact Tables. If these copies are either identical or strict subsets of an idealised dimension (and, by extension, share *exactly* the same naming and structure), then they may be said to be "conformed". It is expected that the dimension includes at least the values required to support the facts in the database in which it occurs or the Fact Table to which it is paired. > Example: > > Source S1: > > BIGBIGBIG (millions of rows) > bigkey > ccy > other_stuff > > CURRENCY (100s of rows) let's call it S1_CCY if we need to distinguish > ccy > ccy_name > > > Source S2: > > BIGGER (millions of rows) > biggerkey > bigkey > ccy > more_stuff > > CURRENCY (100s of rows) similarly, S2_CCY > ccy > ccy_name > > > When executing: > > SELECT B.* > FROM BIGBIGBIG B, > CURRENCY CCY > WHERE B.ccy = CCY.ccy > AND CCY.ccy_name LIKE "%DOLLAR%" > > Then it is clearly advantageous to use the copy of CURRENCY in S1 and re-write the query using S1_CCY. In this situation, federation is eliminated completely. > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2306) Spreadsheet Retry Delay

by Filip Nguyen (JIRA)

Filip Nguyen created TEIID-2306: ----------------------------------- Summary: Spreadsheet Retry Delay Key: TEIID-2306 URL: https://issues.jboss.org/browse/TEIID-2306 Project: Teiid Issue Type: Sub-task Reporter: Filip Nguyen Assignee: Filip Nguyen Create Retry Delay property for ClientLogin API and investigate possible exceptions. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2304) Spreadsheet Integration tests/unit tests

by Filip Nguyen (JIRA)

Filip Nguyen created TEIID-2304: ----------------------------------- Summary: Spreadsheet Integration tests/unit tests Key: TEIID-2304 URL: https://issues.jboss.org/browse/TEIID-2304 Project: Teiid Issue Type: Sub-task Reporter: Filip Nguyen Assignee: Filip Nguyen Identify/add more unit tests to the spreadsheet. Run integration tests in separate profile probably with username/password supplied via java properties. -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2012