June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4293) Some Management CLI should setAllowedValues

by Kylin Soong (JIRA)

Kylin Soong created TEIID-4293: ---------------------------------- Summary: Some Management CLI should setAllowedValues Key: TEIID-4293 URL: https://issues.jboss.org/browse/TEIID-4293 Project: Teiid Issue Type: Enhancement Components: Server Affects Versions: 9.1 Reporter: Kylin Soong Assignee: Kylin Soong Fix For: 9.x * /subsystem=teiid:write-attribute(name=authentication-type,value=USERPASSWORD) - the allowed values should be USERPASSWORD,GSS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3617) Provide an option to Limit per user based connections

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3617: ------------------------------------ > Above is NOT scoped to the VDB. Once you scope to the VDB, it may be not that worth while to put in the system configuration, as that needs to be managed every time one deploys and undeploys the vdb. Each time create a session, the 'authentication-max-sessions-allowed-per-user' will be parse are replace the previous or system level setting, there is no doubt, VDB properties setting will take effect, and it not effect in deploys/undeploys, and effect in connection creates/closes. Also write-attribute will totally refresh the setting. > Typically anything teiid scoped is not in the system configuration. I think authentication-max-sessions-allowed-per-user are more same as authentication-max-sessions-allowed, as below cli for setting max allowed sessions(default is 1000) {code} /subsystem=teiid:write-attribute(name=authentication-max-sessions-allowed,value=1000) /subsystem=teiid:read-attribute(name=authentication-max-sessions-allowed) {code} why authentication-max-sessions-allowed can add as a attribute, and authentication-max-sessions-allowed-per-user can't? > Provide an option to Limit per user based connections > ----------------------------------------------------- > > Key: TEIID-3617 > URL: https://issues.jboss.org/browse/TEIID-3617 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Xian Liu > Assignee: Kylin Soong > Fix For: 9.1 > > > we deploy teiid for users to get data, but some users will create many connections to teiid and they are not necessary, I need to find a good way to limit each user account can only get like 50 connections or so -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4291) Object translator does not take into account folders where determining table name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4291?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4291: --------------------------------------- Van, did you want me to work this? > Object translator does not take into account folders where determining table name > --------------------------------------------------------------------------------- > > Key: TEIID-4291 > URL: https://issues.jboss.org/browse/TEIID-4291 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x, 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When obtaining the table name and using it to match the registered class (configured in RA), the logic doesn't take into account when folders are used. The name is returned like: folder[.folder].tableName > Nee to change logic to strip folder(s) to get the tableName. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4090) Issue with entitysets/properties ending in auth or token

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4090: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1346025|https://bugzilla.redhat.com/show_bug.cgi?id=1346025] from ASSIGNED to MODIFIED > Issue with entitysets/properties ending in auth or token > -------------------------------------------------------- > > Key: TEIID-4090 > URL: https://issues.jboss.org/browse/TEIID-4090 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Blocker > Labels: Final > Fix For: 9.0, 8.12.5 > > > To handle oauth, we are check for uri.endsWith("auth") || uri.endsWith("token") - however valid uris can end with those characters as well. An ioexception will be thrown instead of seeing the expected results - we also need to not simply throw an ioexception in ODataServlet as there is no server log of the exception and the client sees a 500 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4287) An exception is thrown by PostgreSQL when nested CTEs are pushed down

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4287?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4287: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1349030 Bugzilla Update: Perform > An exception is thrown by PostgreSQL when nested CTEs are pushed down > --------------------------------------------------------------------- > > Key: TEIID-4287 > URL: https://issues.jboss.org/browse/TEIID-4287 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Salvatore R > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.5, 8.13.6, 9.0.1 > > > I defined the following views in my VDB, based on a table in PostgreSQL: > {code:sql} > create view tv0 as > WITH > cte1 as (SELECT 1 as a), > alias2 as (select a from cte1), > cte3 as (select a from alias2) > SELECT cte3.a FROM alias2 join cte3 on cte3.a=alias2.a; > create view tv1 as > WITH > cte1 as (SELECT a from pg.test_a), > alias2 as (select a from cte1), > cte3 as (select a from alias2) > SELECT cte3.a FROM alias2 join cte3 on cte3.a=alias2.a; > create view tv2 as > WITH > alias2 as (select b, a from pg.test_a), > cte4 as (select a from alias2) > SELECT cte4.a FROM cte4 join alias2 on cte4.a=alias2.a ; > {code} > The following query, based on views tv0 and tv1: > {code:sql} > with > CTE1 as ( > select a from ( > with CTE11 as (select a from views.tv0) > select a from CTE11 > ) as SUBQ1), > CTE2 as ( > select a from ( > with CTE21 as (select a from views.tv1) > select a from CTE21 > ) as SUBQ2) > select * from CTE1 as T1 join CTE2 as T2 on T1.a=T2.a > {code} > throws this exception: > {code:sql} > 18:55:23,260 WARN [org.teiid.PROCESSOR] (Worker24_QueryProcessorQueue773) qPWXuJPW78go TEIID30020 Processing exception for request qPWXuJPW78go.3 'TEIID30504 test_tables_pg: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: WITH alias2__1 (a) AS (SELECT g_0."a" FROM "public"."test_a" AS g_0) SELECT g_1.a AS c_0 FROM alias2__1 AS g_0, alias2 AS g_1 WHERE g_1.a = g_0.a AND g_1.a = 1 ORDER BY c_0]'. Originally TeiidProcessingException 'ERROR: Relation "alias2" does not exist > Position: 113' QueryExecutorImpl.java:2157. Enable more detailed logging to see the entire stacktrace. > 19:00:13,379 WARN [org.teiid.CONNECTOR] (Worker28_QueryProcessorQueue775) qPWXuJPW78go Connector worker process failed for atomic-request=qPWXuJPW78go.4.7.144: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: WITH alias2__1 (a) AS (SELECT g_0."a" FROM "public"."test_a" AS g_0) SELECT g_1.a AS c_0 FROM alias2__1 AS g_0, alias2 AS g_1 WHERE g_1.a = g_0.a AND g_1.a = 1 ORDER BY c_0] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365) > at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy56.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.postgresql.util.PSQLException: ERROR: Relation "alias2" does not exist > Position: 113 > at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) > at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) > at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) > at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) > at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417) > at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:504) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) > ... 17 more > {code} > A similar query based on view tv2, throws a different exception: > {code:sql} > with > CTE1 as ( > select a from ( > with CTE11 as (select a from views.tv2) > select a from CTE11 > ) as SUBQ1), > CTE2 as ( > select a from ( > with CTE21 as (select a from views.tv2) > select a from CTE21 > ) as SUBQ2) > select * from CTE1 as T1 join CTE2 as T2 on T1.a=T2.a > {code} > {code:sql} > 19:05:02,784 WARN [org.teiid.CONNECTOR] (Worker30_QueryProcessorQueue778) qPWXuJPW78go Connector worker process failed for atomic-request=qPWXuJPW78go.5.2.145: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: WITH alias2 (b, a) AS (SELECT NULL, g_0."a" FROM "public"."test_a" AS g_0), alias2__1 (a, b) AS (SELECT NULL, g_0."a" FROM "public"."test_a" AS g_0) SELECT g_2.a, g_0.a FROM alias2 AS g_0, alias2 AS g_1, alias2 AS g_2, alias2__1 AS g_3 WHERE g_2.a = g_3.a AND g_0.a = g_1.a AND g_0.a = g_2.a] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:365) > at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy56.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.postgresql.util.PSQLException: ERROR: failed to find conversion function from unknown to integer > at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) > at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) > at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) > at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) > at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417) > at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:504) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) > ... 17 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4291) Object translator does not take into account folders where determining table name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4291?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4291: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1349159 Bugzilla Update: Perform > Object translator does not take into account folders where determining table name > --------------------------------------------------------------------------------- > > Key: TEIID-4291 > URL: https://issues.jboss.org/browse/TEIID-4291 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x, 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > > When obtaining the table name and using it to match the registered class (configured in RA), the logic doesn't take into account when folders are used. The name is returned like: folder[.folder].tableName > Nee to change logic to strip folder(s) to get the tableName. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4090) Issue with entitysets/properties ending in auth or token

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4090: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1346025|https://bugzilla.redhat.com/show_bug.cgi?id=1346025] from MODIFIED to ASSIGNED > Issue with entitysets/properties ending in auth or token > -------------------------------------------------------- > > Key: TEIID-4090 > URL: https://issues.jboss.org/browse/TEIID-4090 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Blocker > Labels: Final > Fix For: 9.0, 8.12.5 > > > To handle oauth, we are check for uri.endsWith("auth") || uri.endsWith("token") - however valid uris can end with those characters as well. An ioexception will be thrown instead of seeing the expected results - we also need to not simply throw an ioexception in ODataServlet as there is no server log of the exception and the client sees a 500 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3598) MongoDB string functions - different handling of NULL values

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3598?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3598: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1247976|https://bugzilla.redhat.com/show_bug.cgi?id=1247976] from ON_QA to VERIFIED > MongoDB string functions - different handling of NULL values > ------------------------------------------------------------ > > Key: TEIID-3598 > URL: https://issues.jboss.org/browse/TEIID-3598 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 8.12 > > > Teiid doesn't handle NULL values right in given functions when working with mongodb. > * SUBSTRING(<column resolving to NULL>,2) > ** query: > {code:sql} > SELECT INTKEY, STRINGNUM, SUBSTRING(STRINGNUM, 2) FROM BQT1.SmallA ORDER BY INTKEY > {code} > ** source query: > {code:plain} > {"$project": {{ "c_0" : "$INTKEY" , "c_1" : "$STRINGNUM" , "c_2" : { "$substr" : [ "$STRINGNUM" , { "$subtract" : [ 2 , 1]} , 4000]}}}} > {code} > ** problem: > For row with NULL value in given column returns sth like: > {code:plain}{ "_id" : ObjectId("534bf17516997a2a41000002"), "c_0" : 1, "c_1" : null, "c_2" : "" } > {code}which results in "" as result for SUBSTRING(NULL, 2) which should return NULL instead > * UCASE, LCASE (UPPER, LOWER) > ** query: > {code:sql} > SELECT intkey, stringnum, LOWER(stringnum) AS LOWER FROM BQT1.SmallA ORDER BY intkey > {code} > ** source query: > {code:plain} > {"$project": {{ "c_0" : "$INTKEY" , "c_1" : "$STRINGNUM" , "c_2" : { "$toLower" : [ "$STRINGNUM"]}}}} > {code} > ** problem: > For row with NULL value in given column returns sth like: > {code:plain} > { "_id" : ObjectId("534bf17516997a2a41000002"), "c_0" : 1, "c_1" : null, "c_2" : "" } > {code} which results in "" as result for LCASE(NULL) which should return NULL instead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3281) MongoDB: EmptyStackException when joining tables

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3281?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3281: ------------------------------------------------ Filip Elias <felias(a)redhat.com> changed the Status of [bug 1180144|https://bugzilla.redhat.com/show_bug.cgi?id=1180144] from ON_QA to VERIFIED > MongoDB: EmptyStackException when joining tables > ------------------------------------------------ > > Key: TEIID-3281 > URL: https://issues.jboss.org/browse/TEIID-3281 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.10 > > Attachments: mongodb-vdb.xml, server.log > > > Teiid throws java.util.EmptyStackException when joining data from table which has teiid_mongo:MERGE property enabled. > Example: > {code} > insert into customer2 values(1,'Pepa', 'Koukal'); > insert into customer2 values(2,'Jan', 'Tlemil'); > insert into Address values(1,1,'Pepas Street','Pepas City','Pepas State', 'Pepas zipcode'); > insert into Address values(2,2,'Jans Street','Pepa','Jans State', 'Jans zipcode'); > {code} > {code} > select a.*,b.* from customer2 a inner join Address b on a.CustomerId=b.CustomerId order by a.customerID > {code} > {code} > Error: > java.util.EmptyStackException > at java.util.Stack.peek(Stack.java:102) > at java.util.Stack.pop(Stack.java:84) > at org.teiid.translator.mongodb.MongoDBSelectVisitor.visit(MongoDBSelectVisitor.java:993) > at org.teiid.language.SortSpecification.acceptVisitor(SortSpecification.java:53) > at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) > at org.teiid.translator.mongodb.MongoDBSelectVisitor.append(MongoDBSelectVisitor.java:112) > {code} > VDB and log are in the attachment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3617) Provide an option to Limit per user based connections

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3617?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3617: ------------------------------------- Above is NOT scoped to the VDB. Once you scope to the VDB, it may be not that worth while to put in the system configuration, as that needs to be managed every time one deploys and undeploys the vdb. Typically anything teiid scoped is not in the system configuration. > Provide an option to Limit per user based connections > ----------------------------------------------------- > > Key: TEIID-3617 > URL: https://issues.jboss.org/browse/TEIID-3617 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Xian Liu > Assignee: Kylin Soong > Fix For: 9.1 > > > we deploy teiid for users to get data, but some users will create many connections to teiid and they are not necessary, I need to find a good way to limit each user account can only get like 50 connections or so -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2016