[JBoss JIRA] (TEIID-3117) NullPointerException while creating source model from Excel table
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3117?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3117:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1138697|https://bugzilla.redhat.com/show_bug.cgi?id=1138697] from MODIFIED to ON_QA
> NullPointerException while creating source model from Excel table
> -----------------------------------------------------------------
>
> Key: TEIID-3117
> URL: https://issues.jboss.org/browse/TEIID-3117
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Environment: Fedora 20, data virtualization 6.1.0.ER1
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Labels: Beta1
> Fix For: 8.7.1, 8.9
>
> Attachments: ExcelDynamic-vdb.xml, Server.log, smalla.xlsx, smalla_raw.xlsx
>
>
> I am trying to create source model from Excel file (.xlsx). When I set property "Header Row Number" to 1 (using Teiid Designer), creating ends with NullPointerException. Setting "Header Row Number" to 0 executes with no problems.
> Same problem (and same exception) with dynamic VDB (only with <property name="importer.headerRowNumber" value="1"/>).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[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 MODIFIED to ON_QA
> 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
> Fix For: 8.7.1, 8.9
>
> Attachments: server.log
>
>
> 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.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3141) Bad result of query with GROUB BY clause (underlying sybase15 datasource)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3141?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3141:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1146501|https://bugzilla.redhat.com/show_bug.cgi?id=1146501] from MODIFIED to ON_QA
> Bad result of query with GROUB BY clause (underlying sybase15 datasource)
> -------------------------------------------------------------------------
>
> Key: TEIID-3141
> URL: https://issues.jboss.org/browse/TEIID-3141
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7.1
> Environment: OS: fedora20
> arch: x86_64
> java: sun 1.7
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Description:
> There is sybase15 database with table named SmallA and table named SmallA in VDB which is mapped to sybase table (see tables definition below).
> I am trying to run query against VDB:
> SELECT
> INTKEY, STRINGKEY, INTNUM, STRINGNUM, FLOATNUM, LONGNUM, DOUBLENUM, BYTENUM, DATEVALUE, TIMEVALUE, TIMESTAMPVALUE, BOOLEANVALUE, CHARVALUE, SHORTVALUE, BIGINTEGERVALUE, BIGDECIMALVALUE
> FROM
> BQT1.SMALLA
> GROUP BY
> INTKEY, STRINGKEY, INTNUM, STRINGNUM, FLOATNUM, LONGNUM, DOUBLENUM, BYTENUM, DATEVALUE, TIMEVALUE, TIMESTAMPVALUE, BOOLEANVALUE, CHARVALUE, SHORTVALUE, BIGINTEGERVALUE, BIGDECIMALVALUE
> Result is table which misses some values (the other values are OK):
> FloatNum: always 0
> ByteNum: always 0
> DateValue: always 1900-01-01
> TimeValue: always 00:00:00
> BooleanValue: always 'false'
> CharValue: always empty character
> ShortValue: always 0
> BigIntegerValue: always 0
> BigDecimalValue: always 0
> After removing 'INTKEY' and 'STRINGKEY' from the query is result OK (sybase15 has indices only for these two columns).
> ///////////////////
> Table definition
> ///////////////////
> SmallA (sybase) has these columns (name:type):
> IntKey:int -> PRIMARY KEY, HAS INDEX
> StringKey:varchar -> HAS INDEX
> IntNum:int
> StringNum:varchar
> FloatNum:float
> LongNum:numeric
> DoubleNum:float
> ByteNum:real
> DateValue:datetime
> TimeValue:datetime
> TimestampValue:datetime
> BooleanValue:tinyint
> CharValue:char
> ShortValue:numeric
> BigIntegerValue:numeric
> BigDecimalValue:numeric
> ObjectValue:text
> SmallA (VDB) has these columns (name:type):
> IntKey:integer
> StringKey:string
> IntNum:integer
> StringNum:string
> FloatNum:float
> LongNum:long
> DoubleNum:double
> ByteNum:byte
> DateValue:date
> TimeValue:time
> TimestampValue:timestamp
> BooleanValue:boolean
> CharValue:char
> ShortValue:short
> BigIntegerValue:biginteger
> BigDecimalValue:bigdecimal
> ObjectValue:object
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3142) Vanilla Hive sorting issue
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3142?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3142:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1146522|https://bugzilla.redhat.com/show_bug.cgi?id=1146522] from MODIFIED to ON_QA
> Vanilla Hive sorting issue
> --------------------------
>
> Key: TEIID-3142
> URL: https://issues.jboss.org/browse/TEIID-3142
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Filip Nguyen
> Assignee: Steven Hawkins
>
> It seems that Vanilla Apache Hive 0.13 sorts in a yet another different way than what we expect and also differently from Cloudera Imapla (another Hive flavor).
> SELECT BQT1.SmallA.StringNum FROM BQT1.SmallA order by BQT1.SmallA.StringNum
> 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
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months
[JBoss JIRA] (TEIID-3156) Provide a mechanism to turn off string sorting
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3156?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3156:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1146522|https://bugzilla.redhat.com/show_bug.cgi?id=1146522] from MODIFIED to ON_QA
> Provide a mechanism to turn off string sorting
> ----------------------------------------------
>
> Key: TEIID-3156
> URL: https://issues.jboss.org/browse/TEIID-3156
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9
>
>
> Currently we don't have a fine grained mechanism to turn off source sorting of specifically string data. If a source is using a different collation for example and cannot be set on a session basis (that could be configured on the datasource) to an ansi/utf collation, then at least for join scenarios we have to process the sort in the engine. Optionally the user may wan the Teiid default collation enforced even for other sorts.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 7 months