[ http://issues.apache.org/jira/browse/JCR-202?page=all ]
Jan Kuzniak updated JCR-202:
Attachment: indexConfigurationPatch.zip
Ok, after quite a while of work here it comes. I was not as easy as I thought
and I had to change few parts of the code. If you
Hi,
I noticed that the time a query takes corresponds to the total size of the query
result. Digging into the code I found the following lines in
org.apache.jackrabbit.core.query.lucene.QueryImpl:
result = index.executeQuery(this, query, orderProperties, ascSpecs);
ids = new
you need to escape the name according to section 6.4.3 'Escaping of Names':
//element(prueba_x0020_fe.txt, okm:document)
regards
marcel
btw. this is rather a question for the jackrabbit user list...
Paco Avila wrote:
The question is about the element() sintax:
If I want to search all nodes
Hi,
The best way to solve your issue would be to somehow let the client
instruct the repository that only the first 20 results are needed.
Then there would be no need for any extra trickery.
Perhaps a Jackrabbit-specific extension (or something in JSR 283) like:
public interface
[ http://issues.apache.org/jira/browse/JCR-646?page=all ]
Marcel Reutegger resolved JCR-646.
--
Resolution: Fixed
Fixed in revision: 479587
Misleading exception message for jcr:deref()
Hi,
If setLimit is going to be implemented, then setOffset(long offset)
might as well be implemented at the same time (even if the first
implementation will not be optimized). Just from an API standpoint.
Thomas
On 11/27/06, Christoph Kiehl [EMAIL PROTECTED] wrote:
Jukka Zitting wrote:
The
Jukka Zitting wrote:
On 11/27/06, Christoph Kiehl [EMAIL PROTECTED] wrote:
1. Use a lazy QueryResultImpl that keeps a reference to the result and
only
fetches the UUIDs for requested nodes.
I much prefer this approach over adding yet another cache. :-)
I would prefer a solution that
Thomas Mueller wrote:
If setLimit is going to be implemented, then setOffset(long offset)
might as well be implemented at the same time (even if the first
implementation will not be optimized). Just from an API standpoint.
I think the same can be achieved with existing API calls, even though
Marcel Reutegger wrote:
Thomas Mueller wrote:
If setLimit is going to be implemented, then setOffset(long offset)
might as well be implemented at the same time (even if the first
implementation will not be optimized). Just from an API standpoint.
I think the same can be achieved with existing
Hi Florent,
What you describe is one of the backup tool use case. I am adding the last
touch to it so it can be committed it by hopefully next week (there is jut a
few home cleaning tasks to perform). If you need it faster, please contact
me privately so I can tell you which classes you need to
NullpointerException in SessionItemStateManager
---
Key: JCR-648
URL: http://issues.apache.org/jira/browse/JCR-648
Project: Jackrabbit
Issue Type: Bug
Components: core
Affects
11 matches
Mail list logo
