December 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3261) DB Logging with DB2 - server fails to start

by Jan Stastny (JIRA)

Jan Stastny created TEIID-3261: ---------------------------------- Summary: DB Logging with DB2 - server fails to start Key: TEIID-3261 URL: https://issues.jboss.org/browse/TEIID-3261 Project: Teiid Issue Type: Bug Affects Versions: 8.7.1 Reporter: Jan Stastny Assignee: Steven Hawkins When using DB Logging with DB2 database an error occurs during server start: 13:02:15,237 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 56) HHH000389: Unsuccessful: create table commandlog (id bigint not null, applicationname varchar(255), executionid varchar(50), modelname varchar(255), principal varchar(50), queryplan blob(255), requestid varchar(50), row_count integer, sessionid varchar(50), sourcecommand smallint, sourcerequestid bigint, sqlcmd varchar(8196), eventtype varchar(10), logtime timestamp, transactionid varchar(256), translatorname varchar(50), vdbname varchar(255), vdbversion integer, primary key (id)) 13:02:15,238 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 56) DB2 SQL Error: SQLCODE=-286, SQLSTATE=42727, SQLERRMC=16384;DBALLO00, DRIVER=4.12.55 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3245) Database Logging: Problems with Microsoft

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3245?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3245: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1118470|https://bugzilla.redhat.com/show_bug.cgi?id=1118470] from ON_QA to VERIFIED > Database Logging: Problems with Microsoft > ------------------------------------------ > > Key: TEIID-3245 > URL: https://issues.jboss.org/browse/TEIID-3245 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.7.1 > > > Still getting error with mssql driver and sql server 2012. > The error messages look similar, but one: > [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 55) Incorrect syntax near the keyword 'rowcount'. > is present. > While the prior issue > 14:46:56,858 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool – 57) Incorrect syntax near the keyword 'plan'. > was solved. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3260) Create custom metadata repository that uses Modeshape

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3260?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3260: ------------------------------------ First thought is to create a quick start that provides an example that can be used. > Create custom metadata repository that uses Modeshape > ----------------------------------------------------- > > Key: TEIID-3260 > URL: https://issues.jboss.org/browse/TEIID-3260 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > > Create a custom metadata repository implementation that uses ModeShape as the repository for obtaining the VDB metadata for deployment. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3260) Create custom metadata repository that uses Modeshape

by Van Halbert (JIRA)

