May 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3624) No way to associate enterprise data types in dynamic vdb constructs

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIID-3624?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIID-3624: ------------------------------------- I understand there is no need to have the notion of enterprise datatypes (EDT) once the metadata is loaded. Looking at it from a user standpoint... assuming EDT's are beneficial, making them as transparent and useful as possible does make sense. So if we provide any framework in the tooling to create/manage and use EDT's during the modeling process, it makes sense that users will want to interrogate the runtime "schema" and still see their enterprise types. Not sure we can do this if we don't support enterprise types within DDL column definitions. > No way to associate enterprise data types in dynamic vdb constructs > ------------------------------------------------------------------- > > Key: TEIID-3624 > URL: https://issues.jboss.org/browse/TEIID-3624 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.0 > > > I don't find any doc's on how to define enterprise data types in a dynamic vdb. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4188) Anonymous SSL connection fail with IBM JDK

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4188?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4188. ----------------------------------- Fix Version/s: 9.0 Resolution: Done Expanded the note in the security guide and added a note in the client guide. > Anonymous SSL connection fail with IBM JDK > ------------------------------------------ > > Key: TEIID-4188 > URL: https://issues.jboss.org/browse/TEIID-4188 > Project: Teiid > Issue Type: Bug > Components: Documentation > Environment: IBM JDK 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.0 > > > Anonymous SSL connection fails if with IBM JDK. > I have found similar bug TEIID-1488. It would be nice to have a note in the documentation, e.g. in _Teiid Server Transport Security_ or in _SSL Client Connections_ (or both?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4189) Allow ndv calculation to consider types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4189?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4189. ----------------------------------- Resolution: Done Added a type consideration for boolean/byte. > Allow ndv calculation to consider types > --------------------------------------- > > Key: TEIID-4189 > URL: https://issues.jboss.org/browse/TEIID-4189 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > For columns that lack ndv values, we should use the type as hint. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4189) Allow ndv calculation to consider types

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4189: ------------------------------------- Summary: Allow ndv calculation to consider types Key: TEIID-4189 URL: https://issues.jboss.org/browse/TEIID-4189 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 For columns that lack ndv values, we should use the type as hint. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4186) Prevent partial aggregate pushdown based upon type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4186?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4186. ----------------------------------- Resolution: Done Added a check when processing non-equijoin columns to look for limited value range types. > Prevent partial aggregate pushdown based upon type > -------------------------------------------------- > > Key: TEIID-4186 > URL: https://issues.jboss.org/browse/TEIID-4186 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > For limited value types, such as boolean or byte, there is little value in their use as grouping columns and should be avoided - even if distinct value counts are not available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4184) Timestamps need to be submitted without supporting {ts} for OSI PI translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4184?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4184: ---------------------------------- Fix Version/s: 8.12.5 > Timestamps need to be submitted without supporting {ts} for OSI PI translator > ----------------------------------------------------------------------------- > > Key: TEIID-4184 > URL: https://issues.jboss.org/browse/TEIID-4184 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Al S > Assignee: Steven Hawkins > Priority: Minor > Labels: osisoft-pi > Fix For: 9.0, 8.12.5 > > > Queries with OSI PI translator insert a {ts} when passing timestamps but the PI SQL engine does not handle this well. > Example model query: > select "tag","time","value" from "schema-name"."picomp2" > Example query against Teiid schema: > select * from IceDataThree where tag='sinusoid' and timecol>'2016-01-01 00:00:00' > Translation: > SELECT TOP 1000 g_0."tag" AS c_0, g_0."time" AS c_1, g_0."value" AS c_2 FROM "piarchive"."picomp2" AS g_0 > 02.WHERE g_0."tag" = 'sinusoid' AND g_0."time" > {ts '2016-04-20 00:00:00.0'} > Error: > 20:02:57,250 WARN [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue21) sV28Up1 > 02.GiGOM Connector worker process failed for atomic-request=sV28Up1GiGOM.2.0.3: org > 03..teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error exe > 04.cuting statement(s): [SQL: SELECT TOP 1000 g_0."tag" AS c_0, g_0."time" AS c_1, > 05.g_0."value" AS c_2 FROM "piarchive"."picomp2" AS g_0 WHERE g_0."tag" = 'sinusoid > 06.' AND g_0."time" > {ts '2016-04-20 00:00:00.0'}] > Caused by: com.osisoft.rdsa.RdsaException: [PIOLEDB] [SQL Parser] [Line 1] Synta > 48.x error near 'ts'. > If the translation were to simply remove the "ts" part the query would work: > SELECT TOP 1000 g_0."tag" AS c_0, g_0."time" AS c_1, g_0."value" AS c_2 FROM "piarchive"."picomp2" AS g_0 > WHERE g_0."tag" = 'sinusoid' AND g_0."time" > '2016-04-20 00:00:00.0' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4188) Anonymous SSL connection fail with IBM JDK

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4188?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4188: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1332800 Bugzilla Update: Perform > Anonymous SSL connection fail with IBM JDK > ------------------------------------------ > > Key: TEIID-4188 > URL: https://issues.jboss.org/browse/TEIID-4188 > Project: Teiid > Issue Type: Bug > Components: Documentation > Environment: IBM JDK 1.7 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Minor > > Anonymous SSL connection fails if with IBM JDK. > I have found similar bug TEIID-1488. It would be nice to have a note in the documentation, e.g. in _Teiid Server Transport Security_ or in _SSL Client Connections_ (or both?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4188) Anonymous SSL connection fail with IBM JDK

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4188: ----------------------------------- Summary: Anonymous SSL connection fail with IBM JDK Key: TEIID-4188 URL: https://issues.jboss.org/browse/TEIID-4188 Project: Teiid Issue Type: Bug Components: Documentation Environment: IBM JDK 1.7 Reporter: Juraj Duráni Assignee: Steven Hawkins Priority: Minor Anonymous SSL connection fails if with IBM JDK. I have found similar bug TEIID-1488. It would be nice to have a note in the documentation, e.g. in _Teiid Server Transport Security_ or in _SSL Client Connections_ (or both?). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator

by Al S (JIRA)

[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ] Al S updated TEIID-4187: ------------------------ Description: Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. 1) Import table valued functions as Teiid procedures 2) Allow the pushdown of nested table joins 3) Update the PI translator to use the CROSS APPLY syntax. 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this? Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. was: Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. 1) Import table valued functions as Teiid procedures 2) Allow the pushdown of nested table joins 3) Update the PI translator to use the CROSS APPLY syntax. Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. > Extend support for PI OLEDB Enterprise Queries in OSI PI Translator > ------------------------------------------------------------------- > > Key: TEIID-4187 > URL: https://issues.jboss.org/browse/TEIID-4187 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Al S > Assignee: Steven Hawkins > Priority: Minor > Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf > > > Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. > Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. > 1) Import table valued functions as Teiid procedures > 2) Allow the pushdown of nested table joins > 3) Update the PI translator to use the CROSS APPLY syntax. > 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this? > Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator

by Al S (JIRA)

Al S created TEIID-4187: --------------------------- Summary: Extend support for PI OLEDB Enterprise Queries in OSI PI Translator Key: TEIID-4187 URL: https://issues.jboss.org/browse/TEIID-4187 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.13.3 Reporter: Al S Assignee: Steven Hawkins Priority: Minor Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. 1) Import table valued functions as Teiid procedures 2) Allow the pushdown of nested table joins 3) Update the PI translator to use the CROSS APPLY syntax. Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2016