[
https://jira.jboss.org/jira/browse/DNA-613?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-613:
-----------------------------------
Found several minor issues that all conspired to make this functionality not work.
1) The XPathToQueryTranslator was incorrectly translating queries that used wildcards in
the path.
2) Queries that used aliases in columns, criteria, or order-by clauses were not always
being resolved correctly, resulting in the inability to locate the correct column (when
constraints or order-by clauses had to be evaluated after the fact.
3) The optimizer was not always pushing SELECT nodes (e.g., criteria) down below ACCESS
nodes. The rule to do this was not included by default and was instead added to the rule
stack only when criteria were encountered. This was changed to simply always add the rule
to the stack.
4) Columns used in constraints or order-by clauses were not always being included in the
PROJECT columns. Thus it was possible that the evaluation of the criteria or order-by
required data that was not in the tuples, causing an error. Note that these PROJECT
columns dictate which values are included in the tuples during processing, and all of
these are not necessarily included in the result columns.
5) The LuceneSearchEngine was incorrectly mapping paths into criteria values that could be
applied to Lucene. If the user specified a criteria such as
PATH(table) LIKE '/Cars/Hybrid/%'
the "/Cars/Hybrid/%" value was used directly as the LIKE expression. But paths
are stored in the indexes so that the SNS index is always included, and thus the LIKE
expressions never evaluated to return any documents. Since the SNS index in the path might
include the wildcard characters (e.g., '[%]' or '[_]'), we couldn't
use the standard PathFactory to convert the LIKE expression value into a Path. The
solution was to just use String manipulation to insert a '[1]' at the end of each
segment that didn't already include a SNS index.
6) Lucene 'read past EOF' errors; see DNA-630.
XPath order-by clause is not working
------------------------------------
Key: DNA-613
URL:
https://jira.jboss.org/jira/browse/DNA-613
Project: DNA
Issue Type: Bug
Components: JCR, Query
Affects Versions: 0.7
Reporter: Randall Hauch
Assignee: Randall Hauch
Priority: Blocker
Fix For: 0.7
The JCR extension to XPath that adds support for 'order by' is not working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira