July 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2716) Add Insert/update/Delete capabilities to Cassandra translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2716?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2716. --------------------------------- > Add Insert/update/Delete capabilities to Cassandra translator > ------------------------------------------------------------- > > Key: TEIID-2716 > URL: https://issues.jboss.org/browse/TEIID-2716 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.6 > > > - Provide capability to INSERT/UPDATE/DELETE > - I also find some minor issues with search columns, as Cassandra only allows criteria on the index columns -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3022) refine removed vdb handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3022?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3022. ----------------------------------- Resolution: Done Changed the logic to proactively terminate existing sessions on the removed event. > refine removed vdb handling > --------------------------- > > Key: TEIID-3022 > URL: https://issues.jboss.org/browse/TEIID-3022 > Project: Teiid > Issue Type: Quality Risk > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > > With TEIID-2105 the server will reject requests against a non-active vdb, which includes a removed vdb. This is against the original intent of allowing for lazy cleanup. We should either have a vdb remove proactively terminate all sessions and fully cleanup or we should reinstate the lazy logic. At this point it probably makes the most sense to go the first route as there is other logic (materialization management for one) now checking the vdb state and assuming that removal will invalidate the vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2958?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2958: ------------------------------------- In general we need see, when there is nested document the need for parent ID in child document if that could be removed, so this would apply to all MERGE scenarios in Teiid. One-2-One and One-2-Many Then we should add a import property to flatten out the schema structure, the real issue is when a new document is serialized, it should follow the nested structure. But if the above feature is available then this is mute, as the import metadata needs to add a extra implicit ID column to lets you join to parent table. > MongoDB: Put nested JSON documents in one single table > ------------------------------------------------------- > > Key: TEIID-2958 > URL: https://issues.jboss.org/browse/TEIID-2958 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > 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: > > Customer > { > _id: 1374932, > FirstName: "John", > LastName: "Doe", > Address: > { > _id: 43839430, > Street: "123 Lane", > City: "New York", > State: "NY", > Zipcode: "12345" > } > } > > 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: > 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'); -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2848) MongoDB: Provide Array support

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2848?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2848. --------------------------------- Labels: CR1 (was: ) Fix Version/s: 8.7.1 Resolution: Done Added support for Array data type. It will be exposed as Object[]. Updated the documentation. > MongoDB: Provide Array support > ------------------------------- > > Key: TEIID-2848 > URL: https://issues.jboss.org/browse/TEIID-2848 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.7.1, 8.8 > > > Provide array support for primitive data types in MongoDB translator. The arrays are supported but as embedded documents in the one-2-many situation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3022) refine removed vdb handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3022?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3022: ---------------------------------- Fix Version/s: 8.8 Will address in 8.8 with proactive termination of sessions. Will later look at adding back some form of lazy undeploy such that it doesn't complete until all sessions have been terminated. > refine removed vdb handling > --------------------------- > > Key: TEIID-3022 > URL: https://issues.jboss.org/browse/TEIID-3022 > Project: Teiid > Issue Type: Quality Risk > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > > With TEIID-2105 the server will reject requests against a non-active vdb, which includes a removed vdb. This is against the original intent of allowing for lazy cleanup. We should either have a vdb remove proactively terminate all sessions and fully cleanup or we should reinstate the lazy logic. At this point it probably makes the most sense to go the first route as there is other logic (materialization management for one) now checking the vdb state and assuming that removal will invalidate the vdb. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2884) Support for Amazon Elastic MapReduce

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2884?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2884: ---------------------------------- Fix Version/s: 8.9 (was: Open To Community) (was: 8.8) > Support for Amazon Elastic MapReduce > ------------------------------------ > > Key: TEIID-2884 > URL: https://issues.jboss.org/browse/TEIID-2884 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: 8.9 > > > Amazon Elastic MapReduce > from http://en.wikipedia.org/wiki/Amazon_Elastic_MapReduce#Amazon_Elastic_MapR... > Elastic MapReduce (EMR)was introduced by Amazon in April 2009. Provisioning of the Hadoop cluster, running and terminating jobs, and handling data transfer between EC2 and S3 are automated by Elastic MapReduce. Apache Hive, which is built on top of Hadoop for providing data warehouse services, is also offered in Elastic MapReduce. > ... > In June 2012, premium options for EMR were added that replace ordinary Hadoop with MapR's M3 and M5 versions. These options provide additional capabilities over and above what the default EMR offering provides. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2819) Use Oauth SAML Bearer Assertion Flow

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2819?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2819: ---------------------------------- Fix Version/s: 8.9 (was: 8.8) > Use Oauth SAML Bearer Assertion Flow > ------------------------------------ > > Key: TEIID-2819 > URL: https://issues.jboss.org/browse/TEIID-2819 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.9 > > > I can secure my mobile and cloud applications? > Consider doing SAML first and Oauth later – the use cases are the same, the implementation is different > Link - https://help.salesforce.com/apex/HTViewHelpDoc?id=remoteaccess_oauth_SAML... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2882) Add support for Presto DB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2882?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2882: ---------------------------------- Fix Version/s: 8.9 (was: Open To Community) (was: 8.8) > Add support for Presto DB > ------------------------- > > Key: TEIID-2882 > URL: https://issues.jboss.org/browse/TEIID-2882 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: 8.9 > > > Presto is an open source distributed SQL query engine for running interactive analytic queries against data sources of all sizes ranging from gigabytes to petabytes. > Presto was designed and written from the ground up for interactive analytics and approaches the speed of commercial data warehouses while scaling to the size of organizations like Facebook. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2883) Support ParAccel as a data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2883?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2883: ---------------------------------- Fix Version/s: 8.9 (was: Open To Community) (was: 8.8) > Support ParAccel as a data source > --------------------------------- > > Key: TEIID-2883 > URL: https://issues.jboss.org/browse/TEIID-2883 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Van Halbert > Fix For: 8.9 > > > Support ParAccel as a data source -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2818) Use Oauth SAML Grant Type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2818?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2818: ---------------------------------- Fix Version/s: 8.9 (was: 8.8) > Use Oauth SAML Grant Type > ------------------------- > > Key: TEIID-2818 > URL: https://issues.jboss.org/browse/TEIID-2818 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.9 > > > How to connect to underlying data sources on behalf of Oauth when user comes into webservice with Oauth? > Use cases: > 1 – client u/p sources: oauth/saml > 2- client : oauth/saml sorces u/p, other > 3 – client: Oauth/saml sources Oauth/saml (data sources are also secured by Oauth) – > 3a) propogate sources and 3b – resolve new tokens for sources > Link: http://www.layer7tech.com/tutorials/oauth-20-with-layer-7-gateways-tutori... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2014