February 2017 - teiid-issues - Jboss List Archives

[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: --------------------------------------- Syntax changes were documented - https://teiid.gitbooks.io/documents/content/reference/ddl_deployment_mode... > 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, 9 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 resolved TEIID-4770. ----------------------------------- Resolution: Done Changes for this include: - MetadataStore tracks revokes - removed the GRANT keyword from REVOKE - Changed language to be a resource type - Changed parsing so that ALL PRIVILEGES, TEMPORARY TABLES, and LANGUAGE are handled individually, and that we can have a grant/revoke with no privileges if it affects a mask/condition. > 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, 9 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 resolved TEIID-4771. ----------------------------------- Resolution: Done Corrected the generated ddl. See TEIID-4770 for other changes related to grant/revoke. > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4576) Do not get rid of an excepiton in BasicCryptor.decrypt()

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4576?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4576. ----------------------------------- Resolution: Out of Date Marking as out of date. It's suspected to have a root cause of TEIID-2952. > Do not get rid of an excepiton in BasicCryptor.decrypt() > -------------------------------------------------------- > > Key: TEIID-4576 > URL: https://issues.jboss.org/browse/TEIID-4576 > Project: Teiid > Issue Type: Feature Request > Components: Common > Affects Versions: 8.12.6.6_3 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > > org.teiid.core.crypto.BasicCryptor.decrypt() disposes of an exception which is caught there, but it is necessary for investigation when an error occurs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4791) Bypass lookup function's keycolumn reserved word

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4791?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4791. ----------------------------------- Fix Version/s: 9.3 9.2.1 9.1.4 Resolution: Done Accounted for reserved words in the generated underlying query. > Bypass lookup function's keycolumn reserved word > ------------------------------------------------ > > Key: TEIID-4791 > URL: https://issues.jboss.org/browse/TEIID-4791 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Environment: JDV 6.3.2 > Windows 7, 64-bit > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.1, 9.1.4 > > > When using the Teiid LOOKUP function, the 3rd argument is to specify the keycolumn. In my table, the column I want to reference is literally named "value", which is a SQL reserved word. The generated query chokes on this because it's not expecting a reserved word to be here when parsing the grammar. I've tried quoting and escaping to get around this, but nothing seems to work. > {code} > 21:18:55,860 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue167) TEIID30020 Processing exception for request NLkytVFPLOM6.0 'TEIID30328 Unable to evaluate lookup('tdsa_vbl.t_code_translate', 'descr', 'value', 'NAMS'): TEIID31100 Parsing error: Encountered "SELECT [*]VALUE[*] ,DESCR" at line 1, column 8. > Was expecting: "char" | "date" | "time" | "timestamp" | "cast" | "convert" | "all" | "any" | "array_agg" | "case" ...'. Originally ExpressionEvaluationException QueryParser.java:214. Enable more detailed logging to see the entire stacktrace. > 21:19:13,077 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue168) TEIID30020 Processing exception for request /qqhN3vx+au1.0 'TEIID31118 Element "tdsa_vbl.t_code_translate."[value]"" is not defined by any relevant group.'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > 21:19:40,897 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue169) TEIID30020 Processing exception for request 1TAniWpe2wpN.0 'TEIID31119 Symbol "'value'" is specified with an unknown group context'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > 21:19:52,600 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue170) TEIID30020 Processing exception for request +8tCacHlFS8D.0 'TEIID31119 Symbol "value" is specified with an unknown group context'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4791) Bypass lookup function's keycolumn reserved word

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4791?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4791: ---------------------------------- Component/s: Query Engine > Bypass lookup function's keycolumn reserved word > ------------------------------------------------ > > Key: TEIID-4791 > URL: https://issues.jboss.org/browse/TEIID-4791 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Environment: JDV 6.3.2 > Windows 7, 64-bit > Reporter: Steve Tran > Assignee: Steven Hawkins > > When using the Teiid LOOKUP function, the 3rd argument is to specify the keycolumn. In my table, the column I want to reference is literally named "value", which is a SQL reserved word. The generated query chokes on this because it's not expecting a reserved word to be here when parsing the grammar. I've tried quoting and escaping to get around this, but nothing seems to work. > {code} > 21:18:55,860 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue167) TEIID30020 Processing exception for request NLkytVFPLOM6.0 'TEIID30328 Unable to evaluate lookup('tdsa_vbl.t_code_translate', 'descr', 'value', 'NAMS'): TEIID31100 Parsing error: Encountered "SELECT [*]VALUE[*] ,DESCR" at line 1, column 8. > Was expecting: "char" | "date" | "time" | "timestamp" | "cast" | "convert" | "all" | "any" | "array_agg" | "case" ...'. Originally ExpressionEvaluationException QueryParser.java:214. Enable more detailed logging to see the entire stacktrace. > 21:19:13,077 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue168) TEIID30020 Processing exception for request /qqhN3vx+au1.0 'TEIID31118 Element "tdsa_vbl.t_code_translate."[value]"" is not defined by any relevant group.'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > 21:19:40,897 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue169) TEIID30020 Processing exception for request 1TAniWpe2wpN.0 'TEIID31119 Symbol "'value'" is specified with an unknown group context'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > 21:19:52,600 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue170) TEIID30020 Processing exception for request +8tCacHlFS8D.0 'TEIID31119 Symbol "value" is specified with an unknown group context'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4791) Bypass lookup function's keycolumn reserved word

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-4791?page=com.atlassian.jira.plugin... ] Steve Tran updated TEIID-4791: ------------------------------ Affects Version/s: 8.12.x > Bypass lookup function's keycolumn reserved word > ------------------------------------------------ > > Key: TEIID-4791 > URL: https://issues.jboss.org/browse/TEIID-4791 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.x > Environment: JDV 6.3.2 > Windows 7, 64-bit > Reporter: Steve Tran > Assignee: Steven Hawkins > > When using the Teiid LOOKUP function, the 3rd argument is to specify the keycolumn. In my table, the column I want to reference is literally named "value", which is a SQL reserved word. The generated query chokes on this because it's not expecting a reserved word to be here when parsing the grammar. I've tried quoting and escaping to get around this, but nothing seems to work. > {code} > 21:18:55,860 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue167) TEIID30020 Processing exception for request NLkytVFPLOM6.0 'TEIID30328 Unable to evaluate lookup('tdsa_vbl.t_code_translate', 'descr', 'value', 'NAMS'): TEIID31100 Parsing error: Encountered "SELECT [*]VALUE[*] ,DESCR" at line 1, column 8. > Was expecting: "char" | "date" | "time" | "timestamp" | "cast" | "convert" | "all" | "any" | "array_agg" | "case" ...'. Originally ExpressionEvaluationException QueryParser.java:214. Enable more detailed logging to see the entire stacktrace. > 21:19:13,077 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue168) TEIID30020 Processing exception for request /qqhN3vx+au1.0 'TEIID31118 Element "tdsa_vbl.t_code_translate."[value]"" is not defined by any relevant group.'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > 21:19:40,897 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue169) TEIID30020 Processing exception for request 1TAniWpe2wpN.0 'TEIID31119 Symbol "'value'" is specified with an unknown group context'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > 21:19:52,600 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue170) TEIID30020 Processing exception for request +8tCacHlFS8D.0 'TEIID31119 Symbol "value" is specified with an unknown group context'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4791) Bypass lookup function's keycolumn reserved word

