January 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3301) Add GEOMETRY_COLUMNS view

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3301?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3301: --------------------------------------- > I think we could implement this by storing SRID & friends as column properties, and then creating a view on SYS.COLUMNS & SYS.PROPERTIES. Yes that should be fine. > Add GEOMETRY_COLUMNS view > ------------------------- > > Key: TEIID-3301 > URL: https://issues.jboss.org/browse/TEIID-3301 > Project: Teiid > Issue Type: Feature Request > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > > Another OGC Simple Features implementation detail. Basically this is like a specialized version of SYS.COLUMNS, and would be used to support GIS software (like GeoServer). > http://www.carocoops.org/resources/doc/postgis/x321.html > {code} > CREATE TABLE GEOMETRY_COLUMNS ( > F_TABLE_CATALOG VARCHAR(256) NOT NULL, > F_TABLE_SCHEMA VARCHAR(256) NOT NULL, > F_TABLE_NAME VARCHAR(256) NOT NULL, > F_GEOMETRY_COLUMN VARCHAR(256) NOT NULL, > COORD_DIMENSION INTEGER NOT NULL, > SRID INTEGER NOT NULL, > TYPE VARCHAR(30) NOT NULL > ) > {code} > I think we could implement this by storing SRID & friends as column properties, and then creating a view on SYS.COLUMNS & SYS.PROPERTIES. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3300) Add SPATIAL_REF_SYS table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3300?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3300: --------------------------------------- With attribution we should be able to borrow the postgis sql, but our internal tables are typically not actual tables. If we could have the data as a csv dump it would be similar to other pg logic (PGCatalogMetadataStore) to create a view using texttable and mark it as materialized. This would be done with the other non-pg system tables in https://github.com/teiid/teiid/tree/master/engine/src/main/resources/org/... The system tables that just are backed by live metadata objects are implemented in DataTierManagerImpl. Do you want to make an attempt at this first, or should I add something? > Add SPATIAL_REF_SYS table > ------------------------- > > Key: TEIID-3300 > URL: https://issues.jboss.org/browse/TEIID-3300 > Project: Teiid > Issue Type: Feature Request > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > > Implement SPATIAL_REF_SYS table (from the OGC Simple Features spec). This table stores metadata about different coordinate systems and how to tranform between them. See [here|http://en.wikipedia.org/wiki/SRID] and [here|http://www.carocoops.org/resources/doc/postgis/x321.html] for details. > {code} > CREATE TABLE SPATIAL_REF_SYS > ( > SRID INTEGER NOT NULL PRIMARY KEY, > AUTH_NAME CHARACTER VARYING(256), > AUTH_SRID INTEGER, > SRTEXT CHARACTER VARYING(2048) > ) > {code} > https://raw.githubusercontent.com/postgis/postgis/svn-trunk/spatial_ref_s... > This would be used in conjunction with the GeoTools referencing module or Proj4J to transform between coordinate systems in Teiid (ST_Transform function). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3290) Auto generated REST WAR truncates the larger payloads

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3290?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-3290. --------------------------------- Labels: Beta2 (was: ) Resolution: Done During the execution of the procedure, the new routine consults the underlying metadata of the procedure for parameter types and converts them from string to target type before executing. Thus in case of XML the string will not be truncated at 4000 chars. Another lingering issue with larger payloads is, at the first stage of parameter consumption at the REST layer is still is String, that means the payload value is being materialized, which is bad in terms of memory management. Not sure how one can read stream version of parameter. > Auto generated REST WAR truncates the larger payloads > ----------------------------------------------------- > > Key: TEIID-3290 > URL: https://issues.jboss.org/browse/TEIID-3290 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Labels: Beta2 > Fix For: 8.7.1, 8.10 > > > Currently only query parameters are supported as the input parameters to the Teiid procedure in POST based call. > The POST BODY also needs to be supported to handle larger payloads in this situation as query parameters has size limitations. Currently string based query parameters are supported, but since they passed as is as strings on larger payloads the they will be subject 4000 string length restriction. > It should be possible to read metadata of the procedure and convert the string objects to respective objects before the query gets executed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3290) Auto generated REST WAR truncates the larger payloads

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3290?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3290: ------------------------------- Priority: Blocker (was: Major) > Auto generated REST WAR truncates the larger payloads > ----------------------------------------------------- > > Key: TEIID-3290 > URL: https://issues.jboss.org/browse/TEIID-3290 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.7.1, 8.10 > > > Currently only query parameters are supported as the input parameters to the Teiid procedure in POST based call. > The POST BODY also needs to be supported to handle larger payloads in this situation as query parameters has size limitations. Currently string based query parameters are supported, but since they passed as is as strings on larger payloads the they will be subject 4000 string length restriction. > It should be possible to read metadata of the procedure and convert the string objects to respective objects before the query gets executed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3305) Add system functions for GeoJSON

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-3305?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-3305: ----------------------------------- Haven't written ticket for this yet but I believe another low-hanging format is KML. Need to double-check but I believe it's basically just GML2 without the GML namespace (which can be configured in the JTS writer). Some additional areas to consider: * PostGIS has option to configure precision for floating point. * Current implementation of these functions does not support specifying the CRS. GMLWriter has support for this but the GeoJSON module would need a minor enhancement. Also it looks like the latest GeoJSON is phasing out support for this and is just telling people to use WGS84 or reproject on server. Finally, I think we need SPATIAL_REF_SYS before we can tackle this because SRID is really only useful as PK into that table; CRS needs authority name and possibly other info. > Add system functions for GeoJSON > -------------------------------- > > Key: TEIID-3305 > URL: https://issues.jboss.org/browse/TEIID-3305 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > > Add system functions to convert between GEOMETRY and GeoJSON. These will be helpful for sources that use GeoJSON (like MongoDB and RethinkDB). > Conversion will be GeometryType (WKB) ↔ JTS Geometry ↔ GeoJSON. > * https://github.com/bjornharrtell/jts2geojson > * http://geojson.org/geojson-spec.html > * http://wiki.geojson.org/GeoJSON_draft_version_5 > I don't believe these are part of the OGC spec, but it would probably be best to implement them similar to PostGIS. > * http://postgis.org/docs/ST_AsGeoJSON.html > * http://postgis.org/docs/ST_GeomFromGeoJSON.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3305) Add system functions for GeoJSON

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-3305?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-3305: ----------------------------------- {quote} Tom, I don't recall if you have a contributor agreement in place yet - https://cla.jboss.org/index.seam If not can you click through for approval. {quote} Just signed one. I believe it is awaiting approval. > Add system functions for GeoJSON > -------------------------------- > > Key: TEIID-3305 > URL: https://issues.jboss.org/browse/TEIID-3305 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > > Add system functions to convert between GEOMETRY and GeoJSON. These will be helpful for sources that use GeoJSON (like MongoDB and RethinkDB). > Conversion will be GeometryType (WKB) ↔ JTS Geometry ↔ GeoJSON. > * https://github.com/bjornharrtell/jts2geojson > * http://geojson.org/geojson-spec.html > * http://wiki.geojson.org/GeoJSON_draft_version_5 > I don't believe these are part of the OGC spec, but it would probably be best to implement them similar to PostGIS. > * http://postgis.org/docs/ST_AsGeoJSON.html > * http://postgis.org/docs/ST_GeomFromGeoJSON.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3305) Add system functions for GeoJSON

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3305?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3305: --------------------------------------- > I don't believe these are part of the OGC spec, but it would probably be best to implement them similar to PostGIS. Yes, the more format support the better. The postgis function matrix is quite helpful for quickly seeing the standard functions http://postgis.net/docs/manual-2.0/PostGIS_Special_Functions_Index.html#P... Tom, I don't recall if you have a contributor agreement in place yet - https://cla.jboss.org/index.seam If not can you click through for approval. > Add system functions for GeoJSON > -------------------------------- > > Key: TEIID-3305 > URL: https://issues.jboss.org/browse/TEIID-3305 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > > Add system functions to convert between GEOMETRY and GeoJSON. These will be helpful for sources that use GeoJSON (like MongoDB and RethinkDB). > Conversion will be GeometryType (WKB) ↔ JTS Geometry ↔ GeoJSON. > * https://github.com/bjornharrtell/jts2geojson > * http://geojson.org/geojson-spec.html > * http://wiki.geojson.org/GeoJSON_draft_version_5 > I don't believe these are part of the OGC spec, but it would probably be best to implement them similar to PostGIS. > * http://postgis.org/docs/ST_AsGeoJSON.html > * http://postgis.org/docs/ST_GeomFromGeoJSON.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3269) Oracle pushdown time formatting incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3269?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3269: --------------------------------------- > What do you mean by "invalid matches"? According to the Teiid doc and the oracle doc are F and u valid options. Invalid from a pushdown perspective as there is no corresponding Oracle formatting, thus the translator should report to not pushdown. > Oracle pushdown time formatting incorrect > ----------------------------------------- > > Key: TEIID-3269 > URL: https://issues.jboss.org/browse/TEIID-3269 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.7.1, 8.9.1, 8.10 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > Oracle formatting cannot control the number of digits displayed in the same way as Java formatting, needs to AM instead of PM, and needs better handling for ERA. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3240) Tranlator archetype creation: -Dversion option sets the version of parent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3240?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3240: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1170588|https://bugzilla.redhat.com/show_bug.cgi?id=1170588] from ON_QA to VERIFIED > Tranlator archetype creation: -Dversion option sets the version of parent > ------------------------------------------------------------------------- > > Key: TEIID-3240 > URL: https://issues.jboss.org/browse/TEIID-3240 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Juraj Duráni > Assignee: Van Halbert > > If new translator is created using command line, -Dversion option is set as version of parent project instead of version of actual translator. > pom file: > <parent> > <groupId>org.jboss.teiid</groupId> > <artifactId>connectors</artifactId> > <version>0.0.1</version> > </parent> > ... > <groupId>org.jboss.teiid.test.translator</groupId> > <artifactId>test-translator</artifactId> >  > <packaging>jar</packaging> > ... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3274) Change archetypes to create independent projects

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3274?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3274: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1178658|https://bugzilla.redhat.com/show_bug.cgi?id=1178658] from ON_QA to ASSIGNED > Change archetypes to create independent projects > ------------------------------------------------ > > Key: TEIID-3274 > URL: https://issues.jboss.org/browse/TEIID-3274 > Project: Teiid > Issue Type: Enhancement > Components: Tools > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.7.1 > > > The current archetypes were developed with the mindset of generating projects that are part of the Teiid build. However, they need to be changed so that they are generating projects that are independent, that can stand on their own without requiring Teiid jar's. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2015