May 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3738) Add multi-tenant functionality

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3738?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3738: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Add multi-tenant functionality > ------------------------------ > > Key: TEIID-3738 > URL: https://issues.jboss.org/browse/TEIID-3738 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > To supplement multi-source functionality, we should add explicit multi-tenant functionality similar to hibernate - http://docs.jboss.org/hibernate/orm/4.2/devguide/en-US/html/ch16.html > This would mostly be carried out at the datasource level, but would also make us cache aware. Otherwise our current story is to implement multi-source and add row level filters to all multi-source tables to prune based upon the user - which we could choose to expand on in Designer or the server such that the necessary roles are created automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3883) Properly project generated keys

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3883?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3883: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Properly project generated keys > ------------------------------- > > Key: TEIID-3883 > URL: https://issues.jboss.org/browse/TEIID-3883 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > Even with the generated keys refinements from TEIID-3872 we still are not fully projecting back the generated key values through virtual layers (possibly including masking affects, type, or column name changes). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3660) Add support for unnesting anti semijoins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3660?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3660: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Add support for unnesting anti semijoins > ---------------------------------------- > > Key: TEIID-3660 > URL: https://issues.jboss.org/browse/TEIID-3660 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > Currently we won't perform the rewrite if it's the anit case. A subquery used as an anti semijoin can be unnested into a left outer join with a filter on the null rows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3439) Add support for aliases with .

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3439?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3439: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Add support for aliases with . > ------------------------------ > > Key: TEIID-3439 > URL: https://issues.jboss.org/browse/TEIID-3439 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > We currently don't allow column or table aliases to contain '.'. This is allowable given a quoted identifier is used. However an early design decision of metamatrix was to relax the rules of naming so that queries against the engine could use quoting (on not) similar to whatever was expected by a given database rather than the engine structure. A lot of resolving and parsing logic will need to change unfortunately to fix this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3952) Update to updatable internal materialized view should update the materialized view as well as the database

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3952?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3952: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Update to updatable internal materialized view should update the materialized view as well as the database > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-3952 > URL: https://issues.jboss.org/browse/TEIID-3952 > Project: Teiid > Issue Type: Enhancement > Components: VDB > Affects Versions: 8.7 > Environment: Red Hat JBoss Data Virtualization 6.2 based on Teiid 8.7.x > Reporter: Andy Yuen > Assignee: Kylin Soong > Labels: jboss > Fix For: 9.1 > > > Updating an updatable internal materized view updates the database but not the materialized view at present. The requested enhancement is that they, both, should be updated. > Setup > Client - SquirrelSQL to access JDV > JDV 6.2 - with an updatable nternal materialized view of one table from the data source > Data Source - just one data source: MySQL > I can see from the console that the target table/view has been materialized > Then I did the following: > 1) select a row from the materialized table > 2) update a field in a row in the materialized view > 3) select that row (value unchanged ie, same as int 1) - tried multiple times > 4) issue EXEC SYSADMIN.refreshMatViewRow(...) using primary key for the row that has been changed > 5) select that row (value unchanged) - now I can see the changed data > This behaviour is counter-intuitive because I was expecting that since it is an updatable materialized view, my change will write through the materialized view ie, change both the materialized view as well as the database. But in this case, it changed the database and not the materialized view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 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: 9.1 (was: 9.0) > 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 > Assignee: Steven Hawkins > Fix For: 9.1 > > > 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 (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3454) Dependent Join optimizations for Netezza and Hive

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3454?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3454: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Dependent Join optimizations for Netezza and Hive > ------------------------------------------------- > > Key: TEIID-3454 > URL: https://issues.jboss.org/browse/TEIID-3454 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.10 > Reporter: John Muller > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.1 > > > Currently, dependent joins create 1 or more IN clauses. Many MPP / NoSQL systems can have drastically better performance by creating temp tables that match key distributions. Two examples I know of would be Netezza and Hive. > In Netezza, if the incoming dependent join (small dimension; here "Customer" using Northwind data model concepts) has a key that will be joined to to a big fact table that is DISTRIBUTED ON or ORGANIZED BY 'ed then creating a temp table that matches this distribution will result in ~100x query performance. Sometimes, if the dimension is small enough, this doesn't make a big difference as Netezza will perform a broadcast join, but it's never a bad idea to create the temp table. > Similarly, Hive DDL has both partitions and buckets (pre-sorted). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3630) Support merge statement pushdown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3630?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3630: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Support merge statement pushdown > -------------------------------- > > Key: TEIID-3630 > URL: https://issues.jboss.org/browse/TEIID-3630 > Project: Teiid > Issue Type: Enhancement > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > We should add support for the merge statement to be pushded down. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3537) Use array binding for postgresql dependent join

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3537?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3537: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Use array binding for postgresql dependent join > ----------------------------------------------- > > Key: TEIID-3537 > URL: https://issues.jboss.org/browse/TEIID-3537 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > Rather than creating a large sql statement or rely upon a small fixed limit to the number of binding, we can bind array values to perform dependent query comparisons - where id = ANY ? > This however only seems to work for single values or composites of the same type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3360) Provide an option to virtualize source exceptions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3360?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3360: ---------------------------------- Fix Version/s: 9.1 (was: 9.0) > Provide an option to virtualize source exceptions > ------------------------------------------------- > > Key: TEIID-3360 > URL: https://issues.jboss.org/browse/TEIID-3360 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1 > > > Currently we'll pass the source exception along with the Teiid exception. And from source sql exceptions we'll also rely the sql state/code. When connecting to databases of different types it would be best to return a common set of codes. > There is exception mapping logic in Hibernate that we could reuse, but this could apply to the non-jdbc sources such that a predictable code will seen by Teiid clients. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2016