fabrizio giustina created JCR-3520:
--
Summary: Indexing configuration dtd outdated
Key: JCR-3520
URL: https://issues.apache.org/jira/browse/JCR-3520
Project: Jackrabbit Content Repository
fabrizio giustina created JCR-3375:
--
Summary: Excerpts not available with xpath queries filtered by
path in JR 2.4
Key: JCR-3375
URL: https://issues.apache.org/jira/browse/JCR-3375
Project
[
https://issues.apache.org/jira/browse/JCR-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-3375:
---
Affects Version/s: 2.4
Excerpts not available with xpath queries filtered by path in JR
Hi,
On Thu, May 3, 2012 at 1:50 PM, Peri Subrahmanya
peri.subrahma...@gmail.com wrote:
To answer your question if you want to turn off indexing on the data you
could try something like this;
In the repository.xml add the following entry under the workspace tag you
can add the following:
-deprecated InMemPersistenceManager ?
(As long as it works, I shouldn't care much about the deprecatedness, but
it's just clogging the logs, so I'd rather be sure I can really shunt those
logs down during tests)
Cheers,
-g
On 27 Dec 2010, at 20:35, Fabrizio Giustina wrote:
Hi,
after
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2622:
---
Attachment: JCR-2622-tests_and_patch.diff
patch and updated tests agains current trunk (rev
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2622:
---
Attachment: (was: ISOLatin1AccentLowerCaseTest.java)
Configured index analizer doesn't
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12976424#action_12976424
]
fabrizio giustina commented on JCR-2622:
I tried to trace back the change that broke
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2622:
---
Affects Version/s: 2.2.0
2.1.1
2.1.2
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2622:
---
Summary: Configured index analizers not working in jackrabbit 2.1 and 2.2
(was: Configured
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2622:
---
Resolution: Not A Problem
Status: Resolved (was: Patch Available)
Index analizers
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2622:
---
Summary: Index analizers that extends StandardAnalyzer need to implement
reusableTokenStream
Hi,
after the deprecation of non-bundle persistence managers in 2.2 also
the memory-only implementation
(org.apache.jackrabbit.core.persistence.mem.InMemPersistenceManager)
has been deprecated and its usage generates leads to a few warnings in
the log.
I am currently using the in-memory pm mainly
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2622:
---
Attachment: ISOLatin1AccentLowerCaseTest.java
Configured index analizer doesn't really work
[
https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968749#action_12968749
]
fabrizio giustina commented on JCR-2622:
The attachment
[
https://issues.apache.org/jira/browse/JCR-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2732:
---
Attachment: ColonBracketSearchTest.java
ParseException in xpath query using an escaped string
[
https://issues.apache.org/jira/browse/JCR-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968752#action_12968752
]
fabrizio giustina commented on JCR-2732:
Added a unit test, it works properly in 1.x
: Jackrabbit Content Repository
Issue Type: Bug
Components: query, xpath
Affects Versions: 2.1.1, 2.1.0, 2.0.0
Reporter: fabrizio giustina
For a particular sequence of chars, :) os :(, jackrabbit 2.x seems to break
also when the xpath statement is properly
Components: query, xpath
Affects Versions: 2.1.1, 2.1.0, 1.6.2
Reporter: fabrizio giustina
Any string literal starting with OR , e.g.:
//*[jcr:contains(@title, 'OR ME')]
ends up in a javax.jcr.RepositoryException:
Exception building query
Affects Versions: 2.1.0
Reporter: fabrizio giustina
Priority: Critical
I just tried migrating an existing project which was using jackrabbit 2.0.0 to
2.1.0.
We have an index analyzer configured which filters accented chars:
{code}
public class ItalianSnowballAnalyzer
[
https://issues.apache.org/jira/browse/JCR-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2504:
---
Fix Version/s: 2.1.0
tagging with 2.1.0 as fix version, to not forget the patch for the 2.1
Hi Jukka,
On Tue, Mar 9, 2010 at 12:56 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Please use the 2.1.0 version in Jira to tag any issues you'd like to
see fixed in time for this release.
Any chance to see https://issues.apache.org/jira/browse/JCR-2504 (or
the older
[
https://issues.apache.org/jira/browse/JCR-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2504:
---
Status: Patch Available (was: Open)
see attached indexingConfiguration_classpath.diff
Allow
: Improvement
Components: indexing
Affects Versions: 2.0.0, 1.6.1
Reporter: fabrizio giustina
Attachments: indexingConfiguration_classpath.diff
The indexingConfiguration attribute in the SearchIndex configuration
(http://wiki.apache.org/jackrabbit
[
https://issues.apache.org/jira/browse/JCR-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-2504:
---
Attachment: indexingConfiguration_classpath.diff
SearchIndex patch
Allow
[
https://issues.apache.org/jira/browse/JCR-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12673676#action_12673676
]
fabrizio giustina commented on JCR-1952:
Just a question: what has been changed
[
https://issues.apache.org/jira/browse/JCR-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12673534#action_12673534
]
fabrizio giustina commented on JCR-1952:
I saw the same problem with duplicate
Issue Type: Improvement
Components: indexing
Affects Versions: 1.4
Reporter: fabrizio giustina
Priority: Minor
If I'm not wrong, there is actually no way to configure SearchIndex in order to
use a memory only lucene index.
Since you can configure
[
https://issues.apache.org/jira/browse/JCR-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12621530#action_12621530
]
fabrizio giustina commented on JCR-1694:
I wasn't aware
[
https://issues.apache.org/jira/browse/JCR-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12618259#action_12618259
]
fabrizio giustina commented on JCR-1644:
I also can confirm it definitively
[
https://issues.apache.org/jira/browse/JCR-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12617715#action_12617715
]
fabrizio giustina commented on JCR-1644:
thanks Jukka
What on earth are you doing
://issues.apache.org/jira/browse/JCR-1693
Project: Jackrabbit
Issue Type: Bug
Components: clustering
Affects Versions: core 1.4.5
Reporter: fabrizio giustina
Database journal works fine on oracle when using the OracleDatabaseJournal
implementation
[
https://issues.apache.org/jira/browse/JCR-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12617250#action_12617250
]
fabrizio giustina commented on JCR-1644:
In order to successfully import s large xml
Components: config
Affects Versions: core 1.4.5
Reporter: fabrizio giustina
Since JCR-1304 has been added to jackrabbit 1.4 I guess this should be reported
as a bug...
Still not debugged deeply, but if I try to configure a Cluster using:
Cluster id=${server} syncDelay=10
[
https://issues.apache.org/jira/browse/JCR-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-1694:
---
Attachment: JCR-1694-testcase.diff
failing testcase
System properties does not get replaced
[
https://issues.apache.org/jira/browse/JCR-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-1694:
---
Attachment: JCR-1694-fix.diff
testcase + fix for parsing system properties in cluster id
[
https://issues.apache.org/jira/browse/JCR-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12617280#action_12617280
]
fabrizio giustina commented on JCR-1694:
(if the patch looks good it would be great
[
https://issues.apache.org/jira/browse/JCR-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12605163#action_12605163
]
fabrizio giustina commented on JCR-1644:
I got the StackOverflowError too while
[
https://issues.apache.org/jira/browse/JCR-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594507#action_12594507
]
fabrizio giustina commented on JCR-1562:
I noticed that also the schema gets default
[
https://issues.apache.org/jira/browse/JCR-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-1084:
---
Attachment: JCR-1084.diff
Very simple patch against current 1.4 trunk.
This small change
: 1.4
Reporter: fabrizio giustina
Priority: Minor
When exporting to xml (system view, not tested with document view) the order of
properties is not consistent.
This is not an issue with the jcr specification, since the order of properties
is undefined, but keeping the same
[
https://issues.apache.org/jira/browse/JCR-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-788:
--
Attachment: lucene_2.2.0_patch.diff
The attached patch upgrades the lucene dependency to 2.2.0
On 3/5/07, Cédric Damioli [EMAIL PROTECTED] wrote:
When checking in a versionable Node A, with a child B
(OnParentVersion=COPY) of whatever nodetype, the corresponding
nt:frozenNode has a child node B of type nt:frozenNode and not of
its initial nodetype.
I recently noticed this too and, if I
[
https://issues.apache.org/jira/browse/JCR-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-764:
--
Attachment: textfilter_close.diff
simple patch which adds an additional cleanup on exceptions
Versions: 1.2.2
Reporter: fabrizio giustina
Priority: Trivial
Attachments: textfilter_close.diff
In case of errors in a parsed PDF document jackrabbit may fail to properly
close the parsed document. PDFBox will write a stack trace to system out at
finalize to warn
://issues.apache.org/jira/browse/JCR-765
Project: Jackrabbit
Issue Type: Improvement
Components: core
Affects Versions: 1.2.2
Reporter: fabrizio giustina
Fix For: 1.2.3
This is just a cosmetic fix: when reestablishConnection() is called
[
https://issues.apache.org/jira/browse/JCR-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-765:
--
Attachment: statementclose.diff
simple patch that simply remove the logException() at statement
: 1.2.2
Reporter: fabrizio giustina
Priority: Minor
the default datatype for:
NODE.NODE_DATA
PROP.PROP_DATA
REFS.REFS_DATA
in the mysql ddl is BLOB which is pretty small to the default size in other
dbs.
When playing with a (not very large) jackrabbit repo using mysql
On 2/16/07, Jukka Zitting [EMAIL PROTECTED] wrote:
Please vote on releasing these packages as Apache Jackrabbit 1.2.2.
a non binding +1 from a user, hoping that devs will cast their
positive vote soon ;)
cheers
fabrizio
[
http://issues.apache.org/jira/browse/JCR-332?page=comments#action_12421432 ]
fabrizio giustina commented on JCR-332:
---
Hi Jukka,
there is now a maven plugin for m1 to m2 pom conversion. Still in the sandbox,
but you might find it useful
: fabrizio giustina
Priority: Minor
berkeleydb dependency should be updated to 2.0.83, already available at
ibiblio. At this moment project.xml lists 1.7.1, which is very old.
There are no code changes required, and the PM works correctly with berkeleydb
2.0.83
dependency
release module jackrabbit-bdb 1.0
-
Key: JCR-402
URL: http://issues.apache.org/jira/browse/JCR-402
Project: Jackrabbit
Type: Wish
Components: contrib PMs
Versions: 1.0
Reporter: fabrizio giustina
The berkeydb
52 matches
Mail list logo
