[JBoss JIRA] (TEIID-3301) Add GEOMETRY_COLUMNS view
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-3301?page=com.atlassian.jira.plugin... ]
Tom Arnold edited comment on TEIID-3301 at 2/9/15 3:50 AM:
-----------------------------------------------------------
{quote}
Also if the geometry value is being computed by a function/expression, the resulting sql could take a performance hit as the expression will be repeated. Which is why it seems simpler to stick with the ewkb result from postgresql.
{quote}
This makes sense; I didn't really understand the problem until now. I think internal for MySQL and EWKB for Postgres is the way to go.
For Oracle I'm thinking we could use GML to get the geometry and SRID in one function. The SDO_UTIL GML function returns the SRID as an attribute. If performance is too bad we could look at providing a PL/SQL function to do EWKB conversions.
{code}
<gml:Polygon srsName="SDO:8307" xmlns:gml="http://www.opengis.net/gml">
{code}
Initial commit working on this. https://github.com/Tom9729/teiid/commit/4f1e047159f4787908289aea4a853a916...
was (Author: tom9729):
{quote}
Also if the geometry value is being computed by a function/expression, the resulting sql could take a performance hit as the expression will be repeated. Which is why it seems simpler to stick with the ewkb result from postgresql.
{quote}
This makes sense; I didn't really understand the problem until now. I think internal for MySQL and EWKB for Postgres is the way to go.
For Oracle I'm thinking we could use GML to get the geometry and SRID in one function. The SDO_UTIL GML function returns the SRID as an attribute. Unfortunately the JTS reader doesn't use this, so we would have to do a regex to grab it for now. If performance is too bad we could look at providing a PL/SQL function to do EWKB conversions.
{code}
<gml:Polygon srsName="SDO:8307" xmlns:gml="http://www.opengis.net/gml">
{code}
> 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
> Fix For: 8.10
>
>
> 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, 4 months
[JBoss JIRA] (TEIID-3291) Support Amazon Relational Database Service (RDS) as a data source
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3291?page=com.atlassian.jira.plugin... ]
Kylin Soong commented on TEIID-3291:
------------------------------------
If we create RDS DB instance, for example mysql, we will get a url, user, password like below
URL - teiid.cdlkhb4ez8wd.us-west-2.rds.amazonaws.com:3306
user - username
password - ***
these parameters are enough for teiid-jdbc translator to work. In other words, current teiid support RDS as a data source, so what do we need to do in this issue?
> Support Amazon Relational Database Service (RDS) as a data source
> -----------------------------------------------------------------
>
> Key: TEIID-3291
> URL: https://issues.jboss.org/browse/TEIID-3291
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.10
> Reporter: Van Halbert
> Assignee: Kylin Soong
> Fix For: Open To Community
>
>
> Amazon Relational Database Service (Amazon RDS) is a web service that makes it easy to set up, operate, and scale a relational database in the cloud.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIID-3043) Build a Docker image based kit for Teiid
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3043?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3043.
---------------------------------
Labels: CR1 (was: )
Resolution: Done
Every time the Teiid is built, the "build/target/teiid-${vresion}" directory will have the couple script files for building an image for Teiid runtime. Run the "build-image.sh" file to build the Teiid docker image. It also provides the option to upload the image Docker Hub. Teiid team needs to push once every release.
For JBoss branded Docker images building is located here [https://github.com/jboss-dockerfiles/teiid], however I found this is not optimal for building per the current Teiid build. A similar Dockerfile needs to be developed once every release and provided there.
> Build a Docker image based kit for Teiid
> ----------------------------------------
>
> Key: TEIID-3043
> URL: https://issues.jboss.org/browse/TEIID-3043
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: CR1
> Fix For: 8.10
>
>
> Build a Docker image for Teiid server, may be host it at docker.io ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 4 months
[JBoss JIRA] (TEIID-3301) Add GEOMETRY_COLUMNS view
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-3301?page=com.atlassian.jira.plugin... ]
Tom Arnold commented on TEIID-3301:
-----------------------------------
{quote}
Also if the geometry value is being computed by a function/expression, the resulting sql could take a performance hit as the expression will be repeated. Which is why it seems simpler to stick with the ewkb result from postgresql.
{quote}
This makes sense; I didn't really understand the problem until now. I think internal for MySQL and EWKB for Postgres is the way to go.
For Oracle I'm thinking we could use GML to get the geometry and SRID in one function. The SDO_UTIL GML function returns the SRID as an attribute. Unfortunately the JTS reader doesn't use this, so we would have to do a regex to grab it for now. If performance is too bad we could look at providing a PL/SQL function to do EWKB conversions.
{code}
<gml:Polygon srsName="SDO:8307" xmlns:gml="http://www.opengis.net/gml">
{code}
> 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
> Fix For: 8.10
>
>
> 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, 4 months