[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 NEW to MODIFIED
> 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.1#6329)
10 years
[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 NEW to MODIFIED
> 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.1#6329)
10 years
[JBoss JIRA] (TEIID-3142) Vanilla Hive sorting issue
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3142?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3142.
-----------------------------------
Resolution: Out of Date
TEIID-3156 or turning off order by support entirely can be used to address this. If we learn this is a more general issue, then we can look at disabling sort in some capacity for Hive out of the box.
> 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.1#6329)
10 years
[JBoss JIRA] (TEIID-3180) Use TEIID/hostname as default Kerberos principal name
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3180?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3180:
----------------------------------
Labels: (was: CR2)
Affects Version/s: 8.7
Component/s: JDBC Driver
Thanks Cristiano for these enhancements.
> Use TEIID/hostname as default Kerberos principal name
> -----------------------------------------------------
>
> Key: TEIID-3180
> URL: https://issues.jboss.org/browse/TEIID-3180
> Project: Teiid
> Issue Type: Enhancement
> Components: JDBC Driver
> Affects Versions: 8.7
> Reporter: Cristiano Nicolai
> Assignee: Ramesh Reddy
> Fix For: 8.9
>
>
> Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use TEIID as service name, combined with the hostname used to create the Teiid connection. This is to be used in case kerberosServicePrincipleName is not supplied in the connection properties.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (TEIID-3180) Use TEIID/hostname as default Kerberos principal name
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3180?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3180.
---------------------------------
Labels: CR2 (was: )
Assignee: Ramesh Reddy (was: Steven Hawkins)
Fix Version/s: 8.9
Resolution: Done
Yep, another great suggestion by [~cristiano.nicolai]. I accepted the pull and updated the documentation accordingly.
> Use TEIID/hostname as default Kerberos principal name
> -----------------------------------------------------
>
> Key: TEIID-3180
> URL: https://issues.jboss.org/browse/TEIID-3180
> Project: Teiid
> Issue Type: Enhancement
> Reporter: Cristiano Nicolai
> Assignee: Ramesh Reddy
> Labels: CR2
> Fix For: 8.9
>
>
> Enhancement for the client side of setting up JDBC connections using GSS API. Suggestion is to use TEIID as service name, combined with the hostname used to create the Teiid connection. This is to be used in case kerberosServicePrincipleName is not supplied in the connection properties.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (TEIID-3037) Incorrect odata4j jar name
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3037?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3037.
---------------------------------
> Incorrect odata4j jar name
> --------------------------
>
> Key: TEIID-3037
> URL: https://issues.jboss.org/browse/TEIID-3037
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.8
> Reporter: Cristiano Nicolai
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.7.1, 8.9
>
>
> When deploying Teiid 8.8.0.Final, odata4j fails to initialize due to the wrong jar name.
> MSC000001: Failed to start service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.teiid-odata-8.8.0.Final.war".main: JBAS018759: Failed to load module: deployment.teiid-odata-8.8.0.Final.war:main
> Module declaration is set as:
> <resource-root path="odata4j-core-0.8.0-SNAPSHOT-redhat.jar" />
> But the provided jar name is:
> odata4j-core-0.8.0-SNAPSHOT-redhat-redhat.jar
> There is an extra "-redhat" in the jar name.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (TEIID-2969) timestamp parse format issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2969?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2969.
---------------------------------
> timestamp parse format issues
> -----------------------------
>
> Key: TEIID-2969
> URL: https://issues.jboss.org/browse/TEIID-2969
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
>
> Oracle and Postgresql pushdown of parse/format of timestamps is generally incorrect as the format string is left unquoted. Also Postgresql does not support the same syntax as oracle.
> Also pushdown of timestampdiff is not correct for pg for fields other than DAY and YEAR. Fractional seconds are not implemented and all of the other fields seem to return just the calendar field difference, not the number of intervals different - e.g. the difference in hours for timestamps that are years apart is just the 24 hour difference.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (TEIID-2263) makedep makenotdep hints should allow for more complicated scenarios
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2263?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2263.
---------------------------------
> makedep makenotdep hints should allow for more complicated scenarios
> --------------------------------------------------------------------
>
> Key: TEIID-2263
> URL: https://issues.jboss.org/browse/TEIID-2263
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
> Attachments: dep.patch
>
>
> In the option clause makedep and makenotdep take what are typically fully-qualified names and mark all matching tables/views in the query. This is not generally a good idea. We should allow for something akin to oracle global table syntax (view.)*table to drill down more specifically. Ideally we'd also account for subqueries and set operations as well.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years