February 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3302) Implement ST_Transform

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-3302?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-3302: ----------------------------------- Got permission from the maintainer to upload proj4j to central. Will be working on this later in the week. > Implement ST_Transform > ---------------------- > > Key: TEIID-3302 > URL: https://issues.jboss.org/browse/TEIID-3302 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: spatial > > Implement [ST_Transform|http://postgis.org/docs/ST_Transform.html] system function. This would be used to transform geometry between different coordinate systems. This needs SPATIAL_REF_SYS table and a supporting library. > There are a couple of options for implementing this: > * http://trac.osgeo.org/proj4j/ - Port of the C library used by PostGIS. Fewest dependencies and should keep us close to PostGIS in capabilities. There will be a little boilerplate to interface with JTS. > * http://docs.geotools.org/latest/userguide/library/referencing/index.html - GeoTools referencing module. I think we would need to develop a simple plugin to interface with our SPATIAL_REF_SYS table. GeoTools is active and has good docs, but brings in a lot of dependencies. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[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} but I couldn't find where mysql exposes the same information {quote} It doesn't (http://dev.mysql.com/worklog/task/?id=2378). It looks like the GeoTools MySQL module creates and manages a GEOMETRY_COLUMNS table. For now, we could place the onus on the users to do the same; i.e., try to import from table if it exists. {quote} Or we could just assume the metadata will be set and associate the column property with the result - however that will not work for anything other than a simple select. {quote} What is the concern here? The structure of the table implies that the values in a column will all have the same SRID/type/etc. I think it's possible to mix these in practice, but it's not a good idea. Will see if I can find something to back this up... > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3322) Add Connect BY Feature supported by Oracle

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3322?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3322. ----------------------------------- Resolution: Rejected See JBDVPL-101 - since we support common table expressions, we won't pursue oracle specific syntax. > Add Connect BY Feature supported by Oracle > ------------------------------------------ > > Key: TEIID-3322 > URL: https://issues.jboss.org/browse/TEIID-3322 > Project: Teiid > Issue Type: Feature Request > Reporter: Van Halbert > Assignee: Steven Hawkins > > Would like to request for an enhancement to extend the support functionality of CONNECT BY that is available in Oracle. WHen comes to tranversing hierarchy this feature is very useful and powerful. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3322) Add Connect BY Feature supported by Oracle

by Van Halbert (JIRA)

