Null values cause BLOB corruption
-
Key: JCR-551
URL: http://issues.apache.org/jira/browse/JCR-551
Project: Jackrabbit
Issue Type: Bug
Components: core
Affects Versions: 1.0.1
Hi Christoph,
the search index implementation uses a collection of lucene indexes
for performance reasons. To keep track of the indexes in use it
creates a file indexes with the index names.
the file ns_mappings.properties is a mapping of namespaces to index
internal prefixes to save
a common approach to this problem is to create an MD5 of the binary
data and store it with the resource. when a new resource is added to
the repository it could then search the repository for the MD5 of the
resource to add. if it already exists in the repository it could then
simply create a
Hi,
I also faced the same problem while working in Dreamweaver with Jackrabbit
repository.
1) Finally is it possible to use jackrabbit(1.0.1 war distribution)
repository
with Dreamweaver through webdav protocol for operation like CHECKIN
AND CHECKOUT. ?
Is problem with Dreamweaver
Move listeners from item state to item state managers
-
Key: JCR-552
URL: http://issues.apache.org/jira/browse/JCR-552
Project: Jackrabbit
Issue Type: Improvement
Components:
Hi Marcel,
as mentioned before the current search index implementation does not
work on the jackrabbit FileSystem abstraction. The reason is lack of
support for random access on the FileSystemResource which is a
performance killer when lucene is running on top of that.
Hm, I think all these
[ http://issues.apache.org/jira/browse/JCR-552?page=all ]
Dominique Pfister resolved JCR-552.
---
Resolution: Fixed
fixed in revision 438851.
Move listeners from item state to item state managers
-
Hm, sounds interesting, but wouldn't this only work with file system based
persistence managers? I mean, I can't imagine how to get an index with
decent
performance using a database based persistence manager in the near future?
Do
you already have an idea how achieve the needed performance?
Christoph Kiehl wrote:
in the long term I would like to put the index in the repository
itself. but that means that the repository (at least internally) has
to support random access on its binary resources.
Hm, sounds interesting, but wouldn't this only work with file system
based
[
http://issues.apache.org/jira/browse/JCR-551?page=comments#action_12431877 ]
Jaka Jaksic commented on JCR-551:
-
Oh, it's actually like this:
String propertyValue = null;
node.setProperty(corruptionTest, propertyValue,
Christoph Kiehl wrote:
I like the idea of having a transactional index but I don't think it's a
good idea to read this index from a binary property in a database,
because in our case we've got a fairly large repository where we got
index files with a size of 40MB. As far as I understand you
Hi,
first of all thanks for adding the SPI stuff, and apologies for not
having done anything with it earlier (as I was among those who asked for
it being in SVN even if work in progress).
I have now started to look at the SPI interfaces with an eye how I could
implement them for the backend
OutOfMemoryError when re-indexing the repository
In-Reply-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
[
http://issues.apache.org/jira/browse/JCR-550?page=comments#action_12431955 ]
Marcel Reutegger commented on
[ http://issues.apache.org/jira/browse/JCR-553?page=all ]
Marcel Reutegger resolved JCR-553.
--
Resolution: Fixed
I agree, the version in the project.properties is wrong.
Applied the patch in revision: 439039
Thank you for reporting this issue.
[ http://issues.apache.org/jira/browse/JCR-553?page=all ]
Marcel Reutegger closed JCR-553.
problem in jcr-server/project.properties dependencies?
--
Key: JCR-553
URL:
[
http://issues.apache.org/jira/browse/JCR-169?page=comments#action_12431999 ]
Ian Boston commented on JCR-169:
Search -
I assume this is the lucene indexes ?
If you havent got to it already
Im interested in this Jira becuase, I also want
16 matches
Mail list logo