by Steve Tran (JIRA)

Steve Tran created TEIID-4791: --------------------------------- Summary: Bypass lookup function's keycolumn reserved word Key: TEIID-4791 URL: https://issues.jboss.org/browse/TEIID-4791 Project: Teiid Issue Type: Bug Environment: JDV 6.3.2 Windows 7, 64-bit Reporter: Steve Tran Assignee: Steven Hawkins When using the Teiid LOOKUP function, the 3rd argument is to specify the keycolumn. In my table, the column I want to reference is literally named "value", which is a SQL reserved word. The generated query chokes on this because it's not expecting a reserved word to be here when parsing the grammar. I've tried quoting and escaping to get around this, but nothing seems to work. {code} 21:18:55,860 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue167) TEIID30020 Processing exception for request NLkytVFPLOM6.0 'TEIID30328 Unable to evaluate lookup('tdsa_vbl.t_code_translate', 'descr', 'value', 'NAMS'): TEIID31100 Parsing error: Encountered "SELECT [*]VALUE[*] ,DESCR" at line 1, column 8. Was expecting: "char" | "date" | "time" | "timestamp" | "cast" | "convert" | "all" | "any" | "array_agg" | "case" ...'. Originally ExpressionEvaluationException QueryParser.java:214. Enable more detailed logging to see the entire stacktrace. 21:19:13,077 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue168) TEIID30020 Processing exception for request /qqhN3vx+au1.0 'TEIID31118 Element "tdsa_vbl.t_code_translate."[value]"" is not defined by any relevant group.'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. 21:19:40,897 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue169) TEIID30020 Processing exception for request 1TAniWpe2wpN.0 'TEIID31119 Symbol "'value'" is specified with an unknown group context'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. 21:19:52,600 WARN [org.teiid.PROCESSOR] (Worker16_QueryProcessorQueue170) TEIID30020 Processing exception for request +8tCacHlFS8D.0 'TEIID31119 Symbol "value" is specified with an unknown group context'. Originally QueryResolverException ResolverVisitor.java:106. Enable more detailed logging to see the entire stacktrace. {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 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: ------------------------------------- Looks good, you can merge it. The one thing I was also trying to use RefreshType is to bring in the EAGER type updates, but I see there is no need for that. I would need to redo some parts if the document. > 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, 9 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4785?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4785: --------------------------------------- The issue here is a mismatch between the notion of DDL as interactive and as a declaration. As a declaration the imported table will not yet exist and the alter will fail. > 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 > Components: Query Engine > Affects Versions: 9.2 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.1 > > > 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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2017