March 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3369) Add a extension point to manipulate incoming sql

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3369?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3369: ---------------------------------- Fix Version/s: 8.11 > Add a extension point to manipulate incoming sql > ------------------------------------------------ > > Key: TEIID-3369 > URL: https://issues.jboss.org/browse/TEIID-3369 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > We should look at adding a client or server extension point for manipulating sql - just the sql string, pre resolving. This will allow more flexibility in dealing with clients that don't send queries directly understood by Teiid. For example a select for update. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2709) Quickstart - drools-integration uses drools 5 instead of drools 6

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2709?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2709. ----------------------------------- Resolution: Done Van is correct, so resolving. > Quickstart - drools-integration uses drools 5 instead of drools 6 > ------------------------------------------------------------------- > > Key: TEIID-2709 > URL: https://issues.jboss.org/browse/TEIID-2709 > Project: Teiid > Issue Type: Enhancement > Components: Quick Starts > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The drools-integration quick start uses drools 5, instead of drools 6. > And its not a matter of swapping out the versions due to api changes drools 6. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3368) The database-service.jar needs version version in its name

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3368?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3368: ------------------------------- Git Pull Request: https://github.com/vhalbert/teiid-extensions/commit/90e2b9d144f3b967ce81d... > The database-service.jar needs version version in its name > ---------------------------------------------------------- > > Key: TEIID-3368 > URL: https://issues.jboss.org/browse/TEIID-3368 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.7.1, 8.11 > Reporter: Van Halbert > Assignee: Van Halbert > > The database-service.jar in the tepid-extensions needs to be built with a version in the name. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3371) Upgrade Teiid with EAP 6.4 Alpha

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3371?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3371: ------------------------------------ I'm upgrading teiid-extensions, as I'm making another change. > Upgrade Teiid with EAP 6.4 Alpha > -------------------------------- > > Key: TEIID-3371 > URL: https://issues.jboss.org/browse/TEIID-3371 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.11 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > Upgrade all the Teiid projects to be built based on EAP 6.4 Alpha. Currently, this would align with jboss-integration-platform-bom 6.0.0.CR25 and EAP Alpha version 7.5.0.Final-redhat-17. Note, 7.5.0.Final-redhat-17 is the version in the EAP kit, but only CR25 bom is available. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3371) Upgrade Teiid with EAP 6.4 Alpha

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3371?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-3371: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Upgrade Teiid with EAP 6.4 Alpha > -------------------------------- > > Key: TEIID-3371 > URL: https://issues.jboss.org/browse/TEIID-3371 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.11 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > Upgrade all the Teiid projects to be built based on EAP 6.4 Alpha. Currently, this would align with jboss-integration-platform-bom 6.0.0.CR25 and EAP Alpha version 7.5.0.Final-redhat-17. Note, 7.5.0.Final-redhat-17 is the version in the EAP kit, but only CR25 bom is available. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3265) Incorrect result if multiple aggregate functions used

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3265?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3265. --------------------------------- > Incorrect result if multiple aggregate functions used > ----------------------------------------------------- > > Key: TEIID-3265 > URL: https://issues.jboss.org/browse/TEIID-3265 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.9 > Reporter: Renat Zhilkibaev > Assignee: Steven Hawkins > > When using multiple aggregate functions the value returned by the first one is used as a result of the second one. > With data looking like this: > SYMBOL,PRICE > GE,10.45 > GE,15.45 > GE,20.45 > and this query: > select symbol, max(price), min(price) from mytable group by symbol > result looks like this: > GE, 20.45,20.45 > Note the last value is 20.45 which is not a correct value (10.45). > To reproduce download teiid-8.9.0.Final-embedded-dist.zip from http://sourceforge.net/projects/teiid/files/teiid-8.9.0.Final-embedded-di... > replace content of examples/embedded-portfolio/data/marketdata-price.txt with > SYMBOL,PRICE > GE,10.45 > GE,15.45 > GE,20.45 > Then change the query at > examples/embedded-portfolio/src/org/teiid/example/TeiidEmbeddedPortfolio.java line 186 to be "select symbol, max(price), min(price) from MyView.portfolio group by symbol" > Then execute examples/embedded-portfolio/run.sh -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3335) Uniqueidentifier values are casted inside INSERT clause field list

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3335?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3335. --------------------------------- > Uniqueidentifier values are casted inside INSERT clause field list > ------------------------------------------------------------------ > > Key: TEIID-3335 > URL: https://issues.jboss.org/browse/TEIID-3335 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Nicholas D > Assignee: Steven Hawkins > Labels: sqlserver2012 > > When inserting into SQL Server table which has uniqueidentifier values - Teiid casts these fields to char(36) inside field list. > Example. When i execute query > bq. INSERT INTO TABLE(record_id, "time", tag_id, "value") > VALUES(UUID(), NOW(), '123', 123);}} > Teiid gives me error > bq. Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 ds: 102 TEIID11013:TEIID11004 Error executing statement(s): [Prepared Values: [{ts '2015-02-12 15:40:18.051'}] SQL: INSERT INTO "dbo"."TABLE" (cast("RECORD_ID" as char(36)), "TIME", "TAG_ID", "VALUE") VALUES (uuid(), ?, '123', 123)] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3289) Join subquery containing ifnull in join condition

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3289?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3289. --------------------------------- > Join subquery containing ifnull in join condition > ------------------------------------------------- > > Key: TEIID-3289 > URL: https://issues.jboss.org/browse/TEIID-3289 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Critical > > I have join subquery linked to main query via 2 fields in the query below. > To be able to join null values between main query and subquery, I have added ifnull to join fields with a random value. > If I run my query directly over mysql, the field CalculatedField1 return values whenever the field RESOLUTIONDATE is null in the main query. > But when executed in Teiid, the query returns always null for the field CalculatedField1. > When looking at the jdbc queries executed by Teiid, I found that ifnull is used for the main query fields but not for the subquery fields, which may be causing a link problem between main query and subquery. > I have tried to put the ifnull into the subquery but still getting jdbc subquery fields without the ifnull function. > SELECT DISTINCT > jiraissue.RESOLUTIONDATE AS jiraissue_RESOLUTIONDATE, > jiraissue.CREATED AS jiraissue_CREATED, > CalculatedField1_Sub.CalculatedField1 AS CalculatedField1 > FROM tjiradb_D1_VDB_DSModel.tjiradb.jiraissue jiraissue > LEFT JOIN > (SELECT DISTINCT > TIMESTAMPDIFF( > SQL_TSI_MINUTE, > jiraissue_sub.CREATED, > PARSETIMESTAMP('2014-10-03 00:00:00', > 'yyyy-MM-dd HH:mm:ss')) > AS CalculatedField1, > jiraissue_sub.RESOLUTIONDATE AS jiraissue_RESOLUTIONDATE, > jiraissue_sub.CREATED AS jiraissue_CREATED > FROM tjiradb_D1_VDB_DSModel.tjiradb.jiraissue jiraissue_sub > WHERE ((((jiraissue_sub.RESOLUTIONDATE IS NULL))))) > CalculatedField1_Sub > ON (IFNULL(jiraissue.RESOLUTIONDATE, -2147483648) = > IFNULL(CalculatedField1_Sub.jiraissue_RESOLUTIONDATE, > -2147483648)) > AND (IFNULL(jiraissue.CREATED, -2147483648) = > IFNULL(CalculatedField1_Sub.jiraissue_CREATED, > -2147483648)) > Teiid JDBC queries: > SELECT DISTINCT g_0.`RESOLUTIONDATE` AS c_0, g_0.`CREATED` AS c_1, ifnull(date_format(g_0.`RESOLUTIONDATE`, '%Y-%m-%d %H:%i:%S.%f'), '-2147483648') AS c_2, ifnull(date_format(g_0.`CREATED`, '%Y-%m-%d %H:%i:%S.%f'), '-2147483648') AS c_3 FROM `tjiradb`.`jiraissue` AS g_0 ORDER BY c_2, c_3 > SELECT g_0.`CREATED`, g_0.`RESOLUTIONDATE` FROM `tjiradb`.`jiraissue` AS g_0 WHERE g_0.`RESOLUTIONDATE` IS NULL > Teiid Execution plan > > <?xml version='1.0' encoding='UTF-8'?><node name="LimitNode"><property name="Output Columns"><value>jiraissue_RESOLUTIONDATE (timestamp)</value><value>jiraissue_CREATED (timestamp)</value><value>CalculatedField1 (long)</value></property><property name="Statistics"><value>Node Output Rows: 10</value><value>Node Next Batch Process Time: 7</value><value>Node Cumulative Next Batch Process Time: 43</value><value>Node Cumulative Process Time: 49</value><value>Node Next Batch Calls: 4</value><value>Node Blocks: 3</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: 10.0</value></property><property name="Child 0"><node name="SortNode"><property name="Output Columns"><value>jiraissue_RESOLUTIONDATE (timestamp)</value><value>jiraissue_CREATED (timestamp)</value><value>CalculatedField1 (long)</value></property><property name="Statistics"><value>Node Output Rows: 10</value><value>Node Next Batch Process Time: 13</value><value>Node Cumulative Next Batch Process Time: 42</value><value>Node Cumulative Process Time: 48</value><value>Node Next Batch Calls: 4</value><value>Node Blocks: 3</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="ProjectNode"><property name="Output Columns"><value>jiraissue_RESOLUTIONDATE (timestamp)</value><value>jiraissue_CREATED (timestamp)</value><value>CalculatedField1 (long)</value></property><property name="Statistics"><value>Node Output Rows: 2048</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 35</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 5</value><value>Node Blocks: 4</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="JoinNode"><property name="Output Columns"><value>RESOLUTIONDATE (timestamp)</value><value>CREATED (timestamp)</value><value>CalculatedField1 (long)</value></property><property name="Statistics"><value>Node Output Rows: 2048</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 35</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 5</value><value>Node Blocks: 4</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="AccessNode"><property name="Output Columns"><value>RESOLUTIONDATE (timestamp)</value><value>CREATED (timestamp)</value><value>expr (string)</value><value>expr (string)</value></property><property name="Statistics"><value>Node Output Rows: 2048</value><value>Node Next Batch Process Time: 0</value><value>Node Cumulative Next Batch Process Time: 1</value><value>Node Cumulative Process Time: 0</value><value>Node Next Batch Calls: 10</value><value>Node Blocks: 6</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value>SELECT DISTINCT g_0.RESOLUTIONDATE AS c_0, g_0.CREATED AS c_1, IFNULL(convert(g_0.RESOLUTIONDATE, string), '-2147483648') AS c_2, IFNULL(convert(g_0.CREATED, string), '-2147483648') AS c_3 FROM tjiradb_D1_VDB_DSModel.tjiradb.jiraissue AS g_0 ORDER BY c_2, c_3</value></property><property name="Model Name"><value>tjiradb_D1_VDB_DSModel</value></property></node></property><property name="Child 1"><node name="ProjectNode"><property name="Output Columns"><value>CalculatedField1 (long)</value><value>jiraissue_RESOLUTIONDATE (timestamp)</value><value>jiraissue_CREATED (timestamp)</value><value>CalculatedField11 (long)</value><value>expr (string)</value><value>expr (string)</value></property><property name="Statistics"><value>Node Output Rows: 1320</value><value>Node Next Batch Process Time: 22</value><value>Node Cumulative Next Batch Process Time: 18</value><value>Node Cumulative Process Time: 25</value><value>Node Next Batch Calls: 4</value><value>Node Blocks: 1</value></property><property name="Child 0"><node name="ProjectNode"><property name="Output Columns"><value>CalculatedField1 (long)</value><value>jiraissue_RESOLUTIONDATE (timestamp)</value><value>jiraissue_CREATED (timestamp)</value><value>CalculatedField11 (long)</value></property><property name="Statistics"><value>Node Output Rows: 1320</value><value>Node Next Batch Process Time: 9</value><value>Node Cumulative Next Batch Process Time: 3</value><value>Node Cumulative Process Time: 10</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Child 0"><node name="AccessNode"><property name="Output Columns"><value>CREATED (timestamp)</value><value>RESOLUTIONDATE (timestamp)</value></property><property name="Statistics"><value>Node Output Rows: 1320</value><value>Node Next Batch Process Time: 8</value><value>Node Cumulative Next Batch Process Time: 1</value><value>Node Cumulative Process Time: 8</value><value>Node Next Batch Calls: 2</value><value>Node Blocks: 1</value></property><property name="Cost Estimates"><value>Estimated Node Cardinality: -1.0</value></property><property name="Query"><value>SELECT g_0.CREATED, g_0.RESOLUTIONDATE FROM tjiradb_D1_VDB_DSModel.tjiradb.jiraissue AS g_0 WHERE g_0.RESOLUTIONDATE IS NULL</value></property><property name="Model Name"><value>tjiradb_D1_VDB_DSModel</value></property></node></property><property name="Select Columns"><value>TIMESTAMPDIFF(SQL_TSI_MINUTE, jiraissue_sub.CREATED, {ts'2014-10-03 00:00:00.0'}) AS CalculatedField1</value><value>jiraissue_sub.RESOLUTIONDATE AS jiraissue_RESOLUTIONDATE</value><value>jiraissue_sub.CREATED AS jiraissue_CREATED</value><value>TIMESTAMPDIFF(SQL_TSI_MINUTE, jiraissue_sub.CREATED, {ts'2014-10-03 00:00:00.0'}) AS CalculatedField11</value></property></node></property><property name="Select Columns"><value>CalculatedField1_Sub.CalculatedField1</value><value>CalculatedField1_Sub.jiraissue_RESOLUTIONDATE</value><value>CalculatedField1_Sub.jiraissue_CREATED</value><value>CalculatedField1_Sub.CalculatedField11</value><value>IFNULL(convert(CalculatedField1_Sub.jiraissue_RESOLUTIONDATE, string), '-2147483648')</value><value>IFNULL(convert(CalculatedField1_Sub.jiraissue_CREATED, string), '-2147483648')</value></property></node></property><property name="Join Strategy"><value>MERGE JOIN (ALREADY_SORTED/SORT_DISTINCT)</value></property><property name="Join Type"><value>LEFT OUTER JOIN</value></property><property name="Join Criteria"><value>IFNULL(convert(jiraissue.RESOLUTIONDATE, string), '-2147483648')=IFNULL(convert(CalculatedField1_Sub.jiraissue_RESOLUTIONDATE, string), '-2147483648')</value><value>IFNULL(convert(jiraissue.CREATED, string), '-2147483648')=IFNULL(convert(CalculatedField1_Sub.jiraissue_CREATED, string), '-2147483648')</value></property></node></property><property name="Select Columns"><value>jiraissue.RESOLUTIONDATE AS jiraissue_RESOLUTIONDATE</value><value>jiraissue.CREATED AS jiraissue_CREATED</value><value>CalculatedField1_Sub.CalculatedField1 AS CalculatedField1</value></property></node></property><property name="Sort Mode"><value>DUP_REMOVE</value></property></node></property><property name="Row Offset"><value>null</value></property><property name="Row Limit"><value>10</value></property></node> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3254) Add supporting capabilities

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3254?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3254. --------------------------------- > Add supporting capabilities > --------------------------- > > Key: TEIID-3254 > URL: https://issues.jboss.org/browse/TEIID-3254 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > With spreadsheet queries LIKE is not supported in UPDATE/DELETE and only simple values are supported in the update change set. > We should add capabilities to account for these restrictions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3322) Add Connect BY Feature supported by Oracle

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3322?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3322. --------------------------------- > Add Connect BY Feature supported by Oracle > ------------------------------------------ > > Key: TEIID-3322 > URL: https://issues.jboss.org/browse/TEIID-3322 > Project: Teiid > Issue Type: Feature Request > Reporter: Van Halbert > Assignee: Steven Hawkins > > Would like to request for an enhancement to extend the support functionality of CONNECT BY that is available in Oracle. WHen comes to tranversing hierarchy this feature is very useful and powerful. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015