September 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3119) Improve full sort performance for dup removal and grouping

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3119?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3119. ----------------------------------- Resolution: Done Marking as resolved. There is additional work that can be done to support the rollup and group/sort/distinct combination, but this new logic should cover the most common cases. > Improve full sort performance for dup removal and grouping > ---------------------------------------------------------- > > Key: TEIID-3119 > URL: https://issues.jboss.org/browse/TEIID-3119 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > We perform a full sort for grouping/distinct reusing the existing sorting logic. This is not as efficient as it could for larger data sets with smaller numbers of groups. A hash implementation or combining the grouping with the sorting would perform better. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3125) Netezza translator - add support for the LIKE_REGEX predicate.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3125: ---------------------------------- Issue Type: Enhancement (was: Feature Request) Fix Version/s: 8.9 > Netezza translator - add support for the LIKE_REGEX predicate. > -------------------------------------------------------------- > > Key: TEIID-3125 > URL: https://issues.jboss.org/browse/TEIID-3125 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.9 > > > With version 6 of Jboss DV the Netezza translator doesn't support the LIKE_REGEX predicate. > Netezza doesn't support regular expression by default, but with the installation of SQL Extensions toolkit this functionality is added. After installation Netezza provide the regular expression functions: > regexp_extract() > regexp_extract_all() > regexp_extract_all_sp() > regexp_extract_sp() > regexp_instr() > regexp_like() > regexp_match_count() > regexp_replace() > regexp_replace_sp() > IBM Netezza SQL Extensions toolkit is an optional package for IBM Netezza data warehouse appliances. > After installing this toolkit on Netezza and requires that regular expression in JBoss DV syntax are pushed down (delegated) to Netezza to prevent that filtering in the Jboss DV server most be done. > So please provide a configurable option in the Netezza translator of Jboss DV by which we can enable the LIKE_REGEX predicate for Netezza. This option when enabled will assume that the Netezza SQL extension toolkit is installed and the function regexp_like() is available. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3125) Netezza translator - add support for the LIKE_REGEX predicate.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3125: --------------------------------------- Unless there is good way to glean support from the databasemetadata we'll just need to add a translator property that will show pushdown support for like_regex. We can also look into adding the other regexp_ functions as pushdown functions. > Netezza translator - add support for the LIKE_REGEX predicate. > -------------------------------------------------------------- > > Key: TEIID-3125 > URL: https://issues.jboss.org/browse/TEIID-3125 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > With version 6 of Jboss DV the Netezza translator doesn't support the LIKE_REGEX predicate. > Netezza doesn't support regular expression by default, but with the installation of SQL Extensions toolkit this functionality is added. After installation Netezza provide the regular expression functions: > regexp_extract() > regexp_extract_all() > regexp_extract_all_sp() > regexp_extract_sp() > regexp_instr() > regexp_like() > regexp_match_count() > regexp_replace() > regexp_replace_sp() > IBM Netezza SQL Extensions toolkit is an optional package for IBM Netezza data warehouse appliances. > After installing this toolkit on Netezza and requires that regular expression in JBoss DV syntax are pushed down (delegated) to Netezza to prevent that filtering in the Jboss DV server most be done. > So please provide a configurable option in the Netezza translator of Jboss DV by which we can enable the LIKE_REGEX predicate for Netezza. This option when enabled will assume that the Netezza SQL extension toolkit is installed and the function regexp_like() is available. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3134) Impala sorting Issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3134: ---------------------------------- Assignee: (was: Steven Hawkins) That's an odd ordering. Are other types besides string affected as well? If so we can just turn off order by support. > Impala sorting Issue > -------------------- > > Key: TEIID-3134 > URL: https://issues.jboss.org/browse/TEIID-3134 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > > String sorting of impala is inconsistent with our expectations: > Impala sorting > --------------------------- > SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA > Results > 1: -1 > 2: -10 > 3: -11 > 4: -12 > 5: -13 > 6: -14 > 7: -15 > 8: -16 > 9: -17 > 10: -18 > 11: -19 > 12: -2 > 13: -20 > 14: -21 > 15: -22 > 16: -24 > 17: -3 > 18: -4 > 19: -5 > 20: -6 > 21: -8 > 22: -9 > 23: 0 > 24: 1 > 25: 10 > 26: 11 > 27: 12 > 28: 13 > 29: 14 > 30: 15 > 31: 16 > 32: 17 > 33: 18 > 34: 19 > 35: 2 > 36: 20 > 37: 21 > 38: 22 > 39: 23 > 40: 24 > 41: 3 > 42: 4 > 43: 5 > 44: 6 > 45: 7 > 46: 8 > 47: null > 48: null > 49: null > 50: null > Expected > --------------------------- > While we expect sorting to be consistent with other sources: > 1: 0 > 2: 1 > 3: -1 > 4: 10 > 5: -10 > 6: 11 > 7: -11 > 8: 12 > 9: -12 > 10: 13 > 11: -13 > 12: 14 > 13: -14 > 14: 15 > 15: -15 > 16: 16 > 17: -16 > 18: 17 > 19: -17 > 20: 18 > 21: -18 > 22: 19 > 23: -19 > 24: 2 > 25: -2 > 26: 20 > 27: -20 > 28: 21 > 29: -21 > 30: 22 > 31: -22 > 32: 23 > 33: 24 > 34: -24 > 35: 3 > 36: -3 > 37: 4 > 38: -4 > 39: 5 > 40: -5 > 41: 6 > 42: -6 > 43: 7 > 44: 8 > 45: -8 > 46: -9 > 47: null > 48: null > 49: null > 50: null -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3133) Impala Time/Date/Timestamp handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3133?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3133: --------------------------------------- What is the full exception? Presumably it's failing on ResultSet.getTimestamp. > Impala Time/Date/Timestamp handling > ----------------------------------- > > Key: TEIID-3133 > URL: https://issues.jboss.org/browse/TEIID-3133 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Impala supports only TIMESTAMP datatype (see here http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/lates...) > Converted everything into timestamp and now I am trying to get Date and Time parts of the timestamp in Teiid e.g. > SELECT DISTINCT convert(Source.SmallA.TimeValue, time) as TimeValue FROM Source.SmallA ORDER BY TimeValue > But I get TranslatorException: Unexpected exception while translating results: Method not supported > Tried to workaround this but with limited success. For Date it is possible to use to_date function that returns string reprsentation of the date part. For Time I wasn't able to find the solution (have not yet figured out how to use extract function through Teiid). > http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/lates... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3133) Impala Time/Date/Timestamp handling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3133?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3133: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1141685|https://bugzilla.redhat.com/show_bug.cgi?id=1141685] from NEW to ASSIGNED > Impala Time/Date/Timestamp handling > ----------------------------------- > > Key: TEIID-3133 > URL: https://issues.jboss.org/browse/TEIID-3133 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Impala supports only TIMESTAMP datatype (see here http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/lates...) > Converted everything into timestamp and now I am trying to get Date and Time parts of the timestamp in Teiid e.g. > SELECT DISTINCT convert(Source.SmallA.TimeValue, time) as TimeValue FROM Source.SmallA ORDER BY TimeValue > But I get TranslatorException: Unexpected exception while translating results: Method not supported > Tried to workaround this but with limited success. For Date it is possible to use to_date function that returns string reprsentation of the date part. For Time I wasn't able to find the solution (have not yet figured out how to use extract function through Teiid). > http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/lates... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3134) Impala sorting Issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3134: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1141162 > Impala sorting Issue > -------------------- > > Key: TEIID-3134 > URL: https://issues.jboss.org/browse/TEIID-3134 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > String sorting of impala is inconsistent with our expectations: > Impala sorting > --------------------------- > SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA > Results > 1: -1 > 2: -10 > 3: -11 > 4: -12 > 5: -13 > 6: -14 > 7: -15 > 8: -16 > 9: -17 > 10: -18 > 11: -19 > 12: -2 > 13: -20 > 14: -21 > 15: -22 > 16: -24 > 17: -3 > 18: -4 > 19: -5 > 20: -6 > 21: -8 > 22: -9 > 23: 0 > 24: 1 > 25: 10 > 26: 11 > 27: 12 > 28: 13 > 29: 14 > 30: 15 > 31: 16 > 32: 17 > 33: 18 > 34: 19 > 35: 2 > 36: 20 > 37: 21 > 38: 22 > 39: 23 > 40: 24 > 41: 3 > 42: 4 > 43: 5 > 44: 6 > 45: 7 > 46: 8 > 47: null > 48: null > 49: null > 50: null > Expected > --------------------------- > While we expect sorting to be consistent with other sources: > 1: 0 > 2: 1 > 3: -1 > 4: 10 > 5: -10 > 6: 11 > 7: -11 > 8: 12 > 9: -12 > 10: 13 > 11: -13 > 12: 14 > 13: -14 > 14: 15 > 15: -15 > 16: 16 > 17: -16 > 18: 17 > 19: -17 > 20: 18 > 21: -18 > 22: 19 > 23: -19 > 24: 2 > 25: -2 > 26: 20 > 27: -20 > 28: 21 > 29: -21 > 30: 22 > 31: -22 > 32: 23 > 33: 24 > 34: -24 > 35: 3 > 36: -3 > 37: 4 > 38: -4 > 39: 5 > 40: -5 > 41: 6 > 42: -6 > 43: 7 > 44: 8 > 45: -8 > 46: -9 > 47: null > 48: null > 49: null > 50: null -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3134) Impala sorting Issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3134: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1141162|https://bugzilla.redhat.com/show_bug.cgi?id=1141162] from NEW to ASSIGNED > Impala sorting Issue > -------------------- > > Key: TEIID-3134 > URL: https://issues.jboss.org/browse/TEIID-3134 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > String sorting of impala is inconsistent with our expectations: > Impala sorting > --------------------------- > SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA > Results > 1: -1 > 2: -10 > 3: -11 > 4: -12 > 5: -13 > 6: -14 > 7: -15 > 8: -16 > 9: -17 > 10: -18 > 11: -19 > 12: -2 > 13: -20 > 14: -21 > 15: -22 > 16: -24 > 17: -3 > 18: -4 > 19: -5 > 20: -6 > 21: -8 > 22: -9 > 23: 0 > 24: 1 > 25: 10 > 26: 11 > 27: 12 > 28: 13 > 29: 14 > 30: 15 > 31: 16 > 32: 17 > 33: 18 > 34: 19 > 35: 2 > 36: 20 > 37: 21 > 38: 22 > 39: 23 > 40: 24 > 41: 3 > 42: 4 > 43: 5 > 44: 6 > 45: 7 > 46: 8 > 47: null > 48: null > 49: null > 50: null > Expected > --------------------------- > While we expect sorting to be consistent with other sources: > 1: 0 > 2: 1 > 3: -1 > 4: 10 > 5: -10 > 6: 11 > 7: -11 > 8: 12 > 9: -12 > 10: 13 > 11: -13 > 12: 14 > 13: -14 > 14: 15 > 15: -15 > 16: 16 > 17: -16 > 18: 17 > 19: -17 > 20: 18 > 21: -18 > 22: 19 > 23: -19 > 24: 2 > 25: -2 > 26: 20 > 27: -20 > 28: 21 > 29: -21 > 30: 22 > 31: -22 > 32: 23 > 33: 24 > 34: -24 > 35: 3 > 36: -3 > 37: 4 > 38: -4 > 39: 5 > 40: -5 > 41: 6 > 42: -6 > 43: 7 > 44: 8 > 45: -8 > 46: -9 > 47: null > 48: null > 49: null > 50: null -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3134) Impala sorting Issue

