December 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-1091) Add remaining SQL/XML functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1091?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1091: ---------------------------------- Fix Version/s: 8.10 > Add remaining SQL/XML functions > ------------------------------- > > Key: TEIID-1091 > URL: https://issues.jboss.org/browse/TEIID-1091 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > We should add the remaining functions, xmlparse, xmlserialize, xmlroot, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1170) Support subqueries in temp table update/delete criteria

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1170?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1170. ----------------------------------- Resolution: Done Added support for all subqueries as long as the temp table has a primary key. Temp tables without a primary key will still have an issue with in/correlated subqueries. We could resolve that last deficiency by allowing the compensating procedure use the row id (which is however not currently visible). We'll address that last case when needed. > Support subqueries in temp table update/delete criteria > ------------------------------------------------------- > > Key: TEIID-1170 > URL: https://issues.jboss.org/browse/TEIID-1170 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.10 > > > Subqueries are currently not supported in temp table update/delete criteria. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1170) Support subqueries in temp table update/delete criteria

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1170?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1170: ---------------------------------- Issue Type: Enhancement (was: Feature Request) Fix Version/s: 8.10 (was: 9.0) Component/s: Query Engine > Support subqueries in temp table update/delete criteria > ------------------------------------------------------- > > Key: TEIID-1170 > URL: https://issues.jboss.org/browse/TEIID-1170 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.10 > > > Subqueries are currently not supported in temp table update/delete criteria. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2243) Add ability to configure (change default) support for nulls first/last

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2243?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2243. ----------------------------------- Assignee: Steven Hawkins Resolution: Done Added org.teiid.defaultNullOrder to allow admins to switch from LOW to HIGH, FIRST, or LAST. Did this also in the index logic in case we need to allow null equality. Generally this is helpful in emulation scenarios to ensure that ordered results match a target system. > Add ability to configure (change default) support for nulls first/last > ---------------------------------------------------------------------- > > Key: TEIID-2243 > URL: https://issues.jboss.org/browse/TEIID-2243 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 7.4.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 8.10 > > > Add the ability to configure how nulls first/last will be handled. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3247) MongoDB: Add "MinDistance" to near and nearSphere geo spatial functions

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3247: ----------------------------------- Summary: MongoDB: Add "MinDistance" to near and nearSphere geo spatial functions Key: TEIID-3247 URL: https://issues.jboss.org/browse/TEIID-3247 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.9 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.10 MongoDB version 2.6, adds extra "MinDistance" parameter to the $near and $nearSphere functions. Translator needs to reflect this change. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2243) Add ability to configure (change default) support for nulls first/last

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2243?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2243: ---------------------------------- Fix Version/s: 8.10 Will add another system property to control the default Teiid ordering. > Add ability to configure (change default) support for nulls first/last > ---------------------------------------------------------------------- > > Key: TEIID-2243 > URL: https://issues.jboss.org/browse/TEIID-2243 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 7.4.4 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 8.10 > > > Add the ability to configure how nulls first/last will be handled. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2384) Managing Spatial Data Types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2384?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2384: ---------------------------------- Forum Reference: https://community.jboss.org/message/745111, https://developer.jboss.org/message/909769 (was: https://community.jboss.org/message/745111) > Managing Spatial Data Types > --------------------------- > > Key: TEIID-2384 > URL: https://issues.jboss.org/browse/TEIID-2384 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.2 > Reporter: luca gioppo > Labels: spatial, types > > It would be useful to be able to consume data from spatial database exposing the VDB as a spatial database to other application (imagine geoserver). > TEIID could be strategic for merging georeferenced data and make it available to those systems. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2407) Support temporary table on commit behavior

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2407?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2407. ----------------------------------- Resolution: Done Updated the parser and added a new non-reserved word (preserve). The online grammar will be updated before the final release. > Support temporary table on commit behavior > ------------------------------------------ > > Key: TEIID-2407 > URL: https://issues.jboss.org/browse/TEIID-2407 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Fix For: 8.10 > > > Now that our temporary tables are transactionally aware we should support the on commit clause. > Our current default for on commit is effectively "preserve rows", which is contrary to the sql specification. We should also offer delete rows and possible drop (similar to pg sql). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3246) Support temporary table on commit behavior

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3246: ------------------------------------- Summary: Support temporary table on commit behavior Key: TEIID-3246 URL: https://issues.jboss.org/browse/TEIID-3246 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Fix For: 8.10 Now that our temporary tables are transactionally aware we should support the on commit clause. Our current default for on commit is effectively "preserve rows", which is contrary to the sql specification. We should also offer delete rows and possible drop (similar to pg sql). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3056) MongoDB: Put nested JSON documents in one single table

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3056?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3056: ------------------------------------- I am inclined to reject this, as the above can be simply done in a Teiid View, where customer and address are pulled into single view based on the relationship. > MongoDB: Put nested JSON documents in one single table > ------------------------------------------------------- > > Key: TEIID-3056 > URL: https://issues.jboss.org/browse/TEIID-3056 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: MongoDB with Teiid > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: teiid > > Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work. > I am thinking the following case. For example I have a JSON object like this: > {code} > Customer > { > _id: 1374932, > FirstName: "John", > LastName: "Doe", > Address: { > _id: 43839430, > Street: "123 Lane", > City: "New York", > State: "NY", > Zipcode: "12345" > } > } > {code} > > In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema: > {code} > CREATE FOREIGN TABLE Customer ( > CustomerId integer PRIMARY KEY, > FirstName varchar(25), > LastName varchar(25), > address__id integer, > address_Street varchar(50), > address_City varchar(25), > address_State varchar(25), > address_Zipcode varchar(6), > ) OPTIONS(UPDATABLE 'TRUE'); > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2014