You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "David Geary (JIRA)" <ji...@apache.org> on 2010/11/05 17:00:58 UTC
[jira] Created: (JCR-2806) Search Result Ordering Incorrect
Search Result Ordering Incorrect
--------------------------------
Key: JCR-2806
URL: https://issues.apache.org/jira/browse/JCR-2806
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core, query
Affects Versions: 2.1.2
Environment: Linux, JRE 1.6.0_07
Reporter: David Geary
The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
This seems to be a very specific case, since any of the following stop the problem occuring:
- Removing the NodeType.MIX_VERSIONABLE from the test node type.
- Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
- Removing the where clause from the query (ie using the commented out query instead)
It seems to be something to do with setting the propeties on the nodes since the one that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2806) Search Result Ordering Incorrect
Posted by "David Geary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Geary updated JCR-2806:
-----------------------------
Attachment: repository.xml
JackRabbitOrderingTest.java
> Search Result Ordering Incorrect
> --------------------------------
>
> Key: JCR-2806
> URL: https://issues.apache.org/jira/browse/JCR-2806
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, query
> Affects Versions: 2.1.2
> Environment: Linux, JRE 1.6.0_07
> Reporter: David Geary
> Attachments: JackRabbitOrderingTest.java, repository.xml
>
>
> The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
> This seems to be a very specific case, since any of the following stop the problem occuring:
> - Removing the NodeType.MIX_VERSIONABLE from the test node type.
> - Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
> - Removing the where clause from the query (ie using the commented out query instead)
> It seems to be something to do with setting the propeties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2806) Search Result Ordering Incorrect
Posted by "David Geary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Geary updated JCR-2806:
-----------------------------
Attachment: (was: repository.xml)
> Search Result Ordering Incorrect
> --------------------------------
>
> Key: JCR-2806
> URL: https://issues.apache.org/jira/browse/JCR-2806
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, query
> Affects Versions: 2.1.2
> Environment: Linux, JRE 1.6.0_07
> Reporter: David Geary
> Attachments: JackRabbitOrderingTest.java, repository.xml
>
>
> The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
> This seems to be a very specific case, since any of the following stop the problem occuring:
> - Removing the NodeType.MIX_VERSIONABLE from the test node type.
> - Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
> - Removing the where clause from the query (ie using the commented out query instead)
> It seems to be something to do with setting the propeties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2806) Search Result Ordering Incorrect
Posted by "David Geary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Geary updated JCR-2806:
-----------------------------
Attachment: repository.xml
JackRabbitOrderingTest.java
Sample code to demonstrate the problem. This was run against the latest 2.1.2 release and the standard sample repository.xml (also attached)
> Search Result Ordering Incorrect
> --------------------------------
>
> Key: JCR-2806
> URL: https://issues.apache.org/jira/browse/JCR-2806
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, query
> Affects Versions: 2.1.2
> Environment: Linux, JRE 1.6.0_07
> Reporter: David Geary
> Attachments: JackRabbitOrderingTest.java, repository.xml
>
>
> The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
> This seems to be a very specific case, since any of the following stop the problem occuring:
> - Removing the NodeType.MIX_VERSIONABLE from the test node type.
> - Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
> - Removing the where clause from the query (ie using the commented out query instead)
> It seems to be something to do with setting the propeties on the nodes since the one that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2806) Search Result Ordering Incorrect
Posted by "David Geary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Geary updated JCR-2806:
-----------------------------
Description:
The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
This seems to be a very specific case, since any of the following stop the problem occuring:
- Removing the NodeType.MIX_VERSIONABLE from the test node type.
- Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
- Removing the where clause from the query (ie using the commented out query instead)
It seems to be something to do with setting the properties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
was:
The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
This seems to be a very specific case, since any of the following stop the problem occuring:
- Removing the NodeType.MIX_VERSIONABLE from the test node type.
- Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
- Removing the where clause from the query (ie using the commented out query instead)
It seems to be something to do with setting the propeties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
> Search Result Ordering Incorrect
> --------------------------------
>
> Key: JCR-2806
> URL: https://issues.apache.org/jira/browse/JCR-2806
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, query
> Affects Versions: 2.1.2
> Environment: Linux, JRE 1.6.0_07
> Reporter: David Geary
> Attachments: JackRabbitOrderingTest.java, repository.xml
>
>
> The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
> This seems to be a very specific case, since any of the following stop the problem occuring:
> - Removing the NodeType.MIX_VERSIONABLE from the test node type.
> - Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
> - Removing the where clause from the query (ie using the commented out query instead)
> It seems to be something to do with setting the properties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2806) Search Result Ordering Incorrect
Posted by "David Geary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Geary updated JCR-2806:
-----------------------------
Description:
The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
This seems to be a very specific case, since any of the following stop the problem occuring:
- Removing the NodeType.MIX_VERSIONABLE from the test node type.
- Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
- Removing the where clause from the query (ie using the commented out query instead)
It seems to be something to do with setting the propeties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
was:
The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
This seems to be a very specific case, since any of the following stop the problem occuring:
- Removing the NodeType.MIX_VERSIONABLE from the test node type.
- Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
- Removing the where clause from the query (ie using the commented out query instead)
It seems to be something to do with setting the propeties on the nodes since the one that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
> Search Result Ordering Incorrect
> --------------------------------
>
> Key: JCR-2806
> URL: https://issues.apache.org/jira/browse/JCR-2806
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, query
> Affects Versions: 2.1.2
> Environment: Linux, JRE 1.6.0_07
> Reporter: David Geary
> Attachments: JackRabbitOrderingTest.java, repository.xml
>
>
> The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
> This seems to be a very specific case, since any of the following stop the problem occuring:
> - Removing the NodeType.MIX_VERSIONABLE from the test node type.
> - Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
> - Removing the where clause from the query (ie using the commented out query instead)
> It seems to be something to do with setting the propeties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2806) Search Result Ordering Incorrect
Posted by "David Geary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Geary updated JCR-2806:
-----------------------------
Attachment: (was: JackRabbitOrderingTest.java)
> Search Result Ordering Incorrect
> --------------------------------
>
> Key: JCR-2806
> URL: https://issues.apache.org/jira/browse/JCR-2806
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, query
> Affects Versions: 2.1.2
> Environment: Linux, JRE 1.6.0_07
> Reporter: David Geary
> Attachments: JackRabbitOrderingTest.java, repository.xml
>
>
> The attached code demonstrates a situation where a query which specifies an order by node name is returning results in the wrong order.
> This seems to be a very specific case, since any of the following stop the problem occuring:
> - Removing the NodeType.MIX_VERSIONABLE from the test node type.
> - Commenting out the line properties.put("property6", "value6"); ie only using 5 properties instead of 6.
> - Removing the where clause from the query (ie using the commented out query instead)
> It seems to be something to do with setting the propeties on the nodes since the ones that have had properties set seem to be 'moved' to a different place in the result list. Also I tested this with the same node set up using an import of the node data instead and this had the same problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.