[JBoss JIRA] (TEIID-3352) Can't cast from decimal to boolean in postgresql
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3352:
-------------------------------------
Summary: Can't cast from decimal to boolean in postgresql
Key: TEIID-3352
URL: https://issues.jboss.org/browse/TEIID-3352
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 7.7
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.11
We can't cast directly to boolean in postgresql from decimal. The Teiid conversion assume anything that isn't 0 is true (matches h2 and other handling).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (TEIID-3290) Auto generated REST WAR truncates the larger payloads
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3290?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3290:
------------------------------------------------
Filip Elias <felias(a)redhat.com> changed the Status of [bug 1185024|https://bugzilla.redhat.com/show_bug.cgi?id=1185024] from ON_QA to VERIFIED
> 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, 2 months
[JBoss JIRA] (TEIID-3351) Quick Start "dynamicvdb-datafederation" needlessly made complicated
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-3351:
-----------------------------------
Summary: Quick Start "dynamicvdb-datafederation" needlessly made complicated
Key: TEIID-3351
URL: https://issues.jboss.org/browse/TEIID-3351
Project: Teiid
Issue Type: Quality Risk
Reporter: Ramesh Reddy
Assignee: Van Halbert
The "dynamicvdb-datafederation" example in the Quick Starts example is needlessly made complicated. Originally this is designed to have one File and RDBMS source, to show a simple data integration through Teiid.
Now, it has
- Excel integration
- Materialization Example
- more models
I am not opposed to having these features shown in an example, however not in this example. This needs to be as simple as possible to show a quick introduction to the Teiid. Please move these into separate quick starts.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[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 edited comment on TEIID-3300 at 2/23/15 3:31 PM:
----------------------------------------------------------------
lookup is routed to the ProcessorDataManager, so it only has a stub function method. Also since it's materialized with a primary key it's effectively redundant to use lookup.
You could use the internal Connection that is provided by CommandContext - add the CommandContext as the first function parameter and use CommandContext.getConnection to execute the equivalent prepared statements.
was (Author: shawkins):
lookup is routed to the ProcessorDataManager, so it only has a stub function method. Also since it's materialized with a primary key it's effectively redundant to use lookup.
You could use the internal Connection that is provided by CommandContext - add the CommandContext as the first paremeter and used CommandContext.getConnection to execute the equivalent prepared statements.
> Add SPATIAL_REF_SYS table
> -------------------------
>
> Key: TEIID-3300
> URL: https://issues.jboss.org/browse/TEIID-3300
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Labels: spatial
> Fix For: 8.10
>
>
> 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, 2 months
[JBoss JIRA] (TEIID-3316) MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB 2.4.8 using Teiid 8.9.1
by Ivan Chan (JIRA)
[ https://issues.jboss.org/browse/TEIID-3316?page=com.atlassian.jira.plugin... ]
Ivan Chan commented on TEIID-3316:
----------------------------------
Thanks
> MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB 2.4.8 using Teiid 8.9.1
> --------------------------------------------------------------------------------------------------
>
> Key: TEIID-3316
> URL: https://issues.jboss.org/browse/TEIID-3316
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.9.1
> Environment: Teiid 8.9.1 with MongoDB shell version: 2.4.8 using MongoDB Driver mongo-java-driver-2.12.3.jar
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.10
>
>
> I am getting the following erroe when connecting to MongoDB using Teiid 8.9.1:
> Caused by: com.mongodb.CommandFailureException: { "serverUsed" : "donetsk:27017" , "ok" : 0.0 , "errmsg" : "unrecognized field \"cursor"}
> at com.mongodb.CommandResult.getException(CommandResult.java:76)
> at com.mongodb.CommandResult.throwOnError(CommandResult.java:131)
> at com.mongodb.DBCollectionImpl.aggregate(DBCollectionImpl.java:100)
> at com.mongodb.DBCollection.aggregate(DBCollection.java:1571)
> at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:111)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (TEIID-3316) MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB 2.4.8 using Teiid 8.9.1
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3316?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3316:
-------------------------------------
should later this week, but you can build locally test if you want, as the git branch for 8.10.x is created
> MongoDB: Getting "unrecognized field \"cursor" when connecting to MongoDB 2.4.8 using Teiid 8.9.1
> --------------------------------------------------------------------------------------------------
>
> Key: TEIID-3316
> URL: https://issues.jboss.org/browse/TEIID-3316
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.9.1
> Environment: Teiid 8.9.1 with MongoDB shell version: 2.4.8 using MongoDB Driver mongo-java-driver-2.12.3.jar
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.10
>
>
> I am getting the following erroe when connecting to MongoDB using Teiid 8.9.1:
> Caused by: com.mongodb.CommandFailureException: { "serverUsed" : "donetsk:27017" , "ok" : 0.0 , "errmsg" : "unrecognized field \"cursor"}
> at com.mongodb.CommandResult.getException(CommandResult.java:76)
> at com.mongodb.CommandResult.throwOnError(CommandResult.java:131)
> at com.mongodb.DBCollectionImpl.aggregate(DBCollectionImpl.java:100)
> at com.mongodb.DBCollection.aggregate(DBCollection.java:1571)
> at org.teiid.translator.mongodb.MongoDBQueryExecution.execute(MongoDBQueryExecution.java:111)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (TEIID-3260) Create custom metadata repository that uses Modeshape
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIID-3260?page=com.atlassian.jira.plugin... ]
Barry LaFond commented on TEIID-3260:
-------------------------------------
Fundamentally, the node structure for the *VDB* metadata will be identical for both *library* or *workspace* modes. Only real difference will be in the lock/access restrictions. How the nodes and properties are actually accessesed and edited is an implementation layer. Designer is designing one version of it for "Design-time". No reason why Teiid Metadata Factory couldn't write their own layer based on your runtime behavior/characteristics.
You'd have to look at our editing layer which involves relational-like objects (Table, Column, Procedure, etc...) that provide convenience methods for getting/setting/adding/removing that delegate to the JCR/MS layer without holding any state information other than the repository PATH string value. Keeps it light weight. (Interfaces and Impl's are here: https://github.com/Teiid-Designer/komodo/tree/master/plugins/org.komodo.r...)
The CNDs and sequencers for the VDB, Teiid DDL and SQL components of the VDB artifacts, in theory, should be maintained and kept in sync with BNF and vdb-deployer.xsd schema. These CND's and corresponding sequencers are the bread and butter of what Modeshape provides. To date, this work has been by tooling. If you wish to take ownership of those components from a Teiid Project perspective, that'd be great as long as it's exposed, accessible and integratable from the Komodo Tooling perspective.
> Create custom metadata repository that uses Modeshape
> -----------------------------------------------------
>
> Key: TEIID-3260
> URL: https://issues.jboss.org/browse/TEIID-3260
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 8.10
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Create a custom metadata repository implementation that uses ModeShape as the repository for obtaining the VDB metadata for deployment.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (TEIID-3300) Add SPATIAL_REF_SYS table
by Tom Arnold (JIRA)
[ https://issues.jboss.org/browse/TEIID-3300?page=com.atlassian.jira.plugin... ]
Tom Arnold commented on TEIID-3300:
-----------------------------------
Steve, how can I lookup values from this table in a system function? I'm trying to do something like this...
{code}
public static GeometryType transform(GeometryType geom, int srid) {
String srcParams = lookup('spatial_ref_sys', 'proj4text','srid', getSrid(geom));
String tgtParams = lookup('spatial_ref_sys', 'proj4text','srid', srid);
return transform(geom, srcParams, tgtParams);
}
{code}
> Add SPATIAL_REF_SYS table
> -------------------------
>
> Key: TEIID-3300
> URL: https://issues.jboss.org/browse/TEIID-3300
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Tom Arnold
> Assignee: Steven Hawkins
> Labels: spatial
> Fix For: 8.10
>
>
> 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, 2 months