February 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4784) Provide functionality to perform RENAME table in DDL scripts

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4784?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4784: ------------------------------------- Component/s: Query Engine Affects Version/s: 9.3 (was: 9.2) Assignee: (was: Steven Hawkins) > Provide functionality to perform RENAME table in DDL scripts > ------------------------------------------------------------ > > Key: TEIID-4784 > URL: https://issues.jboss.org/browse/TEIID-4784 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.3 > Reporter: Bram Gadeyne > > Allow rename commands like: > ALTER TABLE "teiidtest" RENAME TO "tmptbl_teiidtest"; > This should rename the table name teiidtest in the current schema to tmptbl_teiidtest. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4785) Add options through alter table in DDL does not work.

by Bram Gadeyne (JIRA)

Bram Gadeyne created TEIID-4785: ----------------------------------- Summary: Add options through alter table in DDL does not work. Key: TEIID-4785 URL: https://issues.jboss.org/browse/TEIID-4785 Project: Teiid Issue Type: Bug Affects Versions: 9.2 Reporter: Bram Gadeyne Assignee: Steven Hawkins A command like the one below fails ALTER TABLE "teiidtest" options (add cardinality 1); This fails with message: This complains that the "group" teiidtest could not be found. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4784) Provide functionality to perform RENAME table in DDL scripts

by Bram Gadeyne (JIRA)