Van Halbert created TEIID-3260: ---------------------------------- Summary: Create custom metadata repository that uses Modeshape Key: TEIID-3260 URL: https://issues.jboss.org/browse/TEIID-3260 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 8.10 Reporter: Van Halbert Assignee: Van Halbert Create a custom metadata repository implementation that uses ModeShape as the repository for obtaining the VDB metadata for deployment. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3258) Add support for quoted identifiers in set/show

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3258?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3258. ----------------------------------- Resolution: Done updated the client handling to accept escaped identifiers as well > Add support for quoted identifiers in set/show > ---------------------------------------------- > > Key: TEIID-3258 > URL: https://issues.jboss.org/browse/TEIID-3258 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > The set / show statements assume that only non-qualified identifiers will be used. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3255) Support PicketBox / XACML authorization

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3255?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3255: ------------------------------------- Do you have proposal as to how it fits/overlays with current security framework and any prototypes? > Support PicketBox / XACML authorization > --------------------------------------- > > Key: TEIID-3255 > URL: https://issues.jboss.org/browse/TEIID-3255 > Project: Teiid > Issue Type: Feature Request > Components: OData > Affects Versions: 8.9 > Reporter: John Muller > Assignee: Steven Hawkins > > We would like the OData, OData4, JDBC, and ODBC transports of Teiid to act as an XACML policy enforcement point for all CRUD operations (as well as execute stored procedures). Looking through old JIRAs: > https://issues.jboss.org/browse/TEIID-1031 > it looks like this was considered back in the mid-2010 timeframe, but wasn't fully thought through. With XACML 3.0, it's possible to use Multiple Decision Profile to get all policy decisions for a given user / resource (or just everything for a user for multiple resources). Our idea here is to have Teiid set the action to be one of (SELECT|INSERT|UPDATE|DELETE|CREATE|DROP|EXECUTE) and the resource to be the fully qualified table (vdbName, SchemaName, TableName) plus a map of projected columns by the query. While this doesn't solve row-based restrictions, it would solve column / object based restrictions. MDP could be used to get policy decisions for all objects under a given schema. > Thoughts? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3259) dynamic sql cannot use into with updates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3259?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3259. ----------------------------------- Resolution: Done Added backwards compatibility and updated the docs / sqladmin materialization procs to use rowcount instead. > dynamic sql cannot use into with updates > ---------------------------------------- > > Key: TEIID-3259 > URL: https://issues.jboss.org/browse/TEIID-3259 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.9 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > TEIID-3198 refined the dynamic sql handling such that the use of AS columns required a result set from the query. However our materialization logic in SYSADMIN and our documentation indicated that the approach should be used. We may need to offer backward compatibility and at the very least should update the materialization sql. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2988) MongoDB: Function substring - starting index and number of arguments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2988?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2988: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1105101|https://bugzilla.redhat.com/show_bug.cgi?id=1105101] from MODIFIED to ON_QA > MongoDB: Function substring - starting index and number of arguments > -------------------------------------------------------------------- > > Key: TEIID-2988 > URL: https://issues.jboss.org/browse/TEIID-2988 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.8, 8.7.1, 8.10 > > > Two minor bugs in function substring() > Mongo's function $substr takes only 3 arguments so this query fails: > {code} > SELECT intkey, SUBSTRING(BQT1.SmallA.stringkey, 1) FROM BQT1.SmallA ORDER BY intkey > {code} > {code} > Exception:13:18:48,220 ERROR [org.teiid.CONNECTOR] (Worker38_QueryProcessorQueue345) Connector worker process failed for atomic-request=omsmHP0o16Sa.40.0.86: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: the $substr operator requires 3 operand(s)" , "code" : 16020 , "ok" : 0.0} > at com.mongodb.CommandResult.getException(CommandResult.java:71) > at com.mongodb.CommandResult.throwOnError(CommandResult.java:110) > at com.mongodb.DBCollection.aggregate(DBCollection.java:1308) > {code} > Generated mongo command: > {code} > { aggregate: "smalla", pipeline: [ { $project: { c_0: "$INTKEY", c_1: { $substr: [ "$STRINGKEY", 1 ] } } }, { $sort: { c_0: 1 } } ] } > {code} > Mongo's $substr function second argument represents number of bytes to skip, not the starting index. The function substring(StringKey,1,1) returns the second letter, but it should return the first letter. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2890) IndexOutOfBoundsException when using GROUP BY

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2890?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2890: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1167875|https://bugzilla.redhat.com/show_bug.cgi?id=1167875] from MODIFIED to ON_QA > IndexOutOfBoundsException when using GROUP BY > --------------------------------------------- > > Key: TEIID-2890 > URL: https://issues.jboss.org/browse/TEIID-2890 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: 8.7, grouping, translator > Fix For: 8.7 > > > I have a translator that does not support aggregates or grouping. I am using a view to try to normalize data from several sources. I am duplicating some of the fields as an approximation. I have existing software that is querying with GROUP BY, and sometimes this happens. > This query works fine in 8.6: > {code:sql} > select identifier > from foo.items > group by identifier, identifier; > {code} > In 8.7 this happens: > {code} > 10:15:24,280 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue39) njknuxobPkVY TEIID30019 Unexpected exception for request njknuxobPkVY.3: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1 > at java.util.ArrayList.rangeCheck(ArrayList.java:604) [rt.jar:1.7.0_02] > at java.util.ArrayList.get(ArrayList.java:382) [rt.jar:1.7.0_02] > at org.teiid.query.processor.relational.MergeJoinStrategy.compareTuples(MergeJoinStrategy.java:313) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.sameGroup(GroupingNode.java:488) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.groupPhase(GroupingNode.java:414) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:336) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:273) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3235) IndexOutOfBoundsException when using GROUP BY

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3235?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3235: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1167875|https://bugzilla.redhat.com/show_bug.cgi?id=1167875] from MODIFIED to ON_QA > IndexOutOfBoundsException when using GROUP BY > --------------------------------------------- > > Key: TEIID-3235 > URL: https://issues.jboss.org/browse/TEIID-3235 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1, 8.10 > > Attachments: mongo-vdb.xml > > > Issuing the following queries that cause the IndexOutofBoundsException: > SELECT IntKey, SUM(IntNum) FROM BQT1.SmallA GROUP BY intKey > SELECT IntKey, IntNum FROM BQT1.SmallA GROUP BY IntKey, IntNum > Will attach VDB. > 0:07:04,905 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue14) Connector worker process failed for atomic-request=XEIlvkzunTej.7.1.0: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1 > at java.util.ArrayList.rangeCheck(ArrayList.java:604) [rt.jar:1.7.0_25] > at java.util.ArrayList.get(ArrayList.java:382) [rt.jar:1.7.0_25] > at org.teiid.translator.mongodb.MongoDBQueryExecution.next(MongoDBQueryExecution.java:124) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:384) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:202) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.1.redhat-5.jar:8.7.1.redhat-5] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2014