You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/10/03 20:48:41 UTC
[jira] [Resolved] (JCR-3677) Invalid
SQL2OrderByTest.testOrderByScore test case
[ https://issues.apache.org/jira/browse/JCR-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-3677.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.7.2
Assignee: Jukka Zitting
Fixed in revision 1528966 by using SCORE() instead of [jcr:score] and simply verifying that the returned rows have an ascending sequence of scores.
> Invalid SQL2OrderByTest.testOrderByScore test case
> --------------------------------------------------
>
> Key: JCR-3677
> URL: https://issues.apache.org/jira/browse/JCR-3677
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.7.1
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 2.7.2
>
>
> The SQL2OrderByTest.testOrderByScore test case makes a query like the following:
> SELECT * FROM [nt:base] WHERE ISCHILDNODE([/testroot])
> ORDER BY [jcr:score]
> The test then expects that he matching nodes are returned in a specific order. This is wrong on two counts:
> 1) The score of a search result is defined only for full text queries. It is meaningless for other queries and undefined by the spec.
> 2) Even if the score was a defined for such queries, the SQL2 syntax for accessing it is "SCORE()", not "[jcr:score]".
> Thus I suggest to either remove the test case or to make it use full text search and/or just verify that the results are ordered according to their scores instead of being in any specific predetermined order.
--
This message was sent by Atlassian JIRA
(v6.1#6144)