March 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4760) optional object name manipulations while executing IMPORT FOREIGN SCHEMA

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4760?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4760: ---------------------------------- Fix Version/s: 10.3 (was: Open To Community) (was: 10.x) > optional object name manipulations while executing IMPORT FOREIGN SCHEMA > ------------------------------------------------------------------------ > > Key: TEIID-4760 > URL: https://issues.jboss.org/browse/TEIID-4760 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Bram Gadeyne > Labels: ddl, import, import_wizard > Fix For: 10.3 > > > While executing IMPORT FOREIGN SCHEMA, table (and other object) names are added to the schema with their original names. > In our previous virtual database we imported two schema's that contain the same objects but one is a production and another is a historical database. > We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the schema it came from. Some software that interacts with teiid can not distinguish between different schemas and can not handle duplicate table names. So for this reason, this would also come in handy. > It would come in handy if it is possible to add a prefix to names while importing objects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4526: ---------------------------------- Fix Version/s: 10.3 (was: 10.x) > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 10.3 > > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5207) Allow exponential values in OData V4 payloads with decimals

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5207?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5207: ---------------------------------- Fix Version/s: 10.3 (was: 10.x) > Allow exponential values in OData V4 payloads with decimals > ----------------------------------------------------------- > > Key: TEIID-5207 > URL: https://issues.jboss.org/browse/TEIID-5207 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 10.3 > > > This is link to the upstream Olingo issue https://issues.apache.org/jira/browse/OLINGO-1150 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4932) Support defining UDFs based upon a class and or function

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4932?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4932: ---------------------------------- Fix Version/s: 10.3 (was: 10.x) > Support defining UDFs based upon a class and or function > -------------------------------------------------------- > > Key: TEIID-4932 > URL: https://issues.jboss.org/browse/TEIID-4932 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > With the new ddl support, we should allow an import to work against a class to define UDFs. > We should also in general support inferring arguments for UDFs and UDFs that are defined by a method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4625) Consider consolidating/managing materialization status tables

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4625?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4625: ---------------------------------- Fix Version/s: 10.3 (was: 10.x) > Consider consolidating/managing materialization status tables > ------------------------------------------------------------- > > Key: TEIID-4625 > URL: https://issues.jboss.org/browse/TEIID-4625 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 10.3 > > > To enhance usability we should consider consolidating/managing status tables. Management would include auto creation similar (which could just leverage hibernate similar to the database log logic, regardless of whether we use hibernate to read/write). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4691) Consider replacing JGroups based custom replication with native

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4691?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4691: ---------------------------------- Fix Version/s: 10.3 (was: 10.x) > Consider replacing JGroups based custom replication with native > --------------------------------------------------------------- > > Key: TEIID-4691 > URL: https://issues.jboss.org/browse/TEIID-4691 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Ramesh Reddy > Fix For: 10.3 > > > JGroups is responsible for node to node communication. JGroups FRAG2 chunks up the messages that are sizeable by flow control. If you use TCP it will automatically break up the messages into the MTU. Using Jumbo Frames would be recommended. > Note that this will affect how we do the materialization replication among nodes currently. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3157) Allow streaming without an intermediate copy

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3157?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3157: ---------------------------------- Fix Version/s: 10.3 (was: 10.x) > Allow streaming without an intermediate copy > -------------------------------------------- > > Key: TEIID-3157 > URL: https://issues.jboss.org/browse/TEIID-3157 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Server > Reporter: H B > Fix For: 10.3 > > > With TEIID-3153 there are scenarios that require streaming larger than 4 gigs of data. We should also provide a mechanism for on demand streaming from the client to accommodate even larger streaming scenarios to eliminate the need for an intermediate copy. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4884) Google spreadsheet throws Error when getting batch 401:Unauthorized

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4884?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4884: ---------------------------------- Fix Version/s: 10.3 (was: 10.x) > Google spreadsheet throws Error when getting batch 401:Unauthorized > ------------------------------------------------------------------- > > Key: TEIID-4884 > URL: https://issues.jboss.org/browse/TEIID-4884 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.3 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 10.3 > > Attachments: gs-http401 > > > It seems that after executing a larger load of queries following error occurs: "Error when getting batch 401:Unauthorized". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4934) Allow importing VDBs with conflicting model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4934?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4934: ---------------------------------- Fix Version/s: 10.3 (was: 10.x) > Allow importing VDBs with conflicting model > ------------------------------------------- > > Key: TEIID-4934 > URL: https://issues.jboss.org/browse/TEIID-4934 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2.3 > Environment: * Wildfly 10 > * Teiid Server 9.2.3 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 10.3 > > > It should be possible to import a model via "_import-vdb_" that conflicts with other models also imported via "_import-vdb_" if the conflicting model has the same version. > This will allow greater model reuse, and not to have duplicated model definitions in multiple vdbs. > Example: > VDB 1: > <code> > <vdb name="OneVDB" version="1"> > <description>One VDB</description> > <import-vdb name=ConflictingVDB" version="1"/> > <import-vdb name="OtherVDB" version="1"/> > </code> > VDB 2: > <code> > <vdb name="TwoVDB" version="1"> > <description>TwoVDB</description> > <import-vdb name=ConflictingVDB" version="1"/> > <import-vdb name="YetOtherVDB" version="1"/> > </code> > VDB 3: > <code> > <vdb name="ThirdVDB" version="1"> > <description>Third VDB</description> > <import-vdb name=OneVDB" version="1"/> > <import-vdb name="TwoVDB" version="1"/> > </code> > Currently we cannot use the ThirdVDB as is, since there is a conflicting VDB (ConflictingVDB) defined in VDBS One and Two. > Since both are using the same version, it should be possible to ignore the conflict (via a property for example). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 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: 10.3 (was: 10.x) > Use Oauth SAML Bearer Assertion Flow > ------------------------------------ > > Key: TEIID-2819 > URL: https://issues.jboss.org/browse/TEIID-2819 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 10.3 > > > 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 (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2018