Van Halbert created TEIID-3322: ---------------------------------- Summary: Add Connect BY Feature supported by Oracle Key: TEIID-3322 URL: https://issues.jboss.org/browse/TEIID-3322 Project: Teiid Issue Type: Feature Request Reporter: Van Halbert Assignee: Steven Hawkins Would like to request for an enhancement to extend the support functionality of CONNECT BY that is available in Oracle. WHen comes to tranversing hierarchy this feature is very useful and powerful. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[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 resolved TEIID-3301. ----------------------------------- Resolution: Done Added the view based upon sys.columns and the metadata properties http://www.teiid.org/translator/spatial/2015}coord_dimension http://www.teiid.org/translator/spatial/2015}srid http://www.teiid.org/translator/spatial/2015}type Both this and the spatial ref sys will be added to docs as well. The appropriate metadata will be populated on a dynamic import as well for oracle and postgresql - but I couldn't find where mysql exposes the same information. We'll by default assume 2 coordinate dimensions, a zero SRID, and a GEOMETRY type. The last remaining metadata piece to tackle would be associating the srid on reads from the sources. For mysql we could use their internal format, for pg we could use ewkb, and oracle could use ewkt. Or we could just assume the metadata will be set and associate the column property with the result - however that will not work for anything other than a simple select. > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3319) Union with different datatypes gives error in mysql

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3319?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3319: --------------------------------------- > Teiid is adding dynamically the cast as char to the int field but the jdbc query is giving an error on mysql level (Illegal mix of collations for operation 'UNION') It's not that there's a mismatch between char and varchar - those are normally comparable. The issue is that the connections default encoding/collation is not compatible with the incidentsm1_INCIDENT_ID column. > I edited the generated jdbc query and added cast as char to both fields int and varchar, mysql executes the jdbc query without a problem. That would effectively give them the same encoding, which would resolve the issue. > I added convert to String to both union fields in Teiid sql query, but the jdbc query generated by teiid is not adding the cast to the string field. The cast would be seen as unnecessary and removed. A couple of resolutions would be to change the collation in use for your connection, change the collation in use for the column, or you could use the teiid_rel:native-query metadata property on the SDView_sub source table to manually insert a cast/convert on the incidentsm1_INCIDENT_ID column - https://docs.jboss.org/author/display/TEIID/JDBC+Translator > Union with different datatypes gives error in mysql > --------------------------------------------------- > > Key: TEIID-3319 > URL: https://issues.jboss.org/browse/TEIID-3319 > Project: Teiid > Issue Type: Bug > Reporter: Mark Tawk > Assignee: Steven Hawkins > > Hello, > I'm using Teiid 8.9.0 Alpha2 with mysql5.7 and mysql5 translator. > I have a union query with fields of different types, int and varchar. > Teiid is adding dynamically the cast as char to the int field but the jdbc query is giving an error on mysql level (Illegal mix of collations for operation 'UNION') > I edited the generated jdbc query and added cast as char to both fields int and varchar, mysql executes the jdbc query without a problem. > I added convert to String to both union fields in Teiid sql query, but the jdbc query generated by teiid is not adding the cast to the string field. > Teiid sql query: > select "ITRITPTicketsView"."ITRITPTicketsView_jiraissue_" as "ITRITPTicketsView_jiraissue_" > from ((select convert("ITRITPTicketsView_sub"."jiraissue_ID", string) as "ITRITPTicketsView_jiraissue_" from "implifyBusinessModel"."ITRITPTicketsView" "ITRITPTicketsView_sub") > union > (select convert("SDView_sub"."incidentsm1_INCIDENT_ID", string) as "SDView_incidentsm1_INCIDENT_" from "implifyBusinessModel"."SDView" "SDView_sub") > ) "ITRITPTicketsView" > LIMIT 0 , 10 > The generated error: > org.teiid.translator.jdbc.JDBCExecutionException: 1271 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: (SELECT cast(g_1.`jiraissue_ID` AS char) AS c_0 FROM `implify_view`.`ITRITPTicketsView` AS g_1) UNION (SELECT g_0.`incidentsm1_INCIDENT_ID` AS c_0 FROM `implify_view`.`SDView` AS g_0) LIMIT 10] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:151) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.sql.SQLException: Illegal mix of collations for operation 'UNION' > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1084) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4232) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4164) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2615) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2776) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2838) > at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2082) > at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2212) > at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) > at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:141) > ... 12 more > Feb 03, 2015 8:43:32 AM org.teiid.logging.JavaLogger log > WARNING: TEIID30020 Processing exception for request AxQ9XTXrAYkm.0 'TEIID30504 implify_viewModelVDB: 1271 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: (SELECT cast(g_1.`jiraissue_ID` AS char) AS c_0 FROM `implify_view`.`ITRITPTicketsView` AS g_1) UNION (SELECT g_0.`incidentsm1_INCIDENT_ID` AS c_0 FROM `implify_view`.`SDView` AS g_0) LIMIT 10]'. Originally TeiidProcessingException 'Illegal mix of collations for operation 'UNION'' SQLError.java:1084. Enable more detailed logging to see the entire stacktrace. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3321) Support Adabas as a data source

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3321?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3321: ------------------------------------- >From Teiid marketplace https://github.com/teiid-marketplace/translator-adabas > Support Adabas as a data source > ------------------------------- > > Key: TEIID-3321 > URL: https://issues.jboss.org/browse/TEIID-3321 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.11 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Support Adabas as a data source -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3321) Support Adabas as a data source

by Van Halbert (JIRA)

Van Halbert created TEIID-3321: ---------------------------------- Summary: Support Adabas as a data source Key: TEIID-3321 URL: https://issues.jboss.org/browse/TEIID-3321 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.11 Reporter: Van Halbert Assignee: Steven Hawkins Support Adabas as a data source -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3320) Use alternative implementation to Spring in CXF

by Van Halbert (JIRA)

Van Halbert created TEIID-3320: ---------------------------------- Summary: Use alternative implementation to Spring in CXF Key: TEIID-3320 URL: https://issues.jboss.org/browse/TEIID-3320 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Reporter: Van Halbert Assignee: Steven Hawkins Use an alternative implementation to Spring in CXF -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3226) Need to upgrade org.springframework to at least version 3.2.12

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3226?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3226: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1166378|https://bugzilla.redhat.com/show_bug.cgi?id=1166378] from ON_QA to VERIFIED > Need to upgrade org.springframework to at least version 3.2.12 > -------------------------------------------------------------- > > Key: TEIID-3226 > URL: https://issues.jboss.org/browse/TEIID-3226 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 8.7.1, 8.10 > > > The spring framework version that's packaged with the connector-ws needs to be upgraded from 3.0.7 to 3.1.2. -- 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 February 2015