by Van Halbert (JIRA)

Van Halbert created TEIID-3134: ---------------------------------- Summary: Impala sorting Issue Key: TEIID-3134 URL: https://issues.jboss.org/browse/TEIID-3134 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.7.1 Reporter: Van Halbert Assignee: Steven Hawkins String sorting of impala is inconsistent with our expectations: Impala sorting --------------------------- SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA Results 1: -1 2: -10 3: -11 4: -12 5: -13 6: -14 7: -15 8: -16 9: -17 10: -18 11: -19 12: -2 13: -20 14: -21 15: -22 16: -24 17: -3 18: -4 19: -5 20: -6 21: -8 22: -9 23: 0 24: 1 25: 10 26: 11 27: 12 28: 13 29: 14 30: 15 31: 16 32: 17 33: 18 34: 19 35: 2 36: 20 37: 21 38: 22 39: 23 40: 24 41: 3 42: 4 43: 5 44: 6 45: 7 46: 8 47: null 48: null 49: null 50: null Expected --------------------------- While we expect sorting to be consistent with other sources: 1: 0 2: 1 3: -1 4: 10 5: -10 6: 11 7: -11 8: 12 9: -12 10: 13 11: -13 12: 14 13: -14 14: 15 15: -15 16: 16 17: -16 18: 17 19: -17 20: 18 21: -18 22: 19 23: -19 24: 2 25: -2 26: 20 27: -20 28: 21 29: -21 30: 22 31: -22 32: 23 33: 24 34: -24 35: 3 36: -3 37: 4 38: -4 39: 5 40: -5 41: 6 42: -6 43: 7 44: 8 45: -8 46: -9 47: null 48: null 49: null 50: null -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3133) Impala Time/Date/Timestamp handling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3133?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3133: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1141685 > Impala Time/Date/Timestamp handling > ----------------------------------- > > Key: TEIID-3133 > URL: https://issues.jboss.org/browse/TEIID-3133 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Impala supports only TIMESTAMP datatype (see here http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/lates...) > Converted everything into timestamp and now I am trying to get Date and Time parts of the timestamp in Teiid e.g. > SELECT DISTINCT convert(Source.SmallA.TimeValue, time) as TimeValue FROM Source.SmallA ORDER BY TimeValue > But I get TranslatorException: Unexpected exception while translating results: Method not supported > Tried to workaround this but with limited success. For Date it is possible to use to_date function that returns string reprsentation of the date part. For Time I wasn't able to find the solution (have not yet figured out how to use extract function through Teiid). > http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/lates... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2014