January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4705) correct the nvl pushdown for the impala translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4705?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4705: ------------------------------------- Looks like Impala translator translator fine according to https://www.cloudera.com/documentation/enterprise/5-8-x/topics/impala_con... Where as for Hive this seems to the one wrong https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF > correct the nvl pushdown for the impala translator > -------------------------------------------------- > > Key: TEIID-4705 > URL: https://issues.jboss.org/browse/TEIID-4705 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Johnathon Lee > Assignee: Steven Hawkins > > queries consisting of the nvl(x, y) function will fail since JDV translates to isnull(x,y) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4705) correct the nvl pushdown for the impala translator

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-4705: ------------------------------------ Summary: correct the nvl pushdown for the impala translator Key: TEIID-4705 URL: https://issues.jboss.org/browse/TEIID-4705 Project: Teiid Issue Type: Bug Components: Misc. Connectors Reporter: Johnathon Lee Assignee: Steven Hawkins queries consisting of the nvl(x, y) function will fail since JDV translates to isnull(x,y) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4704) Importing Flat File with "-" character in one column of the header

by Pedro Inácio (JIRA)

Pedro Inácio created TEIID-4704: ----------------------------------- Summary: Importing Flat File with "-" character in one column of the header Key: TEIID-4704 URL: https://issues.jboss.org/browse/TEIID-4704 Project: Teiid Issue Type: Bug Affects Versions: 9.1.2 Environment: CentOs 7 + Teiid 9.1.2 with Wildfly 10.0.0.Final + Eclipse Neon with Designer 11. Reporter: Pedro Inácio Assignee: Steven Hawkins Trying to create a simple Flat File View Model from aCSV file with the following content: {code:java} "a-a","b" 1,2 3,4 {code} Teiid server gives the following exception {noformat} [org.teiid.RUNTIME] (Worker6_async-teiid-threads6) TEIID50036 VDB PREVIEW-80ce0d21-f22d-431f-bd12-89ac57ac9418.1 model "ViewModel" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "new_table ( a[*]-[*]a string" at line 3, column 10. Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...: org.teiid.metadata.ParseException: TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "new_table ( a[*]-[*]a string" at line 3, column 10. Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ... at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:472) at org.teiid.metadata.MetadataFactory.parse(MetadataFactory.java:798) at org.teiid.query.metadata.DDLMetadataRepository.loadMetadata(DDLMetadataRepository.java:40) at org.teiid.runtime.AbstractVDBDeployer$MetadataRepositoryWrapper.loadMetadata(AbstractVDBDeployer.java:84) at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) at org.teiid.jboss.VDBService$6.run(VDBService.java:360) at org.teiid.jboss.VDBService$7.run(VDBService.java:411) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "new_table ( a[*]-[*]a string" at line 3, column 10. Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ... at org.teiid.query.parser.QueryParser.convertParserException(QueryParser.java:214) ... 13 more {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4702) Clarify that JDG is what's supported, not infinispan

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4702?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4702. ----------------------------------- Fix Version/s: 9.2 Resolution: Done Merged the pull request. > Clarify that JDG is what's supported, not infinispan > ---------------------------------------------------- > > Key: TEIID-4702 > URL: https://issues.jboss.org/browse/TEIID-4702 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 9.2 > > > The documentation related to supporting Infinispan as a data source should be clarified that its JDG that is supported. Referencing Infinispan when its not really the intention of the data source integration, causes confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4702) Clarify that JDG is what's supported, not infinispan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4702?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4702: ------------------------------------ Yes, documentation only. > Clarify that JDG is what's supported, not infinispan > ---------------------------------------------------- > > Key: TEIID-4702 > URL: https://issues.jboss.org/browse/TEIID-4702 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > The documentation related to supporting Infinispan as a data source should be clarified that its JDG that is supported. Referencing Infinispan when its not really the intention of the data source integration, causes confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4702) Clarify that JDG is what's supported, not infinispan

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4702?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4702: --------------------------------------- Just to make sure, this is a doc only change - the names of the managed connection factories won't change? > Clarify that JDG is what's supported, not infinispan > ---------------------------------------------------- > > Key: TEIID-4702 > URL: https://issues.jboss.org/browse/TEIID-4702 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > The documentation related to supporting Infinispan as a data source should be clarified that its JDG that is supported. Referencing Infinispan when its not really the intention of the data source integration, causes confusion. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4694) PrestoDB translator - NULL values not supported in SemiJoin

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4694?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4694: ---------------------------------- Fix Version/s: 9.2 (was: 9.2.1) > PrestoDB translator - NULL values not supported in SemiJoin > ----------------------------------------------------------- > > Key: TEIID-4694 > URL: https://issues.jboss.org/browse/TEIID-4694 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.8.6_3 > Reporter: Juraj Duráni > Assignee: Kylin Soong > Fix For: 9.2 > > > PrestoDB does not allows NULL values in SemiJoin operator. It means, that query like \[1\] causes an exception \[2\]. However, this is disallowed in version 0.162 but worked in 0.161. According to GitHub issues \[3\], this will be fixed in one of the future versions of PrestoDB. Do we want to handle it somehow? > Development and release frequency of PrestoDB seems to be pretty fast (new release every 2 or 3 week). > {code:sql|title=\[1\] Query} > SELECT IntKey, ShortValue FROM BQT1.SmallA WHERE BQT1.SmallA.ShortValue IN (SELECT ShortValue FROM BQT1.SmallB) > {code} > {code:plain|title=\[2\] Exception} > org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 Source: Unexpected exception while translating results: Query failed (#20170110_072908_00117_gftb8): NULL values are not allowed on the probe side of SemiJoin operator. See the query plan for details. > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > ... > Caused by: java.lang.RuntimeException: Remote com.facebook.presto.jdbc.internal.client.FailureInfo$FailureException: NULL values are not allowed on the probe side of SemiJoin operator. See the query plan for details. > at com.facebook.presto.operator.HashSemiJoinOperator.addInput(HashSemiJoinOperator.java:179) > at com.facebook.presto.operator.Driver.processInternal(Driver.java:384) > at com.facebook.presto.operator.Driver.processFor(Driver.java:301) > at com.facebook.presto.execution.SqlTaskExecution$DriverSplitRunner.processFor(SqlTaskExecution.java:622) > at com.facebook.presto.execution.TaskExecutor$PrioritizedSplitRunner.process(TaskExecutor.java:534) > at com.facebook.presto.execution.TaskExecutor$Runner.run(TaskExecutor.java:670) > ... 3 more > {code} > \[3\] https://github.com/prestodb/presto/issues/6991 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4703) The Oracle translator did not limit the number of values in "IN" clause, which were required by Oracle database.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4703?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4703: --------------------------------------- It does default to 1000. There must be some missing details to the scenario that you are describing. > The Oracle translator did not limit the number of values in "IN" clause, which were required by Oracle database. > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4703 > URL: https://issues.jboss.org/browse/TEIID-4703 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.13.4 > Reporter: SHI HONG CHIN > Assignee: Steven Hawkins > > Database: Oracle + Firebird + Microsoft SQL Server. > Oracle limit the maximum number of values in "IN" clause to 1000. > In teiid, I am using the built-in Oracle translator. > When running some SQL queries, Oracle database reported an error "No more data to read from socket". I had set the log level of Teiid to "ALL". According to the WildFly log files, Teiid executed a query with more than 10000 values in the "IN" clause. > I tried to copy the whole SQL from WildFly log file into Oracle SQL Developer and execute it, the same error occurred. Then, I tried to edit the query by delete many values from the "IN" clause and then run the query again, and the query success. > For teiid, as a workaround, I overrided the oracle translator and set the property of "MaxInCriteriaSize" to 50. After that, all SQL queries run success without any issue. > I suggest that, by default, the built-in Oracle translator limit the number of values in "IN" clause to maximum 1000 values, and this behavior can be changed through properties. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4686) PrestoDB translator - ordering of joined tables fails

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4686?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4686: ---------------------------------- Fix Version/s: 9.2 (was: 9.2.1) > PrestoDB translator - ordering of joined tables fails > ----------------------------------------------------- > > Key: TEIID-4686 > URL: https://issues.jboss.org/browse/TEIID-4686 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.8.6_3 > Reporter: Juraj Duráni > Assignee: Kylin Soong > Fix For: 9.2 > > > Issuing query like \[1\] causes an exception in PrestoDB. This seems to be PrestoDB issue. I found similar issue \[2\], but that one should be fixed. I have created a new issue \[3\]. Removing one column from ORDER BY, query returns correct result. > Not sure if we can do something about it without avoiding pushing JOIN. > I suggest either to fix this (if simple enough) or add a note to the documentation. > \[1\] > {code:sql} > SELECT a.intkey, b.intkey FROM BQT1.SmallA AS a INNER JOIN BQT1.SmallB AS b on a.intkey = b.intkey ORDER BY 1, 2 > {code} > \[2\] https://github.com/prestodb/presto/issues/1621 > \[3\] https://github.com/prestodb/presto/issues/7010 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3952) Update to updatable internal materialized view should update the materialized view as well as the database

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3952?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3952: --------------------------------------- Many of the rewrite rules for insert/update/delete would need to be altered or moved into the planner so as when possible the view access is being removed or a procedure plan is being created instead. Either way the planner then does not see the simple form of the update command. It should take about 2-3 days to address that and produce an alternative plan that performs both updates. > Update to updatable internal materialized view should update the materialized view as well as the database > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-3952 > URL: https://issues.jboss.org/browse/TEIID-3952 > Project: Teiid > Issue Type: Enhancement > Components: VDB > Affects Versions: 8.7 > Environment: Red Hat JBoss Data Virtualization 6.2 based on Teiid 8.7.x > Reporter: Andy Yuen > Assignee: Steven Hawkins > Labels: jboss > Fix For: 9.2 > > > Updating an updatable internal materized view updates the database but not the materialized view at present. The requested enhancement is that they, both, should be updated. > Setup > Client - SquirrelSQL to access JDV > JDV 6.2 - with an updatable nternal materialized view of one table from the data source > Data Source - just one data source: MySQL > I can see from the console that the target table/view has been materialized > Then I did the following: > 1) select a row from the materialized table > 2) update a field in a row in the materialized view > 3) select that row (value unchanged ie, same as int 1) - tried multiple times > 4) issue EXEC SYSADMIN.refreshMatViewRow(...) using primary key for the row that has been changed > 5) select that row (value unchanged) - now I can see the changed data > This behaviour is counter-intuitive because I was expecting that since it is an updatable materialized view, my change will write through the materialized view ie, change both the materialized view as well as the database. But in this case, it changed the database and not the materialized view? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017