January 2016 - 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 reassigned TEIID-3931: ------------------------------------- Fix Version/s: 9.x (was: 9.0) Assignee: (was: Steven Hawkins) This will be difficult to do as Teiid currently has a single geometry type value - olingo needs to use a specific subtype instead. We can emulate this somewhat by using extension metadata when creating the edm metadata - however all of the other logic paths are just based upon passing the teiid type (and not the column) which would be required to determine the proper odata type. > Add support for odata service geospatial handling > ------------------------------------------------- > > Key: TEIID-3931 > URL: https://issues.jboss.org/browse/TEIID-3931 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Fix For: 9.x > > > 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 (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3909) Add support for odata translator geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3909?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3909. ----------------------------------- Resolution: Done Added support at the translator level by mapping all geometry types to our geometry type. We do not yet have support for geography (which looks like we would need to integrate the full geotools suite to support). The metadata import will set the appropriate srid and type in the geometry_columns table. A bit of messiness is the conversion in and out of the olingo string/type representation is handled through forked classes - one from JTS (to alter the string logic since odata does not use WKT) and one from olingo (to minimize dependencies). > Add support for odata translator geospatial handling > ---------------------------------------------------- > > Key: TEIID-3909 > URL: https://issues.jboss.org/browse/TEIID-3909 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > 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 (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3909) Add support for odata translator geospatial handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3909?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3909: ---------------------------------- Summary: Add support for odata translator geospatial handling (was: Add support for odata geospatial handling) Switching the issue to be specific to the translator. > Add support for odata translator geospatial handling > ---------------------------------------------------- > > Key: TEIID-3909 > URL: https://issues.jboss.org/browse/TEIID-3909 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > 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 (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3931: ------------------------------------- Summary: Add support for odata service geospatial handling Key: TEIID-3931 URL: https://issues.jboss.org/browse/TEIID-3931 Project: Teiid Issue Type: Bug Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0 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 (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3871) moving documentation from confluence to gitbook

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3871?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3871: --------------------------------------- They should all be read only now, thanks. > moving documentation from confluence to gitbook > ------------------------------------------------- > > Key: TEIID-3871 > URL: https://issues.jboss.org/browse/TEIID-3871 > Project: Teiid > Issue Type: Task > Components: Documentation > Affects Versions: 9.x > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.x > > > From Teiid DV 7 F2F Notes, > " In the Teiid 9.x timeframe we should look toward moving everything to gitbook / markdown. We should start by migrating the documentation and solicit help with the website if possible." > This issue will address this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3869) Enable Teiid to be exposed as a GIS compliant data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3869?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3869: ---------------------------------- Fix Version/s: 9.0 8.12.5 This has also been pulled into 8.12.5. The initial work of support for geoserver should now be considered done - except for the documentation of the new functions. > Enable Teiid to be exposed as a GIS compliant data source > --------------------------------------------------------- > > Key: TEIID-3869 > URL: https://issues.jboss.org/browse/TEIID-3869 > Project: Teiid > Issue Type: Feature Request > Components: Grammar, JDBC Driver, OData, ODBC > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > See > http://www.esri.com/~/media/Files/Pdfs/library/whitepapers/pdfs/supported... > WMS - http://www.opengeospatial.org/standards/wms > WFS - http://www.opengeospatial.org/standards/wfs > Using MapViewer to show maps based on WMS services. The WMS services are provided by a GeoServer like ArcGIS or GeoServer. > OData has also some capabilities in the Geo space especially on the .Net libraries side. > See http://www.odata.org/libraries/ for Microsoft.Spatial (OData v4) and System.Spatial (OData v1-3) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3912: --------------------------------------- Pulled into 8.12.5, but minimized the changes - that is keep most of the existing assembly logic. This was needed as this change became the basis for future fixes in master. > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 9.0, 8.12.5 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3912) Centralize type handling for odata4

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3912?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3912: ---------------------------------- Fix Version/s: 8.12.5 > Centralize type handling for odata4 > ----------------------------------- > > Key: TEIID-3912 > URL: https://issues.jboss.org/browse/TEIID-3912 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.13, 9.0, 8.12.5 > > > There is similar type handling logic in both the server odata4 and translator odata4 modules. This should be combined to remove duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3816) Informix translator - <> ALL is translated as NOT IN - this statement seem to not work in Infromix

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3816?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3816: ------------------------------- Fix Version/s: 8.12.x > Informix translator - <> ALL is translated as NOT IN - this statement seem to not work in Infromix > -------------------------------------------------------------------------------------------------- > > Key: TEIID-3816 > URL: https://issues.jboss.org/browse/TEIID-3816 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.2.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.x > > > Query: > {code:sql} > SELECT INTKEY, BOOLEANVALUE FROM BQT1.SMALLA WHERE BOOLEANVALUE <> ALL (SELECT BOOLEANVALUE FROM BQT1.SMALLA WHERE INTKEY = 40) > {code} > Source-specific command: > {code:sql} > SELECT g_0.IntKey, g_0.BooleanValue FROM Source.SmallA AS g_0 WHERE g_0.BooleanValue NOT IN (SELECT g_1.BooleanValue FROM Source.SmallA AS g_1 WHERE g_1.IntKey = 40) > {code} > *Note: boolean value for row where Intkey = 40 is false.* > Expected result: > |intkey|booleanvalue| > |1|true| > |...|...| > Actual result: > |intkey|booleanvalue| > |1|false| > |...|...| > This seems to be an Informix issue as neither '<> ALL' nor 'NOT IN' works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3270) Allow UDFs to call Teiid functions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3270?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3270: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1295461|https://bugzilla.redhat.com/show_bug.cgi?id=1295461] from NEW to MODIFIED > Allow UDFs to call Teiid functions > ---------------------------------- > > Key: TEIID-3270 > URL: https://issues.jboss.org/browse/TEIID-3270 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Fix For: 8.13, 8.12.4 > > > Currently custom functions require the implementation on be in Java, there could be an alternative way to allow using Teiid expressions inside the custom functions. The related thread is here- > https://developer.jboss.org/thread/251179 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2016