September 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3931) Add support for odata service geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3931. ----------------------------------- Resolution: Done Added as much of an initial implementation as possible at this time. To make this fully robust we need geography support and the odata issues fixed. > Add support for odata service geospatial handling > ------------------------------------------------- > > Key: TEIID-3931 > URL: https://issues.jboss.org/browse/TEIID-3931 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5482) Dynamic SQL: Executing Dynamic SQL Throws an Error

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5482?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5482. ----------------------------------- Resolution: Rejected It is likely using executeQuery, which won't work as the first query does not return a result set. Teiid currently expects the result set of dynamic sql in an anonymous procedure block to be declared just like the second example. Running locally I see the TeiidSQLException: TEIID30490 The query does not return a result set, executeQuery should not be used. > Dynamic SQL: Executing Dynamic SQL Throws an Error > -------------------------------------------------- > > Key: TEIID-5482 > URL: https://issues.jboss.org/browse/TEIID-5482 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 11.1 > Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > > When running the following query: > {code:sql} > BEGIN > declare clob sql_query = 'select 1'; > execute immediate sql_query; > END ;; > {code} > in result set can see only: > {code:noformat} > Error: 0 > SQLState: 38000 > ErrorCode: 0 > {code} > but running the following query just adding the "as cnt string": > {code:sql} > BEGIN > declare clob sql_query = 'select 1'; > execute immediate sql_query as cnt string; > END ;; > {code} > can see correct "1" in result set. I don't know if it's a correct behavior, maybe it's related to how SQuirrel handles result set. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3931) Add support for odata service geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3931 at 9/21/18 9:37 AM: ---------------------------------------------------------------- The initial changes are in. The biggest issues are around the srid handling. One more refinement would be good to expose a geometry with 4326 as a geography type - however this cannot be done as geographic function evaluation will differ from what jts can produce. was (Author: shawkins): The initial changes are in. The biggest issues are around the srid handling. One more refinement would be good to expose a geometry with 4326 as a geography type. > Add support for odata service geospatial handling > ------------------------------------------------- > > Key: TEIID-3931 > URL: https://issues.jboss.org/browse/TEIID-3931 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3931) Add support for odata service geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3931: --------------------------------------- The initial changes are in. The biggest issues are around the srid handling. One more refinement would be good to expose a geometry with 4326 as a geography type. > Add support for odata service geospatial handling > ------------------------------------------------- > > Key: TEIID-3931 > URL: https://issues.jboss.org/browse/TEIID-3931 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3931) Add support for odata service geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-3931 at 9/21/18 9:20 AM: ---------------------------------------------------------------- Here's a running list of Olingo issues: 1. toString of Geospatial value types should use lower case type dimension names. This is not a severe issue - it looks like only Point implements toString and generally this is only for debug. 2. Polygon should support multiple interior holes. https://issues.apache.org/jira/browse/OLINGO-1294 3. The srid should optionally be associated with the value in json output - https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67... Otherwise VARIABLE support is not possible. https://issues.apache.org/jira/browse/OLINGO-1293 4. The url parser requires an srid (because it's based upon the string to value type logic). This by itself is not an issue as it's required by their grammar - https://docs.oasis-open.org/odata/odata/v4.0/os/abnf/odata-abnf-construct... 3/4 Together mean that any creation of value object from string parsing is then not valid for json output. 5. srid is not included in xml/json metadata MetadataDocument*Serializer - it is only included in type definitions in json metadata, but that is unlikely to be utilized. https://issues.apache.org/jira/browse/OLINGO-1292 was (Author: shawkins): Here's a running list of Olingo issues: 1. toString of Geospatial value types should use lower case type names 2. Polygon should support multiple interior holes. 3. The srid should optionally be associated with the value in json output - https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67... Otherwise VARIABLE support is not possible. 4. The url parser requires an srid (because it's based upon the string to value type logic). 3/4 Together mean that any creation of value object from string parsing is then not valid for json output. 5. srid is not included in xml/json metadata MetadataDocument*Serializer - it is only included in type definitions in json metadata, but that is unlikely to be utilized. > Add support for odata service geospatial handling > ------------------------------------------------- > > Key: TEIID-3931 > URL: https://issues.jboss.org/browse/TEIID-3931 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5482) Dynamic SQL: Executing Dynamic SQL Throws an Error

by dalex dalex (JIRA)

