September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2441) Invalid character detected for charset {0}. The text may be encoded in a different charset.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2441?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2441. --------------------------------- > Invalid character detected for charset {0}. The text may be encoded in a different charset. > -------------------------------------------------------------------------------------------- > > Key: TEIID-2441 > URL: https://issues.jboss.org/browse/TEIID-2441 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.3 > Reporter: luca gioppo > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.4.1, 8.5 > > > The error could return a more clear statement -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2369) Query plan for continuous execution should be refreshed after alter command

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2369?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2369. --------------------------------- > Query plan for continuous execution should be refreshed after alter command > --------------------------------------------------------------------------- > > Key: TEIID-2369 > URL: https://issues.jboss.org/browse/TEIID-2369 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.1 > Environment: Windows > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.4 > > > When continuous queries are started on a view and the view is later altered, the change in the view definition is picked up. This is due to the query plan being cached at the time of initial execution. Following discussion contains more information- > https://community.jboss.org/thread/220761 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2487) Wrong aliasing when "supportsSelectExpression" is false in translator capabilities

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2487?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2487. --------------------------------- > Wrong aliasing when "supportsSelectExpression" is false in translator capabilities > ---------------------------------------------------------------------------------- > > Key: TEIID-2487 > URL: https://issues.jboss.org/browse/TEIID-2487 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.4 > > > When "supportsSelectExpression" is false, in the translator capabilities and user submits a query like > {code} > select sum (intnum) as "sum" from smalla group by intkey order by "sum" > {code} > the pushdown command at the translator is > {code} > SELECT SUM(SMALLA.INTNUM) FROM SMALLA GROUP BY SMALLA.INTKEY ORDER BY c_0 > {code} > The alias in the ORDER BY is wrong. Also do not understand why the query engine pushed the aggregate is being pushed, possibly due to "supportsAggregatesSum" is turned on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2549) Join planning produces cross joins with limited costing

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2549?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2549. --------------------------------- > Join planning produces cross joins with limited costing > ------------------------------------------------------- > > Key: TEIID-2549 > URL: https://issues.jboss.org/browse/TEIID-2549 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > The join planning logic does not gracefully handle a lack of costing information in effective cross joins (where there is still outside criteria). For example with a small table x that only has cardinality set and a large table y with no costing information, the join structure > from x inner join y as y1 on x.col = y1.col inner join y as y2 on x.col1 = y2.col1 > can result in a cross join plan between y1 and y2 (although the specifics of the plan may verify from version to version - in 7.7 the cross join will likely be pushed down, while in 8.4 a dependent join can be created depending upon the size of x, but can still produce a pushed cross join). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2423) add xml deployment for Teiid Embedded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2423?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2423. --------------------------------- > add xml deployment for Teiid Embedded > ------------------------------------- > > Key: TEIID-2423 > URL: https://issues.jboss.org/browse/TEIID-2423 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > We can accept a Reader for the VDBMetadataParser to turn into a VDBMetadata object for deployment (there is already a protected deplyVDB that takes VDBMetadata). There are some additional considerations here, such as allowing for vdb specific connector repositories and the setting of classloaders and other logic typically handled by a server deployment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2506) Additional row based security issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2506?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2506. --------------------------------- > Additional row based security issues > ------------------------------------ > > Key: TEIID-2506 > URL: https://issues.jboss.org/browse/TEIID-2506 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4 > > > On updates, constraints with values outside of the changelist will throw an exception. Also, non-compensated updates should always have the condition applied as a row filter - which currently it is not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2429) Large sort performance

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2429?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2429. --------------------------------- > Large sort performance > ---------------------- > > Key: TEIID-2429 > URL: https://issues.jboss.org/browse/TEIID-2429 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > Large sorts (high data volume over above several hundred thousand rows) experience a disproportionate performance degradation as the data set grows larger. > This is due to the SortUtility default collection strategy that will create intermediate sort buffers too proactively. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2437) Issuing query against SYS.VirtualDatabases causes SingleInstanceCommunicationException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2437?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2437. --------------------------------- > Issuing query against SYS.VirtualDatabases causes SingleInstanceCommunicationException > -------------------------------------------------------------------------------------- > > Key: TEIID-2437 > URL: https://issues.jboss.org/browse/TEIID-2437 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4 > > > Issuing query: select * from SYS.VirtualDatabases using Squirrel produces this error on client: > Error: org.teiid.net.socket.SingleInstanceCommunicationException > SQLState: 08S01 > ErrorCode: 0 > The server log shows this error: > 12:34:41,665 ERROR [org.teiid.TRANSPORT] (New I/O worker #1) Unhandled exception, closing client instance: org.teiid.core.TeiidRuntimeException: TEIID20001 The modeled datatype string for column 1 doesn't match the runtime type "java.lang.Integer". Please ensure that the column's modeled datatype matches the expected data. > at org.teiid.client.BatchSerializer.writeBatch(BatchSerializer.java:732) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.client.ResultsMessage.writeExternal(ResultsMessage.java:291) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) [rt.jar:1.7.0_13] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) [rt.jar:1.7.0_13] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) [rt.jar:1.7.0_13] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) [rt.jar:1.7.0_13] > at org.teiid.net.socket.Message.writeExternal(Message.java:56) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1443) [rt.jar:1.7.0_13] > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1414) [rt.jar:1.7.0_13] > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) [rt.jar:1.7.0_13] > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) [rt.jar:1.7.0_13] > at org.teiid.transport.ObjectEncoder.handleDownstream(ObjectEncoder.java:115) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.jboss.netty.channel.Channels.write(Channels.java:704) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1] > at org.jboss.netty.channel.Channels.write(Channels.java:671) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1] > at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) [netty-3.6.2.Final-redhat-1.jar:3.6.2.Final-redhat-1] > at org.teiid.transport.SSLAwareChannelHandler$ObjectChannelImpl.write(SSLAwareChannelHandler.java:94) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.transport.SocketClientInstance.send(SocketClientInstance.java:82) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.transport.ServerWorkItem.sendResult(ServerWorkItem.java:135) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.transport.ServerWorkItem$1.onCompletion(ServerWorkItem.java:105) [teiid-runtime-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:130) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:37) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75) [teiid-client-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.sendResultsIfNeeded(RequestWorkItem.java:785) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem$1.flushBatchDirect(RequestWorkItem.java:583) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.query.processor.BatchCollector.flushBatch(BatchCollector.java:191) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:166) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:400) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:296) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:224) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:253) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:123) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:298) [teiid-engine-8.3.0.Beta3-SNAPSHOT.jar:8.3.0.Beta3-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2499) timing issue with asynch results procssing

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2499?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2499. --------------------------------- > timing issue with asynch results procssing > ------------------------------------------ > > Key: TEIID-2499 > URL: https://issues.jboss.org/browse/TEIID-2499 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > If the first results are sent to the client before the nonblockingrowprocessor is attached as a completionlistener, then the client may effectively drop results and throw an AsynchPositioningException. This was seen with TestAsynch.testAsynchContinuousEmpty since effectively no processing is performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2494) View definition column naming issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2494?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2494. --------------------------------- > View definition column naming issue > ----------------------------------- > > Key: TEIID-2494 > URL: https://issues.jboss.org/browse/TEIID-2494 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > View definition columns that do not have names matching the view columns will not be named correctly if the view layer is preserved and pushed down. > for example: > SELECT MIN(x.count) FROM agg x > will fail with agg defined as > create foreign table smalla (intkey integer); > create view agg (count integer) as select count(\*) from smalla; > but will function correctly with count(\*) as count > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2013