April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2983) MongoDB: Function "count()" returns sum instead of number of rows

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2983?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2983. --------------------------------- > MongoDB: Function "count()" returns sum instead of number of rows > ----------------------------------------------------------------- > > Key: TEIID-2983 > URL: https://issues.jboss.org/browse/TEIID-2983 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.8, 8.7.1 > > > Function "count()" returns sum of rows instead of number of rows > Query [1] returns sum of values of all rows of IntKey column. > Query [2] correctly returns number of rows > > [1] SELECT COUNT(IntKey) FROM BQT1.SmallA > [2] SELECT COUNT(*) FROM BQT1.SmallA -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3103) ODBC fetch fails to send command complete

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3103?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3103. --------------------------------- > ODBC fetch fails to send command complete > ----------------------------------------- > > Key: TEIID-3103 > URL: https://issues.jboss.org/browse/TEIID-3103 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > If a fetch statement hits the fetch limit before the end of the results it fails to send a command complete. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2984) MongoDB: Usage of function "mod()" in SQL query throws an exception

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2984?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2984. --------------------------------- > MongoDB: Usage of function "mod()" in SQL query throws an exception > ------------------------------------------------------------------- > > Key: TEIID-2984 > URL: https://issues.jboss.org/browse/TEIID-2984 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Fix For: 8.8, 8.7.1 > > Attachments: server.log > > > Exception[1] is thrown when function modulo(mod) is used in SQL query. > Sample query: > SELECT LongNum, 11, MOD(LongNum, 11) FROM BQT1.SmallA ORDER BY LONGNUM > Server log is in the attachment. > [1] 16:36:59,645 ERROR [org.teiid.CONNECTOR] (Worker10_QueryProcessorQueue71) Connector worker process failed for atomic-request=hRCP8hHjrmZb.25.0.13: com.mongodb.CommandFailureException: { "serverUsed" : "localhost/127.0.0.1:27017" , "errmsg" : "exception: disallowed field type Array in object expression (at 'mod')" , "code" : 15992 , "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) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3212) Materialized Views Documentation Issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3212?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3212. --------------------------------- > Materialized Views Documentation Issues > --------------------------------------- > > Key: TEIID-3212 > URL: https://issues.jboss.org/browse/TEIID-3212 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 8.7 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Labels: alpha1 > Fix For: 8.10 > > > On the documentation page https://docs.jboss.org/author/display/teiid87final/External+Materialization there are several inconsistencies within the text: > 1. In doc property teiid_rel:MATVIEW_STAGE_TABLE is stated as optional, but in fact to activate the vdb setting of property teiid_rel:MATERIALIZED_STAGE_TABLE is required which is also in the sample code. > 2. teiid_rel:MATVIEW_TTL stated as optional, but if not set error occurs on deploy. > 3. In the table of properties is teiid_rel:ON_VDB_START_SCRIPT, but under the table there is teiid_rel:ON_VDB_CREATE_SCRIPT property. > 4. in the sample vdb definition the Cache Hint with the query is misleading, as the teiid_rel:MATVIEW_TTL is required. In sync with issue TEIID-3209. > On the https://docs.jboss.org/author/display/teiid87final/Internal+Materialization page: > 1. in section "Updatable" the "Update SQL" query calls wrong procedure. It calls updateMatViewRow, but should call refreshMatViewRow as is stated in the surrounding text. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3097) Model names should not be allowed to contain .

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3097?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3097. --------------------------------- > Model names should not be allowed to contain . > ---------------------------------------------- > > Key: TEIID-3097 > URL: https://issues.jboss.org/browse/TEIID-3097 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > The server should not allow model names to contain a . as that is not allowed by our resolving conventions. This has been enforced in designer, but is not yet validated on the runtime side. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2987) MongoDB: No rows are returned when a function is used in a where clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2987?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2987. --------------------------------- > MongoDB: No rows are returned when a function is used in a where clause > ----------------------------------------------------------------------- > > Key: TEIID-2987 > URL: https://issues.jboss.org/browse/TEIID-2987 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4.1 > Environment: Teiid 8.4.1 > Reporter: Filip Elias > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.8, 8.7.1 > > > Teiid will return no rows when a function which is pushed down is used in a where clause. > These queries should return few rows, but the result is empty: > Query: > {code} > SELECT intkey, stringnum FROM BQT1.SmallA WHERE concat(stringkey, stringnum) = '7-17' ORDER BY intkey > {code} > Generated mongo command: > {code} > {aggregate: "smalla", pipeline: [ { $match: { _m0: "7-17" } }, { $project: { c_0: "$INTKEY", c_1: "$STRINGNUM" } }, { $sort: { c_0: 1 } } ] } > {code} > Query: > {code} > select intKey from bqt1.smalla where intKey+intKey >20 > {code} > Generated mongo command: > {code} > {aggregate: "smalla", pipeline: [ { $match: { _m0: { $gt: 20 } } }, { $project: { _m1: "$INTKEY" } } ] } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3120) honor javax.sql.DataSource LoginTimeout

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3120?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3120. --------------------------------- > honor javax.sql.DataSource LoginTimeout > --------------------------------------- > > Key: TEIID-3120 > URL: https://issues.jboss.org/browse/TEIID-3120 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 8.4.2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.9 > > > setLoginTimeout is currently not honored. > Modify [1] to generate a reproducer. Use [2] in order to simulate an unresponsive Teiid instance. > > [1] > https://github.com/teiid/teiid-quickstarts/tree/8.4.x/simpleclient > add ds.setLoginTimeout(1) to JDBCClient.getDataSourceConnection > [2] > sudo iptables -I INPUT 1 -m state --state NEW -m tcp -p tcp --dport 31000 -j DROP -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3127) Multiple subquery arguments prevent plan completion

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3127?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3127. --------------------------------- > Multiple subquery arguments prevent plan completion > --------------------------------------------------- > > Key: TEIID-3127 > URL: https://issues.jboss.org/browse/TEIID-3127 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > The evaluator is closed after each successful evaluation, but the values are not saved so multiple subqueries in the same logical operation will cause indefinite blocking. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3115) Invalid Query With OrderBy in SubQuery Table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3115?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3115. --------------------------------- > Invalid Query With OrderBy in SubQuery Table > -------------------------------------------- > > Key: TEIID-3115 > URL: https://issues.jboss.org/browse/TEIID-3115 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.8 > Reporter: Joseph CHIDIAC > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > Hi, I'm using Teiid Embedded Server , i tried to execute the Following query : > > SELECT jiraissue.issuetype > FROM imOrganizationjiraissue jiraissue > LEFT OUTER JOIN > (SELECT jiraissue_sub.issuetype AS jiraissue_issuetype, > AVG( > TIMESTAMPDIFF(SQL_TSI_DAY, > jiraissue_sub.CREATED, > jiraissue_sub.RESOLUTIONDATE)) > AS CalculatedField > FROM jiraissue jiraissue_sub > GROUP BY jiraissue_sub.issuetype > ORDER BY AVG( > TIMESTAMPDIFF(SQL_TSI_DAY, > jiraissue_sub.CREATED, > jiraissue_sub.RESOLUTIONDATE)) ASC > LIMIT 2) j_Sub > ON jiraissue.issuetype = j_Sub.jiraissue_issuetype > > i verified the query sent to the JDBC [JDBCQueryExecution.java] > SELECT g_0.issuetype > FROM JIRADB.dbo.jiraissue g_0 > LEFT OUTER JOIN ( > SELECT TOP 2 g_1.issuetype AS c_0 > FROM JIRADB.dbo.jiraissue g_1 > GROUP BY g_1.issuetype > ORDER BY anon_grp0.agg0 > ) v_0 > ON g_0.issuetype = v_0.c_0 > > i got the following exception : > > java.sql.SQLException: The multi-part identifier "anon_grp0.agg0" could not be bound -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 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 closed TEIID-3259. --------------------------------- > 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.9.1, 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)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015