dalex dalex created TEIID-5482: ---------------------------------- Summary: Dynamic SQL: Executing Dynamic SQL Throws an Error Key: TEIID-5482 URL: https://issues.jboss.org/browse/TEIID-5482 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 11.1 Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) Reporter: dalex dalex Assignee: Steven Hawkins When running the following query: {code:sql} BEGIN declare clob sql_query = 'select 1'; execute immediate sql_query; END ;; {code} in result set can see only: {code:noformat} Error: 0 SQLState: 38000 ErrorCode: 0 {code} but running the following query just adding the "as cnt string": {code:sql} BEGIN declare clob sql_query = 'select 1'; execute immediate sql_query as cnt string; END ;; {code} can see correct "1" in result set. I don't know if it's a correct behavior, maybe it's related to how SQuirrel handles result set. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3931) Add support for odata service geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3931: --------------------------------------- Here's a running list of Olingo issues: 1. toString of Geospatial value types should use lower case type names 2. Polygon should support multiple interior holes. 3. The srid should optionally be associated with the value in json output - https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67... Otherwise VARIABLE support is not possible. 4. The url parser requires an srid (because it's based upon the string to value type logic). 3/4 Together mean that any creation of value object from string parsing is then not valid for json output. 5. srid is not included in xml/json metadata MetadataDocument*Serializer - it is only included in type definitions in json metadata, but that is unlikely to be utilized. > Add support for odata service geospatial handling > ------------------------------------------------- > > Key: TEIID-3931 > URL: https://issues.jboss.org/browse/TEIID-3931 > Project: Teiid > Issue Type: Enhancement > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5477) Incorrect results with lead/lag over windows with duplicates

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5477?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5477: --------------------------------- Fix Version/s: 8.12.16.6_4 > Incorrect results with lead/lag over windows with duplicates > ------------------------------------------------------------ > > Key: TEIID-5477 > URL: https://issues.jboss.org/browse/TEIID-5477 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2, 11.1.1, 11.0.3, 10.3.5, 8.12.16.6_4 > > > LEAD/LAG should be computed as row values functions, rather than over a range. > for example: > select e1, lead(e1, 2) over (order by e1 nulls last) from pm1.g1 > returns three rows of ('a', 'c') - rather than the expected ('a', 'a'), ('a', 'b'), ('a', 'c') -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5439) Batch removed during large internal materialization load

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5439?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5439: --------------------------------- Fix Version/s: 8.12.16.6_4 > Batch removed during large internal materialization load > -------------------------------------------------------- > > Key: TEIID-5439 > URL: https://issues.jboss.org/browse/TEIID-5439 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1, 10.3.4, 11.0.2, 8.12.16.6_4 > > > For a sufficiently large materialization, such as 33000000 rows by 10 columns of biginteger/string types, the load will not complete and instead produce an exception: > {code} > ERROR: TEIID30019 Unexpected exception for request yGKKEfVoiD5O.0 > org.teiid.core.TeiidRuntimeException: Batch removed > at org.teiid.query.tempdata.TempTableDataManager.rethrow(TempTableDataManager.java:880) > at org.teiid.query.tempdata.TempTableDataManager.access$800(TempTableDataManager.java:92) > at org.teiid.query.tempdata.TempTableDataManager$4.load(TempTableDataManager.java:625) > at org.teiid.query.tempdata.TempTableDataManager$4.createTupleSource(TempTableDataManager.java:548) > at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:108) > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:401) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:141) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:492) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5013) Google Spreadsheet Data Sources with custom client_id and client_secret

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5013?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5013: --------------------------------- Fix Version/s: 8.12.16.6_4 > Google Spreadsheet Data Sources with custom client_id and client_secret > ----------------------------------------------------------------------- > > Key: TEIID-5013 > URL: https://issues.jboss.org/browse/TEIID-5013 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.x > Environment: JDV6.3 / Teiid 8.12 / Teiid Desinger 10.0.1 > Reporter: Hiroki Daicho > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.3, 8.12.16.6_4 > > > When getting an OAuth Refresh Token, it needs to use a fixed client_id and client_secret such as > "217138521084.apps.googleusercontent.com" and "gXQ6-lOkEjE1lVcz7giB4Poy". > Currently, no way to change another client_id/client_secret. > It had better to be able to use the client_id/client_secret from each google account. > - Teiid 8.13 : Getting an OAuth Refresh Token > https://docs.jboss.org/author/display/teiid813final/Google+Spreadsheet+Da... > - Teiid 9.3 : Getting an OAuth Refresh Token > https://teiid.gitbooks.io/documents/content/v/9.3.x/admin/Google_Spreadsh... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2018