October 2016 - teiid-issues - Jboss List Archives

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4187: ------------------------------------- [~jolee] Yes TEIID-4202 is required for this. > 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: Ramesh Reddy > Fix For: 9.1 > > 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)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4393) Add new Geospatial functions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4393?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4393: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1383776 Bugzilla Update: Perform > Add new Geospatial functions > ---------------------------- > > Key: TEIID-4393 > URL: https://issues.jboss.org/browse/TEIID-4393 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.12.x, 9.x > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.1 > > > Adding a list of geospatial features to be added. Used the following specification: https://portal.opengeospatial.org/files/?artifact_id=829 > st_Dimension > st_GeometryType > st_IsEmpty > st_IsSimple > st_Boundary > st_Envelope > st_X > st_Y > st_StartPoint > st_EndPoint > st_Boundary > st_Boundary > st_Length > st_NumPoints > st_PointN > st_Centroid > st_PointOnSurface > st_Area > st_ExteriorRing > st_NumInteriorRings > st_InteriorRingN > st_NumGeometries > st_GeometryN > st_IsClosed > st_Length > st_Centroid > st_PointOnSurface > st_Area > st_Within > st_Relate > st_Intersection > st_Difference > st_Union > st_SymmetricDifference > st_Buffer > st_ConvexHull -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4506) Evaluate Logstash whether it can repleace JPA + EJB + RDBMS

by Kylin Soong (JIRA)

Kylin Soong created TEIID-4506: ---------------------------------- Summary: Evaluate Logstash whether it can repleace JPA + EJB + RDBMS Key: TEIID-4506 URL: https://issues.jboss.org/browse/TEIID-4506 Project: Teiid Issue Type: Feature Request Components: Tools Affects Versions: 9.x Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.x * JPA + EJB + RDBMS + logAppender to persist logging is quite legacy way, JPA/Hibernate have performance bottleneck, it also consume high cpu and memory. * https://www.elastic.co/products/logstash are a popular logging framework used in micro service, big data area, both Wildfly Swarm and Spring boot have support it. So I think it may helpful to spend some time to investigate the Logstash, to check whether it can repleace current JPA + EJB + RDBMS way -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4012) Implement XA transaction support for Teiid ODBC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4012?page=com.atlassian.jira.plugin... ] Work on TEIID-4012 started by Steven Hawkins. --------------------------------------------- > Implement XA transaction support for Teiid ODBC > ----------------------------------------------- > > Key: TEIID-4012 > URL: https://issues.jboss.org/browse/TEIID-4012 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP6.4.0 patched to version 6.4.5, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 9.2 > > > Without XA support the pg client will hit the following error: > TEIID30020 Processing exception for request ... 'Group does not exist: pg_prepared_xacts' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4012) Implement XA transaction support for Teiid ODBC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4012?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4012: --------------------------------------- In addition to the prepared table, we'll need to implement syntax for: PREPARE TRANSACTION id COMMIT TRANSACTION id ROLLBACK TRANSACTION id > Implement XA transaction support for Teiid ODBC > ----------------------------------------------- > > Key: TEIID-4012 > URL: https://issues.jboss.org/browse/TEIID-4012 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP6.4.0 patched to version 6.4.5, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 9.2 > > > Without XA support the pg client will hit the following error: > TEIID30020 Processing exception for request ... 'Group does not exist: pg_prepared_xacts' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4470) Google spreadsheet translator execution should not require metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4470?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4470: --------------------------------------- Made a minor change use just a single metadata load per managed connection factory. The full change here would need to update the metadata - including some extension properties, such as if a header is used. But that is pretty low priority now. > Google spreadsheet translator execution should not require metadata > ------------------------------------------------------------------- > > Key: TEIID-4470 > URL: https://issues.jboss.org/browse/TEIID-4470 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Priority: Minor > Fix For: Open To Community > > > The google translator uses the connection metadata at execution time rather than just relying on name in source and other metadata. An option should be added to just use the Teiid metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4472) Add CLI scripts for standalone "HA" and "FULL-HA" configurations

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4472?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4472. ----------------------------------- Resolution: Done merged the pull request > Add CLI scripts for standalone "HA" and "FULL-HA" configurations > ---------------------------------------------------------------- > > Key: TEIID-4472 > URL: https://issues.jboss.org/browse/TEIID-4472 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 9.2 > > > Add cli scripts to configure the standalone "ha" and "full-ha" configurations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4505) Clarify JDG doc's

by Van Halbert (JIRA)

Van Halbert created TEIID-4505: ---------------------------------- Summary: Clarify JDG doc's Key: TEIID-4505 URL: https://issues.jboss.org/browse/TEIID-4505 Project: Teiid Issue Type: Task Components: Misc. Connectors Affects Versions: 9.x Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor In the JDG related doc's, clarify the following: JDG Hot Rod connector - when defining the cacheTypeMap, the pfKeyField name should correspond to a getter/setter method in the pojo. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3836) Create a quick start to demonstrate OData

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3836?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3836: ---------------------------------- Fix Version/s: 9.2 (was: 9.1) > Create a quick start to demonstrate OData > ----------------------------------------- > > Key: TEIID-3836 > URL: https://issues.jboss.org/browse/TEIID-3836 > Project: Teiid > Issue Type: Task > Components: Quick Starts > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Van Halbert > Fix For: 9.2 > > > Add a quick start to demonstrate OData api may helpful for users. > After deploy portfolio-vdb.xml successful, I test with(http://localhost:8080/odata/Portfolio.1/Stocks.StockPrices) return a error: > {code} > TEIID16011 EntitySet "Stocks.StockPrices" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4427: ---------------------------------- Fix Version/s: 9.2 (was: 9.1) (was: 9.0.5) It's not clear there is a regression here, so I'm pushing the issue into 9.2. > Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal > ----------------------------------------------------------------------------------------- > > Key: TEIID-4427 > URL: https://issues.jboss.org/browse/TEIID-4427 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.0 > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2 > > > After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server. > when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal. > If we go back to Teiid 8.11.3, the same materialized views fetch without any problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016