[
https://issues.apache.org/jira/browse/JCR-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836553#action_12836553
]
Martijn Hendriks commented on JCR-2503:
---
We regularly encounter inconsistent Jackrabbit
High memory usage on node with multi-valued string properties
-
Key: JCR-2505
URL: https://issues.apache.org/jira/browse/JCR-2505
Project: Jackrabbit Content Repository
Issue Type:
Stop text extraction when the maxFieldLength limit is reached
-
Key: JCR-2506
URL: https://issues.apache.org/jira/browse/JCR-2506
Project: Jackrabbit Content Repository
Issue Type:
[
https://issues.apache.org/jira/browse/JCR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836601#action_12836601
]
Cédric Damioli commented on JCR-2505:
-
do you mean lucene tokenizer ?
what about non-whit
JcrValueType#typeFromContentType throws IllegalArgumentException for type
weak-ref and uri
--
Key: JCR-2507
URL: https://issues.apache.org/jira/browse/JCR-2507
Pr
[
https://issues.apache.org/jira/browse/JCR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2505:
--
Status: Patch Available (was: Open)
> High memory usage on node with multi-valued string propert
[
https://issues.apache.org/jira/browse/JCR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2505:
--
Attachment: JCR-2505.patch
> High memory usage on node with multi-valued string properties
>
[
https://issues.apache.org/jira/browse/JCR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836699#action_12836699
]
Marcel Reutegger commented on JCR-2505:
---
> do you mean lucene tokenizer ?
yes.
actua
[
https://issues.apache.org/jira/browse/JCR-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2507.
-
Resolution: Fixed
Fix Version/s: 2.1.0
> JcrValueType#typeFromContentType throws IllegalArgumentException fo
[
https://issues.apache.org/jira/browse/JCR-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836705#action_12836705
]
Jukka Zitting commented on JCR-2505:
+1 Sounds great!
> High memory usage on node with m
JsonWriter: missing handling of new JCR 2.0 property types
--
Key: JCR-2508
URL: https://issues.apache.org/jira/browse/JCR-2508
Project: Jackrabbit Content Repository
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JCR-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2508.
-
Resolution: Fixed
> JsonWriter: missing handling of new JCR 2.0 property types
> --
Reduce number of compiler warning by adding @Override and generics where
appropriate
--
Key: JCR-2509
URL: https://issues.apache.org/jira/browse/JCR-2509
Project: J
[
https://issues.apache.org/jira/browse/JCR-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela reassigned JCR-2509:
---
Assignee: angela
> Reduce number of compiler warning by adding @Override and generics where
> appropriate
>
AbstractResource: Use jcr:createdBy to expose DAV:creator-displayname
-
Key: JCR-2510
URL: https://issues.apache.org/jira/browse/JCR-2510
Project: Jackrabbit Content Repository
On 17 Feb 2010, at 15:47, Alexander Klimetschek wrote:
> Thus a broken search index must not break repository startup or it
> must be possible to delete it with a tool w/o requiring a full
> repository start.
Over in an earlier version of Sakai we have a distributed Lucene Index, where
the inde
On 18 Feb 2010, at 13:04, Stefan Guggisberg wrote:
> On Wed, Feb 17, 2010 at 5:17 PM, Jukka Zitting
> wrote:
>> Hi,
>>
>> This one's a quite frequently asked feature. Currently we store the
>> full list of child nodes in the same bundle or node state record with
>> the parent node. This makes
On 19 Feb 2010, at 15:21, Marcel Reutegger wrote:
> On Thu, Feb 18, 2010 at 13:55, Jukka Zitting wrote:
>> Agreed. Ideally (not sure if that's feasible) we'd push all caching
>> down below the unified persistence layer.
>
> IMO that's exactly where a distributed cache belongs to.
>
> the curre
On 19 Feb 2010, at 08:43, Marcel Reutegger wrote:
> think we should try to abstract from a concrete underlying
> persistence layer, like we currently do. I know this adds overhead but
> it makes it possible to have alternative back-ends. In addition, I
> think it helps us to better understand wh
Value#getBinary() and #getStream() return internal representation for type PATH
and NAME
Key: JCR-2511
URL: https://issues.apache.org/jira/browse/JCR-2511
Projec
20 matches
Mail list logo