[
https://issues.apache.org/jira/browse/TAJO-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243810#comment-14243810
]
Hudson commented on TAJO-1239:
------------------------------
SUCCESS: Integrated in Tajo-master-build #501 (See
[https://builds.apache.org/job/Tajo-master-build/501/])
TAJO-1239 ORDER BY with null column desc miss some data. (Hyoungjun Kim via
hyunsik) (hyunsik: rev c7dd002a6e12b569e830396f84a32c832bf1e783)
*
tajo-storage/tajo-storage-common/src/main/java/org/apache/tajo/storage/BaseTupleComparator.java
*
tajo-storage/tajo-storage-common/src/test/java/org/apache/tajo/storage/TestTupleComparator.java
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestSortQuery.java
* CHANGES
> ORDER BY with null column desc miss some data.
> ----------------------------------------------
>
> Key: TAJO-1239
> URL: https://issues.apache.org/jira/browse/TAJO-1239
> Project: Tajo
> Issue Type: Bug
> Components: physical operator, planner/optimizer
> Reporter: Hyoungjun Kim
> Assignee: Hyoungjun Kim
> Priority: Minor
> Fix For: 0.9.1
>
>
> TAJO-904 fixed the ORDER BY ascending bug. But descending with null column
> still miss some data. I tested the following code.
> {code}
> KeyValueSet tableOptions = new KeyValueSet();
> tableOptions.set(StorageConstants.TEXT_DELIMITER,
> StorageConstants.DEFAULT_FIELD_DELIMITER);
> tableOptions.set(StorageConstants.TEXT_NULL, "\\\\N");
> Schema schema = new Schema();
> schema.addColumn("id", Type.INT4);
> schema.addColumn("name", Type.TEXT);
> String[] data = new String[]{ "1|111", "2|\\N", "3|333" };
> TajoTestingCluster.createTable("table11", schema, tableOptions, data, 1);
> try {
> ResultSet res = executeString("select * from table11 order by name asc");
> String ascExpected = "id,name\n" +
> "-------------------------------\n" +
> "1,111\n" +
> "3,333\n" +
> "2,null\n";
> assertEquals(ascExpected, resultSetToString(res));
> res.close();
> res = executeString("select * from table11 order by name desc");
> String descExpected = "id,name\n" +
> "-------------------------------\n" +
> "2,null\n" +
> "3,333\n" +
> "1,111\n";
> assertEquals(descExpected, resultSetToString(res));
> res.close();
> } finally {
> executeString("DROP TABLE table11 PURGE");
> }
> {code}
> The first query is successful, but the second query will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
