October 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3790) Restrict any authenticated roles

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3790: ------------------------------------- Summary: Restrict any authenticated roles Key: TEIID-3790 URL: https://issues.jboss.org/browse/TEIID-3790 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.0, 8.12.x A local connection with the pass-through flag set will allow any connection if no security domain is set (the 8.x default). Beyond that the role assignment logic will any authenticated roles to those users. We need to restrict any-authenticated roles to only properly authenticated users. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Extension metadata is not visible when queried through OData

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2715: ------------------------------------- I am not sure where the annotation support lies in Olingo framework, I know it is not fully supported as of Olingo 4.0.0. So, yes this may need to be moved if we want use Annotations for these properties. > Extension metadata is not visible when queried through OData > ------------------------------------------------------------ > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Fix For: 8.12.x > > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Extension metadata is not visible when queried through OData

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2715: ----------------------------------- Assignee: Ramesh Reddy > Extension metadata is not visible when queried through OData > ------------------------------------------------------------ > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Assignee: Ramesh Reddy > Fix For: 8.12.x > > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3776) Teiid throws NPE if query contains AVG function on varchar type

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3776?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3776: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1272975|https://bugzilla.redhat.com/show_bug.cgi?id=1272975] from NEW to MODIFIED > Teiid throws NPE if query contains AVG function on varchar type > --------------------------------------------------------------- > > Key: TEIID-3776 > URL: https://issues.jboss.org/browse/TEIID-3776 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Execution of this query ends with NPE in Teiid: > SELECT stringnum FROM bqt1.smalla GROUP BY stringnum HAVING avg(stringnum) = '1' > Expected result: > Exception similar to - org.teiid.api.exception.query.QueryValidatorException: TEIID30492 The aggregate function AVG cannot be used with non-numeric expressions: AVG(BQT1.SmallA.StringNum) > Actual result: > {code:text} > 12:27:32,829 DEBUG [org.teiid.TRANSPORT] (New I/O worker #7) processing message:MessageHolder: key=619 contents=Invoke interface org.teiid.client.DQP.executeRequest > 12:27:32,830 DEBUG [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) Request Thread r77C2X0C5Gwa.10 with state NEW > 12:27:32,830 DEBUG [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) r77C2X0C5Gwa.10 Non-cachable command. > 12:27:32,830 DEBUG [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) r77C2X0C5Gwa.10 executing SELECT stringnum FROM bqt1.smalla GROUP BY stringnum HAVING avg(stringnum) = '1' > 12:27:32,831 ERROR [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) TEIID30019 Unexpected exception for request r77C2X0C5Gwa.10: java.lang.NullPointerException > at org.teiid.query.resolver.util.ResolverVisitor.resolveCompareCriteria(ResolverVisitor.java:767) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.util.ResolverVisitor.visit(ResolverVisitor.java:248) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.lang.CompareCriteria.acceptVisitor(CompareCriteria.java:126) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.navigator.AbstractNavigator.visitVisitor(AbstractNavigator.java:54) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.postVisitVisitor(PreOrPostOrderNavigator.java:61) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.postVisitVisitor(SimpleQueryResolver.java:197) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.navigator.PreOrPostOrderNavigator.visit(PreOrPostOrderNavigator.java:135) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.lang.CompareCriteria.acceptVisitor(CompareCriteria.java:126) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.sql.navigator.AbstractNavigator.visitNode(AbstractNavigator.java:63) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:214) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.command.SimpleQueryResolver.resolveCommand(SimpleQueryResolver.java:69) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:271) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.query.resolver.QueryResolver.resolveCommand(QueryResolver.java:124) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.Request.resolveCommand(Request.java:260) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.Request.generatePlan(Request.java:369) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.Request.processRequest(Request.java:435) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.RequestWorkItem.processNew(RequestWorkItem.java:613) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:315) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:254) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.1.6_2-redhat-6.jar:8.7.1.6_2-redhat-6] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40] > 12:27:32,832 DEBUG [org.teiid.PROCESSOR] (Worker52_QueryProcessorQueue378) java.lang.NullPointerException Sending error to client r77C2X0C5Gwa.10 > 12:27:32,833 DEBUG [org.teiid.TRANSPORT] (Worker52_QueryProcessorQueue378) send message: MessageHolder: key=619 contents=ResultsMessage rowCount=0 finalRow=-1 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2476: ---------------------------------- Description: We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries. (was: We should offer or possibly default to filtering columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries.) Summary: Exclude hidden tables/columns from metadata (was: Exclude hidden columns from metadata) > Exclude hidden tables/columns from metadata > ------------------------------------------- > > Key: TEIID-2476 > URL: https://issues.jboss.org/browse/TEIID-2476 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2476) Exclude hidden columns from metadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2476: ---------------------------------- Description: We should offer or possibly default to filtering columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries. (was: We should offer or possibly default to filtering columns that can not accessed out of the user metadata. This could be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it seems better to add filters to the DatabaseMetadata (and ideally pg) metadata queries. On the server side we may still want to have alternative handling for resolving select star.) > Exclude hidden columns from metadata > ------------------------------------ > > Key: TEIID-2476 > URL: https://issues.jboss.org/browse/TEIID-2476 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > We should offer or possibly default to filtering columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2715) Extension metadata is not visible when queried through OData

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2715?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2715: ---------------------------------- Fix Version/s: 8.12.x Ramesh does this make sense yet for 8.12.x, or should it be pushed? > Extension metadata is not visible when queried through OData > ------------------------------------------------------------ > > Key: TEIID-2715 > URL: https://issues.jboss.org/browse/TEIID-2715 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.6 > Environment: Windows 7 > Reporter: Alex Khvatov > Fix For: 8.12.x > > > x`Hi, > I used Teiid Designer and just plain XML editor (because Teiid Designer would constantly complain) I created Model Extension Definition file which I was able to successfully register. My definition was showing up in Model Extension Registry view. I deployed my virtual database and tried accessing columns and tables via Odata: > http://localhost:8080/odata/MCR_VDB/Tables?$format=json > http://localhost:8080/odata/MCR_VDB/Columns?$format=json > Both documents returned did not contain any extra metadata I defined. > HELP! > Thanks. > Alex -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3554) Audit log is missing details related to what role was applied and what info was allowed or denied

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3554?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3554: --------------------------------------- Can you provide updates based upon the last comment, or can this be closed out? > Audit log is missing details related to what role was applied and what info was allowed or denied > ------------------------------------------------------------------------------------------------- > > Key: TEIID-3554 > URL: https://issues.jboss.org/browse/TEIID-3554 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.7.1.6_2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Attachments: portfolioroles_data.xlsx > > > Using the dynamicvdb-dataroles quick start as the basis for triggering the audit log. Executing the view query: "Select * from StockPrice" . The query will only present the "price" column value when the user has the "prices" role. When performing queries with a user (name=teiidUser) that doesn't have the "prices" role versus one that does (name=portfolio), doesn't provide any discerning information in the audit log to indicate that a role was applied to the data. > Attaching excel file of the audit log data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3140) Add getVDBType() method to the VDB interface

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3140?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3140: ---------------------------------- Component/s: AdminApi Fix Version/s: 8.12.1 Targeting to 8.12.1 to add the is xml deployment method. > Add getVDBType() method to the VDB interface > -------------------------------------------- > > Key: TEIID-3140 > URL: https://issues.jboss.org/browse/TEIID-3140 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi > Reporter: Barry LaFond > Assignee: Steven Hawkins > Fix For: 8.12.1 > > > Because Teiid supports mutliple VDB types, any tooling designed to interact (edit, deploy, undeploy, display etc...) with the runtime VDBs will need to be able to easilly distinguish what each VDB type is. > Currently Teiid Designer utilizes PREVIEW and defeault VDBs with *vdb* file extensions and there are 2 types of dynamic VDBs, *xml* and *zip* files backed by DDL model metadata definitions. > The current VDB interface currently doesn't provide a type. > Request adding something like: > {code} > public enum VDBType {DEFAULT, PREVIEW, XML, DDL} > /** > * @return the vdb type > */ > public VDBType getVDBType(); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3771) Teiid throws an NPE while executing query with nested subquery IN predicate

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3771?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3771: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1272915|https://bugzilla.redhat.com/show_bug.cgi?id=1272915] from NEW to MODIFIED > Teiid throws an NPE while executing query with nested subquery IN predicate > --------------------------------------------------------------------------- > > Key: TEIID-3771 > URL: https://issues.jboss.org/browse/TEIID-3771 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 8.12.1, 8.13 > > > Teiid throws an NPE while executing query with double IN predicate. Example query: > SELECT intkey FROM BQT1.SmallA AS A WHERE INTKEY IN (SELECT CONVERT(STRINGKEY, INTEGER) FROM BQT1.SMALLA AS A WHERE STRINGKEY IN (SELECT CONVERT(INTKEY, STRING) FROM BQT1.SMALLA AS B WHERE A.INTNUM = B.INTNUM)) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2015