June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3243) MongoDB: doens't support more than 1 aggregation in SQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3243?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3243. --------------------------------- > MongoDB: doens't support more than 1 aggregation in SQL > -------------------------------------------------------- > > Key: TEIID-3243 > URL: https://issues.jboss.org/browse/TEIID-3243 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.8 > Environment: MongoDB with Teiid > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.10 > > > Got exception if I have more than 1 aggregation in SQL for MongoDB: > Original SQL > SELECT COUNT(MongoNestedDocDS.addresst.age) AS c_0, SUM(MongoNestedDocDS.addres > st.age) AS c_1 FROM MongoNestedDocDS.addresst LIMIT 1000 > Got exception: > Caused by: org.teiid.jdbc.TeiidSQLException: TEIID30504 -1880007235: TEIID18024 multiple aggregate symbols are not sup > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:667) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:63) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:515) > at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:511) > at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:261) > at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:233) > Can we consider to use in memory engine instead if more than 1 aggregation? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3123) Exception when using dense_rank() in Teiid Development

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3123?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3123. --------------------------------- > Exception when using dense_rank() in Teiid Development > ------------------------------------------------------ > > Key: TEIID-3123 > URL: https://issues.jboss.org/browse/TEIID-3123 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.8 > Reporter: Joseph CHIDIAC > Assignee: Steven Hawkins > Fix For: 8.9 > > > SELECT DISTINCT > subQueryTable.jiraissue_ASSIGNEE AS jiraissue_ASSIGNEE, > dense_rank() over(order by subQueryTable.jiraissue_ID DESC) as CalculatedField1 > FROM jiraissue > LEFT OUTER JOIN > (SELECT jiraissue_sub.ASSIGNEE AS jiraissue_ASSIGNEE, > COUNT(IFNULL(jiraissue_sub.ID, -2147483648)) > AS jiraissue_ID > FROM jiraissue jiraissue_sub > WHERE ((jiraissue_sub.RESOLUTIONDATE BETWEEN NULL > AND PARSETIMESTAMP( > '2014-09-10 18:46:28', > 'yyyy-MM-dd HH:mm:ss'))) > GROUP BY jiraissue_sub.ASSIGNEE) subQueryTable > ON jiraissue.ASSIGNEE = > subQueryTable.jiraissue_ASSIGNEE > > The query sent to the JDBC : > SELECT DISTINCT DENSE_RANK() OVER (ORDER BY NULL DESC) FROM "JIRADB"."dbo"."jiraissue" g_0 > > and i got this error : > > java.sql.SQLException: Windowed functions do not support constants as ORDER BY clause expressions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2584) Add management features to materialization

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2584. --------------------------------- > Add management features to materialization > ------------------------------------------ > > Key: TEIID-2584 > URL: https://issues.jboss.org/browse/TEIID-2584 > Project: Teiid > Issue Type: Feature Request > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.5 > > > Currently Teiid supports internal and external materialization features. The internal is managed completely by the Teiid query engine along with the infinispan cache. > External materialization is completely unmanaged and left out to the user to manage it externally. This goals for this feature are unify the materialization logic for internal and external, such that both are managed similarly irrespective of the type of materialization chosen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2845) MongoDB: Join processing produces wrong results in some cases

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2845?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2845. --------------------------------- > MongoDB: Join processing produces wrong results in some cases > ------------------------------------------------------------- > > Key: TEIID-2845 > URL: https://issues.jboss.org/browse/TEIID-2845 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: alpha3, mongodb > Fix For: 8.7 > > > When two or more tables are used to build single document in the MongoDB, depending upon the JOIN query used it may produce wrong results. > - support for inner is not turned ON, this should be allowed > - For example cross-join between parent and embedded table > - right-join between parent and embedded table > - depending upon the parent the ordering of left and right join -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3063) Push down DISTINCT with select expression in the query and the datasource doesn't support select expressions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3063?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3063. --------------------------------- > Push down DISTINCT with select expression in the query and the datasource doesn't support select expressions > ------------------------------------------------------------------------------------------------------------- > > Key: TEIID-3063 > URL: https://issues.jboss.org/browse/TEIID-3063 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.7 > Environment: Windows > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Fix For: 8.9 > > > Teiid doesn't push down DISTINCT when a select expression is used and the underlying data source doesn't support select expressions. The data source supports DISTINCT. > Related discussion thread: https://community.jboss.org/thread/243376 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2406) Quickstart to demonstrate custom database appender logger

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2406?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2406. --------------------------------- > Quickstart to demonstrate custom database appender logger > --------------------------------------------------------- > > Key: TEIID-2406 > URL: https://issues.jboss.org/browse/TEIID-2406 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Van Halbert > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2481) common table (with) push down improvements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2481?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2481. --------------------------------- > common table (with) push down improvements > ------------------------------------------ > > Key: TEIID-2481 > URL: https://issues.jboss.org/browse/TEIID-2481 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > > The general strategy for with pushdown should better handle: > - a with clause that can be pushed against a source that does not support common table. If a single reference or some other sufficient condition is met then we should just inline the pushdown rather than inhibiting the whole query from pushing down. > - even if a source supports with pushdown, it may be more performant in some circumstances to inline the common table reference (such as only a single reference). This is complicated slightly by subqueries. > - alternatively in some situations even if a with clause can be pushed, it may be better to not perform the pushdown -e.g. two separate pushdown accesses to a common table that is expensive to compute (this may need to be hint driven). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3055) Querying JDG local cache using greater than value cause exception

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3055?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3055. --------------------------------- > Querying JDG local cache using greater than value cause exception > ----------------------------------------------------------------- > > Key: TEIID-3055 > URL: https://issues.jboss.org/browse/TEIID-3055 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.9 > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > Issuing query: select nss, valor_inicial, valor_final from CacheView.Resumen where valor_inicial > 950.0 > produces the following in the query plan: > USER COMMAND: > SELECT nss, valor_inicial, valor_final FROM CacheView.Resumen WHERE nss > '950.0' > request=/1MuNPfoG76j.0.0.5: org.hibernate.search.SearchException: Cannot create numeric range query for field saldo.valorInicial, since values are not numeric (int,long, short or double) > at org.hibernate.search.bridge.util.impl.NumericFieldUtils.createNumericRangeQuery(NumericFieldUtils.java:69) > at org.hibernate.search.query.dsl.impl.ConnectedMultiFieldsRangeQueryBuilder.createQuery(ConnectedMultiFieldsRangeQueryBuilder.java:107) > at org.hibernate.search.query.dsl.impl.ConnectedMultiFieldsRangeQueryBuilder.createQuery(ConnectedMultiFieldsRangeQueryBuilder.java:83) > at org.teiid.translator.object.infinispan.LuceneSearch.createRangeAboveQuery(LuceneSearch.java:349) > at org.teiid.translator.object.infinispan.LuceneSearch.visit(LuceneSearch.java:217) > at org.teiid.translator.object.infinispan.LuceneSearch.buildQueryFromWhereClause(LuceneSearch.java:145) > at org.teiid.translator.object.infinispan.LuceneSearch.performSearch(LuceneSearch.java:66) > at org.teiid.translator.object.infinispan.InfinispanExecutionFactory.search(InfinispanExecutionFactory.java:119) > at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:102) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:312) [te -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2882) Add support for Presto DB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2882?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2882. --------------------------------- > Add support for Presto DB > ------------------------- > > Key: TEIID-2882 > URL: https://issues.jboss.org/browse/TEIID-2882 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.10 > > > Presto is an open source distributed SQL query engine for running interactive analytic queries against data sources of all sizes ranging from gigabytes to petabytes. > Presto was designed and written from the ground up for interactive analytics and approaches the speed of commercial data warehouses while scaling to the size of organizations like Facebook. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2839) Selection of nested document based on non primary key does not work on MongoDB Translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2839?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2839. --------------------------------- > Selection of nested document based on non primary key does not work on MongoDB Translator > ----------------------------------------------------------------------------------------- > > Key: TEIID-2839 > URL: https://issues.jboss.org/browse/TEIID-2839 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha3, mongodb > Fix For: 8.7 > > > When a table is either EMBEDDED or MERGED into a parent table, issuing a "SELECT" query using WHERE clause that uses a NON primary key results in empty result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 June 2015