[
https://issues.apache.org/jira/browse/TRAFODION-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488343#comment-15488343
]
ASF GitHub Bot commented on TRAFODION-2219:
-------------------------------------------
GitHub user zellerh opened a pull request:
https://github.com/apache/incubator-trafodion/pull/699
[TRAFODION-2219] charsets regression failures and retrieved columns
Fixed a problem with occasional failures of regressions, due to
non-deterministic order of results.
Also changed the way we show the number of "retrieved columns" for
Hive and ORC scans. The EXPLAIN now only shows the number of
actually needed columns, not all of them.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zellerh/incubator-trafodion bug/fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/699.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #699
----
commit cda727ac3615543abf5558c2d87b9bce4dda206c
Author: Hans Zeller <[email protected]>
Date: 2016-09-13T20:33:45Z
[TRAFODION-2219] charsets regression failures and retrieved columns
Fixed a problem with occasional failures of regressions, due to
non-deterministic order of results.
Also changed the way we show the number of "retrieved columns" for
Hive and ORC scans. The EXPLAIN now only shows the number of
actually needed columns, not all of them.
----
> Non-determinstic result order in charsets tests
> -----------------------------------------------
>
> Key: TRAFODION-2219
> URL: https://issues.apache.org/jira/browse/TRAFODION-2219
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-general
> Affects Versions: 2.0-incubating
> Reporter: Hans Zeller
> Assignee: Hans Zeller
> Fix For: 2.1-incubating
>
>
> We have seen failures in regression tests charsets/TEST310 and TEST311, due
> to queries that used an ORDER BY, yet produced a non-deterministic order.
> Adding another column to the ORDER BY will fix that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