Bram Gadeyne created TEIID-4784: ----------------------------------- Summary: Provide functionality to perform RENAME table in DDL scripts Key: TEIID-4784 URL: https://issues.jboss.org/browse/TEIID-4784 Project: Teiid Issue Type: Feature Request Affects Versions: 9.2 Reporter: Bram Gadeyne Assignee: Steven Hawkins Allow rename commands like: ALTER TABLE "teiidtest" RENAME TO "tmptbl_teiidtest"; This should rename the table name teiidtest in the current schema to tmptbl_teiidtest. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4770) The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema.

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-4770?page=com.atlassian.jira.plugin... ] Bram Gadeyne commented on TEIID-4770: ------------------------------------- Hi Steven, Please let me know if you need the full data-role xml. e.g. for the resource glims it is defined (by teiiddesigner) as: {code:xml} <data-role name="mica" any-authenticated="false" allow-create-temporary-tables="true" grant-all="false"> <description></description>  <permission> <resource-name>glims</resource-name> <allow-create>false</allow-create> <allow-read>false</allow-read> <allow-update>false</allow-update> <allow-delete>false</allow-delete> <allow-execute>false</allow-execute> <allow-alter>false</allow-alter> </permission>  <mapped-role-name>mica</mapped-role-name> </data-role> {code} > The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema. > -------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4770 > URL: https://issues.jboss.org/browse/TEIID-4770 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 9.2 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.1 > > > The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema. > E.g. GRANT ON SCHEMA glims TO mica; > When you try to deploy the script, the server complains that it expects a permission type (like select or alter) here. > These lines should probably be removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4770) The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4770?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4770: --------------------------------------- Do you have an example of what data role xml generated the empty grant? > The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema. > -------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4770 > URL: https://issues.jboss.org/browse/TEIID-4770 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 9.2 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.1 > > > The convert script generates empty GRANT statements for roles that don't have permission to access a certain schema. > E.g. GRANT ON SCHEMA glims TO mica; > When you try to deploy the script, the server complains that it expects a permission type (like select or alter) here. > These lines should probably be removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4626) Add a full snapshot refresh strategy based upon table modifications

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4626: --------------------------------------- > On the "LAZY" case, I see that in update/delete case setting value to -1 works, but I am not sure how to handle a "insert" case? any suggestions? I'm not sure I follow this in the context of this issue - are you talking about implementing row level lazy updates? For this issue we're not assuming row level tracability and simply tracking any update as a modification. > Add a full snapshot refresh strategy based upon table modifications > ------------------------------------------------------------------- > > Key: TEIID-4626 > URL: https://issues.jboss.org/browse/TEIID-4626 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > using the existing full materialization refresh logic we can trigger a refresh based upon a notion of how dirty a table is based upon a proportion of rows updated to the rows in the table. This would also require some change to the status table to capture the number of transitive row updates. This could then be hooked up to debezium as the event source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4771) The convert script generates GRANT TEMPORARY_TABLE ON DATABASE statements but these fail.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4771?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4771: --------------------------------------- I'm working on these changes. We need to make several adjustments. First with the generated ddl the permission names need to be corrected. Then it makes sense to remove the ON DATABASE and instead make grants contextual to the current database. Beyond that we need to use slightly different syntax to handle the LANGUAGE and ALL PRIVILEGES grants - as they are currently not implemented against schema resources. We also have an issue with REVOKE handling in that it attempts to match the resource - but with the current permission system it's perfectly valid to grant access at a high level (for example the schema) then revoke for individual tables. > The convert script generates GRANT TEMPORARY_TABLE ON DATABASE statements but these fail. > ----------------------------------------------------------------------------------------- > > Key: TEIID-4771 > URL: https://issues.jboss.org/browse/TEIID-4771 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 9.2 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.1 > > > The script generates GRANT TEMPORARY_TABLE ON DATABASE statements but these fail. > Apparently the script does accept TEMPORARY TABLE (without the underscore). I also had to explicitly state the database name otherwise I get a message "TEIID31231 Database null.{1} not found". > So this doesn't work: GRANT TEMPORARY_TABLE ON DATABASE TO rouser; > But this does work: GRANT TEMPORARY TABLE ON DATABASE vdb TO rouser; -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4626) Add a full snapshot refresh strategy based upon table modifications

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4626: ------------------------------------- Yes, RefreshType is not required on {{Status}} table, I realized that after the comment. Yes, on EAGER right now it is updating the view for each event, my comment was more specific to *if* we ever need to do anything on TTL, but since the view always up to date, there is nothing to be done. On the "LAZY" case, I see that in update/delete case setting value to -1 works, but I am not sure how to handle a "insert" case? any suggestions? As per the full update of all invalid rows collected over the time, I am sure we can develop further refinements/additions to TTL strategy. > Add a full snapshot refresh strategy based upon table modifications > ------------------------------------------------------------------- > > Key: TEIID-4626 > URL: https://issues.jboss.org/browse/TEIID-4626 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > using the existing full materialization refresh logic we can trigger a refresh based upon a notion of how dirty a table is based upon a proportion of rows updated to the rows in the table. This would also require some change to the status table to capture the number of transitive row updates. This could then be hooked up to debezium as the event source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4771) The convert script generates GRANT TEMPORARY_TABLE ON DATABASE statements but these fail.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4771?page=com.atlassian.jira.plugin... ] Work on TEIID-4771 started by Steven Hawkins. --------------------------------------------- > The convert script generates GRANT TEMPORARY_TABLE ON DATABASE statements but these fail. > ----------------------------------------------------------------------------------------- > > Key: TEIID-4771 > URL: https://issues.jboss.org/browse/TEIID-4771 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 9.2 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.1 > > > The script generates GRANT TEMPORARY_TABLE ON DATABASE statements but these fail. > Apparently the script does accept TEMPORARY TABLE (without the underscore). I also had to explicitly state the database name otherwise I get a message "TEIID31231 Database null.{1} not found". > So this doesn't work: GRANT TEMPORARY_TABLE ON DATABASE TO rouser; > But this does work: GRANT TEMPORARY TABLE ON DATABASE vdb TO rouser; -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4626) Add a full snapshot refresh strategy based upon table modifications

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4626: --------------------------------------- Does the status table need the refresh type if it's already defined on the view? > When CDC event comes in, and processed through "UpdateMatview", this procedure will update the affected column's LoadNumber to -1, and this will also keep Status table's "Updated" column unmodified. > When TTL event occurs, if LAZY, "LoadMatView" procedure updates all the rows with LoadNumber -1. If EAGER, depending upon Status table's Updated column this will either run or do a SNAPSHOT re-load. This doesn't quite match the expected semantics of eager. You would expect eager to do something on every event, not based upon TTL. More than likely you would see this as an alternative or in addition to the TTL refresh approach. Such that after n update events we'll refresh - where n would likely be based upon the number of rows/columns. > Add a full snapshot refresh strategy based upon table modifications > ------------------------------------------------------------------- > > Key: TEIID-4626 > URL: https://issues.jboss.org/browse/TEIID-4626 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > using the existing full materialization refresh logic we can trigger a refresh based upon a notion of how dirty a table is based upon a proportion of rows updated to the rows in the table. This would also require some change to the status table to capture the number of transitive row updates. This could then be hooked up to debezium as the event source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2017