November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1326) API request: rewrite query/command before it reaches the teiid planner

by Mark Addleman (JIRA)

API request: rewrite query/command before it reaches the teiid planner ----------------------------------------------------------------------- Key: TEIID-1326 URL: https://jira.jboss.org/browse/TEIID-1326 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Mark Addleman Assignee: Steven Hawkins I'd like an API to inspect and rewrite a user query/command before it reaches the Teiid planner. The use case is to rewrite the query/command to implement view-like capabilities. For example: SELECT a,b,c FROM table1 AS t WHERE t.a='xyz' would be rewritten as: SELECT a,b,c FROM (SELECT a,b,c FROM table2 UNION SELECT a,b,c FROM table3) AS t I imagine this API would be similar to the translator API: it would receive a data structure representing the query/command and use a visitor to rewrite the query. As a convenience, it would be nice to have something similar to the SQLConversionVisitor. -- 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, 10 months

6
19
0 / 0

[JBoss JIRA] Created: (TEIID-1720) Support for JBoss AS 7.x as host environment

by Ramesh Reddy (JIRA)

Support for JBoss AS 7.x as host environment -------------------------------------------- Key: TEIID-1720 URL: https://issues.jboss.org/browse/TEIID-1720 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 7.6 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 Currently Teiid 7.x line is based on JBoss AS 5.1.0. Migrate host environment to JBoss AS 7.x. This JIRA will be used to put in some initial work, then will be used bucket to add sub-tasks involved in the overhaul. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
5
0 / 0

[JBoss JIRA] (TEIID-1841) week function in teiid not returning expected value

by Graeme Gillies (Created) (JIRA)

week function in teiid not returning expected value --------------------------------------------------- Key: TEIID-1841 URL: https://issues.jboss.org/browse/TEIID-1841 Project: Teiid Issue Type: Bug Affects Versions: 7.5 Environment: Teiid 7.5 running on java 1.6 openjdk on rhel5 Reporter: Graeme Gillies Assignee: Steven Hawkins One of our users of our teiid instance as reported that the week function (to determine which week of the year it is) operates in teiid a little different to how they expect. Teiid resets the week count to 1 on every 1st of January even though the day is not the 1st day of the week (Sunday in here). But Postgres will only resets the week count to 1 only on the 1st Monday of the year. The examples below compare the results return by teiid and Postgres: {noformat} # Teiid result: EngVDBR=> select week(parsedate('2011-01-01', 'yyyy-MM-dd')) AS Week; week ------ 1 (1 row) EngVDBR=> select week(parsedate('2011-01-02', 'yyyy-MM-dd')) AS Week; week ------ 2 (1 row) {noformat} {noformat} # Postgres result: postgres=> SELECT EXTRACT(WEEK FROM DATE '2011-01-01') AS Week; week ------ 52 (1 row) postgres=> SELECT EXTRACT(WEEK FROM DATE '2011-01-03') AS Week; week ------ 1 (1 row) {noformat} -- 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

4
4
0 / 0

[JBoss JIRA] Created: (TEIID-1604) Rationalize the context objects

by Steven Hawkins (JIRA)

Rationalize the context objects ------------------------------- Key: TEIID-1604 URL: https://issues.jboss.org/browse/TEIID-1604 Project: Teiid Issue Type: Quality Risk Components: Connector API, Query Engine Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 The the CommandContext and the ExecutionContext should have their methods rationalized so that there is a uniform way to access information (ExecutionContext.getCommandContext().getSession().getUsername() vs. ExecutionContext.getUserName()) and/or at least ensure that method names are the same. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (TEIID-1851) run.bat in simpleclient for teiid 7.5 incorrect path

by Mike Bailey (Created) (JIRA)

run.bat in simpleclient for teiid 7.5 incorrect path ---------------------------------------------------- Key: TEIID-1851 URL: https://issues.jboss.org/browse/TEIID-1851 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 7.5 Environment: Windows 7 Reporter: Mike Bailey Assignee: Steven Hawkins Priority: Minor following the instructions in the quick start guide and the README for the simpleclient, the command fails when run on windows. run.bat localhost 31000 dynamicportfolio "select * from tables" This part of the run.bat is incorrect: rem Second one adds the Teiid client set TEIID_PATH=../lib/teiid-7.5.0.Final-client.jar should be: rem Second one adds the Teiid client set TEIID_PATH=../../lib/teiid-7.5.0.Final-client.jar -- 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

4
3
0 / 0

[JBoss JIRA] (TEIID-1819) Reading multi entity data from a single data file

