January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4693) mysql "booleans" translation issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4693?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4693. ----------------------------------- Resolution: Done This will be fixed automatically when using the native importer, but for Designer or existing DDL will require setting the native type of the affected boolean columns to tinyint(1) rather than bit that is reported by mysql. I'll make a note of this in the docs. > mysql "booleans" translation issues > ------------------------------------ > > Key: TEIID-4693 > URL: https://issues.jboss.org/browse/TEIID-4693 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 9.x > Reporter: Marco Ardito > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2, 9.1.3 > > > Fields defined as tinyint(1) in MySQL are reported as a bit type in JDBC, which is then mappeed in Teiid to boolean. However tinyint(1) does not behave as you would expect with bit. (see forum reference below for more details) at least, for instance, when it contains 0 as false and -1 as true (typical by vb/msaccess usage) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4693) mysql "booleans" translation issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4693?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4693: ---------------------------------- Component/s: JDBC Connector Fix Version/s: 9.2 9.1.3 Priority: Critical (was: Major) Modifying to critical as the default behavior leads to unexpected results - but that's mostly on MySQL... > mysql "booleans" translation issues > ------------------------------------ > > Key: TEIID-4693 > URL: https://issues.jboss.org/browse/TEIID-4693 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 9.x > Reporter: Marco Ardito > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2, 9.1.3 > > > Fields defined as tinyint(1) in MySQL are reported as a bit type in JDBC, which is then mappeed in Teiid to boolean. However tinyint(1) does not behave as you would expect with bit. (see forum reference below for more details) at least, for instance, when it contains 0 as false and -1 as true (typical by vb/msaccess usage) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4695) Provide a better error with an invalid skipToken

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4695?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4695: ---------------------------------- Summary: Provide a better error with an invalid skipToken (was: Provide a better error with an invalid error code) > Provide a better error with an invalid skipToken > ------------------------------------------------ > > Key: TEIID-4695 > URL: https://issues.jboss.org/browse/TEIID-4695 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Kylin Soong > Priority: Optional > Fix For: 9.3 > > > The error message from an invalid skipToken could be improved - however users should not manually enter skipTokens. Similar errors still occur with our OData4 as the StringTokenizer used for the token will hit a no such element exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4695) Provide a better error with an invalid error code

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4695: ------------------------------------- Summary: Provide a better error with an invalid error code Key: TEIID-4695 URL: https://issues.jboss.org/browse/TEIID-4695 Project: Teiid Issue Type: Bug Components: OData Reporter: Steven Hawkins Assignee: Kylin Soong Priority: Optional Fix For: 9.3 The error message from an invalid skipToken could be improved - however users should not manually enter skipTokens. Similar errors still occur with our OData4 as the StringTokenizer used for the token will hit a no such element exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4622) Adding new data quality functions from osDQ

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4622?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4622: --------------------------------------- Updated the release notes and docs about adding a prefix to the functions. > Adding new data quality functions from osDQ > ------------------------------------------- > > Key: TEIID-4622 > URL: https://issues.jboss.org/browse/TEIID-4622 > Project: Teiid > Issue Type: Feature Request > Components: Common > Affects Versions: Open To Community > Environment: osdq-core and its dependency simmetric 3.0.0 is needed to run these functions > maven central location > http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22osdq-core%22 > Reporter: vivek singh > Assignee: Kylin Soong > Fix For: 9.2 > > Attachments: DateUtil.java, NumberUtil.java, StringUtil.java > > > Following functions have been added into osdq-core for integration with teiid. > String functions : > // Encrypting a string using key and AES encryption > String encrypt ( String val, String key) > String decrypt ( String val, String key) > // Fuzzy distance - similarity between two strings > float levestheindistance ( String a, String b) > float jarowinklerdistance( String a , String b) > float cosinedistance (String a, String b) > // Format check for PII ( personal information) > boolean isCreditCardFormat(String a) > boolean isSSNFormat(String a) > boolean isPhoneFormat(String a) > boolean isEmailFormat(String a) > boolean hasWhiteSpace(String a ) > Date Functions > // converting date into universal recognized format > long dateToEpoch(java.util.Date date) > Date epochToDate(long epoch) > Date epochToDate(long epoch, String TimeZone) > long diffInSec(date a, date b) > String convertToFormat ( Date a, String Format) > Numerical Functions > // Statistical functions > double stdDev(Number[] numSeries) > double range(Number[] numSeries) > double median(Number[] numSeries) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4622) Adding new data quality functions from osDQ

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4622?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4622: ---------------------------------- Fix Version/s: 9.2 (was: Open To Community) > Adding new data quality functions from osDQ > ------------------------------------------- > > Key: TEIID-4622 > URL: https://issues.jboss.org/browse/TEIID-4622 > Project: Teiid > Issue Type: Feature Request > Components: Common > Affects Versions: Open To Community > Environment: osdq-core and its dependency simmetric 3.0.0 is needed to run these functions > maven central location > http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22osdq-core%22 > Reporter: vivek singh > Assignee: Kylin Soong > Fix For: 9.2 > > Attachments: DateUtil.java, NumberUtil.java, StringUtil.java > > > Following functions have been added into osdq-core for integration with teiid. > String functions : > // Encrypting a string using key and AES encryption > String encrypt ( String val, String key) > String decrypt ( String val, String key) > // Fuzzy distance - similarity between two strings > float levestheindistance ( String a, String b) > float jarowinklerdistance( String a , String b) > float cosinedistance (String a, String b) > // Format check for PII ( personal information) > boolean isCreditCardFormat(String a) > boolean isSSNFormat(String a) > boolean isPhoneFormat(String a) > boolean isEmailFormat(String a) > boolean hasWhiteSpace(String a ) > Date Functions > // converting date into universal recognized format > long dateToEpoch(java.util.Date date) > Date epochToDate(long epoch) > Date epochToDate(long epoch, String TimeZone) > long diffInSec(date a, date b) > String convertToFormat ( Date a, String Format) > Numerical Functions > // Statistical functions > double stdDev(Number[] numSeries) > double range(Number[] numSeries) > double median(Number[] numSeries) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 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 reassigned TEIID-4694: ------------------------------------- Fix Version/s: 9.2.1 Assignee: Kylin Soong (was: Steven Hawkins) > 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.1 > > > 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)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4633) Odata $expand over Oracle tables generates bad query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4633?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4633. ----------------------------------- Fix Version/s: 9.1.3 Resolution: Done Added a new capability to capture that array/row value expressions are not supported for projection by oracle. > Odata $expand over Oracle tables generates bad query > ---------------------------------------------------- > > Key: TEIID-4633 > URL: https://issues.jboss.org/browse/TEIID-4633 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, OData > Affects Versions: 9.1.1 > Reporter: Sergio Samayoa > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.2, 9.1.3 > > > Query generated to obtain referenced records ($expand many to one) is generated with parentheses, > Generated query for Oracle*: > SELECT g_0."CATEGORY_ID", (g_0."CATEGORY_ID", g_0."NAME", g_0."LAST_UPDATE") FROM "SAKILA"."CATEGORY" g_0 > Generated query for MySQL is: > SELECT g_0.category_id, g_0.name, g_0.last_update FROM Sakila.category AS g_0 > * Note the parentheses enclosing all columns but PK, this raises "ORA-00907: missing right parenthesis". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

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

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4686?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4686: ------------------------------------- Ordering by Ordinal - If you mean *ORDER BY 1,2*, the issue applies even for *ORDER BY Col1, Col2*. > 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.1 > > > 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)

7 years, 5 months

1
0
0 / 0

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

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4694?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-4694: -------------------------------- Summary: PrestoDB translator - NULL values not supported in SemiJoin (was: PrestoDB tranlator - NULL values not supported in SemiJoin) > 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: Steven Hawkins > > 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)

7 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2017