October 2014 - teiid-issues - Jboss List Archives

[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 MODIFIED 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 > Fix For: 8.7.1, 8.9 > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3186) PARSETIMESTAMP('12:10:10', 'hh:mm:ss') returns 00:10:10

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-3186?page=com.atlassian.jira.plugin... ] Filip Nguyen updated TEIID-3186: -------------------------------- Affects Version/s: 8.7 > PARSETIMESTAMP('12:10:10', 'hh:mm:ss') returns 00:10:10 > ------------------------------------------------------- > > Key: TEIID-3186 > URL: https://issues.jboss.org/browse/TEIID-3186 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > This > {noformat} > SELECT PARSETIMESTAMP('12:10:10', 'hh:mm:ss'), PARSETIMESTAMP('13:10:10', 'hh:mm:ss') > {noformat} > returns > {noformat} > 1970-01-01 00:10:10.0,1970-01-01 13:10:10.0 > {noformat} > It seems odd to me. Shouldnt the result of PARSETIMESTAMP('12:10:10'... be 12:10:10? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3186) PARSETIMESTAMP('12:10:10', 'hh:mm:ss') returns 00:10:10

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-3186?page=com.atlassian.jira.plugin... ] Filip Nguyen updated TEIID-3186: -------------------------------- Component/s: Query Engine > PARSETIMESTAMP('12:10:10', 'hh:mm:ss') returns 00:10:10 > ------------------------------------------------------- > > Key: TEIID-3186 > URL: https://issues.jboss.org/browse/TEIID-3186 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > > This > {noformat} > SELECT PARSETIMESTAMP('12:10:10', 'hh:mm:ss'), PARSETIMESTAMP('13:10:10', 'hh:mm:ss') > {noformat} > returns > {noformat} > 1970-01-01 00:10:10.0,1970-01-01 13:10:10.0 > {noformat} > It seems odd to me. Shouldnt the result of PARSETIMESTAMP('12:10:10'... be 12:10:10? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3186) PARSETIMESTAMP('12:10:10', 'hh:mm:ss') returns 00:10:10

by Filip Nguyen (JIRA)

Filip Nguyen created TEIID-3186: ----------------------------------- Summary: PARSETIMESTAMP('12:10:10', 'hh:mm:ss') returns 00:10:10 Key: TEIID-3186 URL: https://issues.jboss.org/browse/TEIID-3186 Project: Teiid Issue Type: Bug Reporter: Filip Nguyen Assignee: Steven Hawkins This {noformat} SELECT PARSETIMESTAMP('12:10:10', 'hh:mm:ss'), PARSETIMESTAMP('13:10:10', 'hh:mm:ss') {noformat} returns {noformat} 1970-01-01 00:10:10.0,1970-01-01 13:10:10.0 {noformat} It seems odd to me. Shouldnt the result of PARSETIMESTAMP('12:10:10'... be 12:10:10? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

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

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ] Filip Nguyen commented on TEIID-3134: ------------------------------------- What are the semantics of "low, high"? I tested with int, string and timestamp columns and it seems that Impala puts the nulls at the end of the result set. > 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, 2 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 commented on TEIID-3134: --------------------------------------- There is a code change that is applicable. We can set the source's default null ordering and Teiid will compensate appropriately. Do you know the actual ordering impala uses - high, low, first, last? > 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, 2 months

1
0
0 / 0

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

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ] Filip Nguyen commented on TEIID-3134: ------------------------------------- Is it possible to modify null order by some translator property? > 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, 2 months

1
0
0 / 0

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

by Filip Nguyen (JIRA)

[ https://issues.jboss.org/browse/TEIID-3134?page=com.atlassian.jira.plugin... ] Filip Nguyen commented on TEIID-3134: ------------------------------------- Ah you are correct, the only issue is that impala sorts null first that caused test failures, my interpretation of the cause was bad. > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3184) pg metadata always reports column names as lower case

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3184?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3184: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1156168|https://bugzilla.redhat.com/show_bug.cgi?id=1156168] from NEW to ASSIGNED > pg metadata always reports column names as lower case > ----------------------------------------------------- > > Key: TEIID-3184 > URL: https://issues.jboss.org/browse/TEIID-3184 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > The result set metadata is reporting the column name in lower case regardless of the submitted query. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3175) Allow property lookup on function parameters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3175?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3175. ----------------------------------- Resolution: Done Assigned uids to function parameters and added them into the appropriate system tables. > Allow property lookup on function parameters > -------------------------------------------- > > Key: TEIID-3175 > URL: https://issues.jboss.org/browse/TEIID-3175 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > FunctionParameters until TEIID-3044 were not first class metadata objects, so now we need to round out support them including extension metadata lookup. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2014