by Peter Larsen (Created) (JIRA)

Reading multi entity data from a single data file ------------------------------------------------- Key: TEIID-1819 URL: https://issues.jboss.org/browse/TEIID-1819 Project: Teiid Issue Type: Feature Request Components: Connector API Environment: Any Reporter: Peter Larsen Assignee: Steven Hawkins A common problem for data files is the concept of multiple data sets inclosed in the same file. An example is a data file of accounts receivable orders. You'll export at least two logical entities: Orders and OrderLines. Each of the two entities have very different data sets; the relate (OrderLines belong to a particular Order) and there are a dynamic number of OrderLines per Order. A common way to differentiate is to put a special "record type" selector as the first field in each record. Ie. A and B. The load program will based on this selector apply different templates to map the columns, and it will also know that the OrderLines are associated with the Order above it and create that relation column ID in the out put. Example: ;selector=A,orderdate,ordernumber,customernumber,ordertotal,ordertax ;selector=B,lineno,itemno,description,quantity,priceach,pricetotal A,10-dec-2011,12345,3322,3000,222 B,1,123,Sprockets Black,30,50,1500 B,2,333,Sprockets Blue,300,5,1500 A,11-dec-2011,12346,3311,..... etc. -- 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

5
14
0 / 0

[JBoss JIRA] (TEIID-1829) Clarify source warnings

by Steven Hawkins (Created) (JIRA)

Clarify source warnings ----------------------- Key: TEIID-1829 URL: https://issues.jboss.org/browse/TEIID-1829 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 When a warning is added through an ExecutionContext, the client receives the exception wrapped by a SourceException, then wrapped as a SQLException. The issues with this are that the SourceException class is not expressly public and there is an unnecessary level of wrapping. We should introduce a TeiddSQLWarning for non-partial results warnings that would contain source/model information and prevent the unnecessary wrapping. -- 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

3
4
0 / 0

[JBoss JIRA] (TEIID-1809) Teiid maven build needs to work off of Jboss parent pom

by Ramesh Reddy (Created) (JIRA)

Teiid maven build needs to work off of Jboss parent pom ------------------------------------------------------- Key: TEIID-1809 URL: https://issues.jboss.org/browse/TEIID-1809 Project: Teiid Issue Type: Enhancement Components: Build/Kits Reporter: Ramesh Reddy Version 7 of the JBoss parent POM was released today. Please consider using this as the parent POM for your Maven builds, because it helps keep our builds consistent. Also, be aware that this POM is now in the Public Domain (i.e. no copyright), and the license setting will be inherited to your POMs unless overridden. So make sure your POM contains the correct <license> settings after updating. Some other notable changes in this version are that the release profile is now called "jboss-release". If you use the maven release plugin this profile will be called automatically, but if you release manually, then you should add "-Pjboss-release" to the build command, and the jboss-parent configuration will generate javadoc jars, and update the release info in the repository. The full list of changes in this version is available in jira [1], and more information about using the POM is available on the github site [2] [1]https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310081&ver... [2]https://github.com/jboss/jboss-parent-pom -- 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

4
3
0 / 0

[JBoss JIRA] Created: (TEIID-1687) GSSAPI support for postgres emulation layer

by Graeme Gillies (JIRA)

GSSAPI support for postgres emulation layer ------------------------------------------- Key: TEIID-1687 URL: https://issues.jboss.org/browse/TEIID-1687 Project: Teiid Issue Type: Feature Request Affects Versions: 7.4 Environment: All Reporter: Graeme Gillies Assignee: Steven Hawkins Priority: Minor Similar to TEIID-1610 Postgres clients support authentication via GSSAPI http://www.google.com/url?sa=t&source=web&cd=2&ved=0CB4QFjAB&url=http%3A%... It would be great if teiid's postgres emulation layer would allow it to support GSSAPI as an authentication mechanism from clients. Server side you could setup a keytab with the correct server side principal postgres/$fqdn(a)REALM.COM which teiid would use to authenticate clients connecting to it via the postgres emulation layer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
4
0 / 0

[JBoss JIRA] Created: (TEIID-1540) Add the ability to delegate one shot dependent joins to the translators

by Steven Hawkins (JIRA)

Add the ability to delegate one shot dependent joins to the translators ----------------------------------------------------------------------- Key: TEIID-1540 URL: https://issues.jboss.org/browse/TEIID-1540 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4 Using a memory safe iterator, like with bulk handling, we should be able to push dependent joins to the translator to perform specialized source specific one-shot join handling. With the other dependent join improvements this should hopefully be needed only in the most extreme cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011