is
org.apache.jackrabbit.core.persistence.AutoFixCorruptNode.testAutoFixWithConsistencyCheck.
Oh, indeed! My mistake.
However, the ConcurrentImportTest does currently fail in my
environment, so I wonder if this is relate to JCR-3277 or something
different, perhaps triggered by some change in my enviroment.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3493.
Resolution: Fixed
Fix Version/s: (was: 2.7)
I committed the patch (with extra
[
https://issues.apache.org/jira/browse/JCR-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3502:
---
Fix Version/s: (was: 2.7)
Deleted states are not merged correctly
[
https://issues.apache.org/jira/browse/JCR-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3501:
---
Fix Version/s: (was: 2.7)
When cancelling an update modcount of modified states must be reset
Hi,
On Fri, Jan 25, 2013 at 12:32 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
No problem. There seems to still be some related issue when running
the build with -PintegrationTesting. See the last CI build failure.
I fixed that one in revision 1439797.
BR,
Jukka Zitting
, so the
size increase is just temporary.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3497:
---
Fix Version/s: (was: 2.7)
2.6
Affects Version/s: (was: 2.7
[
https://issues.apache.org/jira/browse/JCR-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3499:
---
Fix Version/s: (was: 2.7)
2.6
Affects Version/s: 2.5.3
Merged
[
https://issues.apache.org/jira/browse/JCR-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565775#comment-13565775
]
Jukka Zitting commented on JCR-1873:
Merged to the 2.6 branch in revision 1440103
[
https://issues.apache.org/jira/browse/JCR-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3500.
Resolution: Fixed
Done in revision 1438541, and merged to the 2.6 branch in revision 1440104
[
https://issues.apache.org/jira/browse/JCR-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565780#comment-13565780
]
Jukka Zitting commented on JCR-3503:
Merged to the 2.6 branch in revision 1440106
[
https://issues.apache.org/jira/browse/JCR-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3498:
---
Fix Version/s: (was: 2.6)
OUTER JOIN behavior is improperly excluding some values
clients no
longer refer to the smaller segments) take care of disposing the small
segments that are no longer needed.
BR,
Jukka Zitting
small segments from time to time.
Indeed, see my response to Marcel's post.
BR,
Jukka Zitting
.
About atomic updates: I thought segments are immutable?
We need atomic updates of the journal documents. They are mutable.
BR,
Jukka Zitting
hidden classes for otherwise
untyped objects.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3493:
---
Fix Version/s: (was: 2.5.3)
OUTER JOIN tests expect incorrect results
Jukka Zitting created JCRSITE-39:
Summary: Adjust release check script to use dist.apache.org
Key: JCRSITE-39
URL: https://issues.apache.org/jira/browse/JCRSITE-39
Project: Jackrabbit Site
Hi,
On Mon, Jan 28, 2013 at 1:37 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Jan 28, 2013 11:37:29 AM
hudson.remoting.SynchronousCommandTransport$ReaderThread run
SEVERE: I/O error in channel channel
java.io.StreamCorruptedException
Looks like a Jenkins problem.
BR,
Jukka
[
https://issues.apache.org/jira/browse/JCRSITE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCRSITE-39.
--
Resolution: Fixed
An updated release checker now live in
https://dist.apache.org/repos/dist
Hi,
On Wed, Jan 23, 2013 at 12:43 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Please vote on releasing this package as Apache Jackrabbit 2.5.3.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
The vote passes as follows
Hi,
On Fri, Jan 25, 2013 at 12:30 PM, KÖLL Claus c.ko...@tirol.gv.at wrote:
Thanks you jukka for fixing !
No problem. There seems to still be some related issue when running
the build with -PintegrationTesting. See the last CI build failure.
BR,
Jukka Zitting
, with a default implementation like:
public WebdavRequestImpl(HttpServletRequest httpRequest,
DavLocatorFactory factory) {
this(httpRequest, factory, true);
}
BR,
Jukka Zitting
Jukka Zitting created JCR-3500:
--
Summary: Upgrade to Tika 1.3
Key: JCR-3500
URL: https://issues.apache.org/jira/browse/JCR-3500
Project: Jackrabbit Content Repository
Issue Type: Improvement
not release this package because...
My vote is +1.
BR,
Jukka Zitting
Hi,
BTW, when building the 0.6 release candidate, you need to also have
the Jackrabbit 2.5.3 release candidate locally installed.
BR,
Jukka Zitting
that either the Jackrabbit CI build didn't yet deploy fresh
snapshots, or the Oak build still had older Jackrabbit snapshots
cached locally. The issue should resolve itself soon.
BR,
Jukka Zitting
to use query? I would
assume that it would be both easier (i.e. less code) and more
efficient to simply read the relevant ACLs directly from the content
tree being accessed.
BR,
Jukka Zitting
to assume that the per-principal policy getters in
JackrabbitAccessControlManager referred only to global access policies
not tied to specific nodes or subtrees, and that the path-based
getters in AccessControlManager would return policies tied to the
given path. Looks like I was mistaken.
BR,
Jukka
[
https://issues.apache.org/jira/browse/JCR-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3305:
---
Fix Version/s: 2.5.3
spi2davex.RepositoryServiceImpl - idUriCache raises until heap overflow
[
https://issues.apache.org/jira/browse/JCR-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3455:
---
Component/s: jackrabbit-core
Fix Version/s: 2.5.3
Looks like this was fixed in revision 1405792
because...
My vote is +1.
PS. Note the new dist.apache.org location for the release candidate
and the updated check-release.sh script (remember to svn update before
running the above command).
BR,
Jukka Zitting
be backported to
the 2.6 branch.
BR,
Jukka Zitting
?
BR,
Jukka Zitting
. Does that help?
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3486:
---
Fix Version/s: (was: 2.6)
2.5.3
Potential null pointer exception
[
https://issues.apache.org/jira/browse/JCR-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3483:
---
Fix Version/s: (was: 2.6)
2.5.3
Result set iterator causes infinite loop
[
https://issues.apache.org/jira/browse/JCR-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3478:
---
Fix Version/s: (was: 2.6)
2.5.3
Partial search terms matching fails when
[
https://issues.apache.org/jira/browse/JCR-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3476:
---
Fix Version/s: (was: 2.6)
2.5.3
NodeIndexer attempts to extract binary
[
https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3469:
---
Fix Version/s: (was: 2.6)
2.5.3
Thread interrupt may result in closed
[
https://issues.apache.org/jira/browse/JCR-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3435:
---
Fix Version/s: (was: 2.6)
2.5.3
NPE on parsing XPath query with child axis
[
https://issues.apache.org/jira/browse/JCR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3439:
---
Fix Version/s: (was: 2.6)
2.5.3
PrincipalManagerImpl.CheckedGroup should
[
https://issues.apache.org/jira/browse/JCR-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3435:
---
Resolution: Fixed
Fix Version/s: (was: 2.4.4)
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/JCR-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3443:
---
Assignee: Jukka Zitting
Issue Type: New Feature (was: Improvement)
Normalize String
[
https://issues.apache.org/jira/browse/JCR-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3443:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Looks useful, thanks! Patch
[
https://issues.apache.org/jira/browse/JCR-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3485:
---
Resolution: Fixed
Assignee: Jukka Zitting
Status: Resolved (was: Patch Available)
Patch
[
https://issues.apache.org/jira/browse/JCR-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3402:
---
Fix Version/s: (was: 2.5.3)
I'm hesitant to apply the patch as is for the following two reasons
[
https://issues.apache.org/jira/browse/JCR-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3489:
---
Fix Version/s: (was: 2.5.3)
Let's postpone this to see if some of the feedback could be addressed
[
https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3440.
Resolution: Fixed
Re-resolving this as the patch already got applied.
Please see the backwards
[
https://issues.apache.org/jira/browse/JCR-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559671#comment-13559671
]
Jukka Zitting commented on JCR-3402:
The problem is the + invalid part. By definition
[
https://issues.apache.org/jira/browse/JCR-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559690#comment-13559690
]
Jukka Zitting commented on JCR-3402:
Nice! Looks good to me.
Marcel, Alex, others; any
there are still some bugs in the garbage collector.
BR,
Jukka Zitting
Jukka Zitting created JCR-3494:
--
Summary: Make Jackrabbit performance benchmark easier to use from
Oak
Key: JCR-3494
URL: https://issues.apache.org/jira/browse/JCR-3494
Project: Jackrabbit Content
Hi,
On Tue, Oct 23, 2012 at 5:03 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Here's an early draft of how this could work out in terms of the
Jackrabbit roadmap:
Seems like we have fairly good consensus on the big picture, so let's
start laying some more concrete plans!
* Jackrabbit 2.6
Hi,
On Thu, Jan 17, 2013 at 1:00 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
On Tue, Oct 23, 2012 at 5:03 PM, Jukka Zitting jukka.zitt...@gmail.com
wrote:
* Jackrabbit 2.6: We target at releasing a stable Jackrabbit 2.6.0
version sometime around the end of this year. As usual, we'll
towards Jackrabbit 3.0
by starting to include Oak in the Jackrabbit deployment packages
(-webapp, -standalone, etc.) and by preparing initial
upgrade/migration tools. I'll follow up with more details on that
after the release.
BR,
Jukka Zitting
clients could write directly to that master, while others that don't
require such guarantees could gain extra write concurrency by
committing their changes to other cluster nodes with lower authority.
BR,
Jukka Zitting
in different cases.
BR,
Jukka Zitting
Hi,
On Wed, Jan 16, 2013 at 11:04 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
If yes, please revert, as these methods were intentionally added to
satisfy the need for different exceptions in different cases.
Hmm, on second thought that's a bit harsh and not too constructive,
sorry. Let me
problem. Let's hope it resolves itself shortly.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552557#comment-13552557
]
Jukka Zitting commented on JCR-3491:
This might have broken the CI build, see
https
Hi,
On Mon, Jan 7, 2013 at 3:06 PM, Jukka Zitting jukka.zitt...@gmail.comwrote:
I assume the problem only occurs when you run mvn eclipse:eclipse, not
on a normal build?
As of revision 1431306 also mvn eclipse:eclipse should work. I simplified
the build setup a bit to avoid the troublesome
] https://svn.apache.org/viewvc?view=revisionrevision=1411247
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13537211#comment-13537211
]
Jukka Zitting commented on JCR-3489:
There's little downside to adding something like
for merging.
Alternatively, as discussed separately, we may need to switch the
Lucene indexer from a CommitHook to an Observer (with some cluster
synchronization mechanism) so it can better run things in background.
BR,
Jukka Zitting
Hi,
On Mon, Dec 17, 2012 at 12:09 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
As documented in [1], we should migrate our release publishing
mechanism from people.apache.org to the new svnpubsub-based
dist.apache.org mechanism [2]. Since we currently have no releases
being prepared
component under .../jackrabbit/trunk.
BR,
Jukka Zitting
=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12895234
BR,
Jukka Zitting
with OSGi. I replaced the exception with
UnsupportedOperationException.
BR,
Jukka Zitting
Hi,
On Mon, Dec 10, 2012 at 12:43 PM, Alexander Klimetschek
aklim...@adobe.com wrote:
is anything planned for this already? Or did we already move, and
jackrabbit.apache.org is incorrectly listed below?
It's still on the TODO, see latest board report.
BR,
Jukka Zitting
by disabling the auto-versioning CommitHook.
BR,
Jukka Zitting
,
Jukka Zitting
for details
I updated the sql2_explain.txt file to match test output in revision 1417419.
BR,
Jukka Zitting
this
simplifies the process of mounting the version store into the workspace.
I see the point, but I don't think you can make the version store
read-only with this approach. How for example would you trigger
operations like VersionHistory.addVersionLabel() or
VersionHistory.removeVersion()?
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13508601#comment-13508601
]
Jukka Zitting commented on JCR-3474:
I replaced the isJackrabbitImpl flag
below for the full InterruptedQueryTest failure. The test case was
added in revision 1415093 for JCR-3469, and has failed in all Jenkins
builds since then.
BR,
Jukka Zitting
junit.framework.AssertionFailedError: javax.jcr.RepositoryException:
java.io.IOException: null:
SimpleFSIndexInput(path
Jukka Zitting created JCR-3474:
--
Summary: Add JackrabbitQueryResult.getTotalSize()
Key: JCR-3474
URL: https://issues.apache.org/jira/browse/JCR-3474
Project: Jackrabbit Content Repository
Issue
[
https://issues.apache.org/jira/browse/JCR-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3474.
Resolution: Fixed
Fix Version/s: 2.5.3
Done in revision 1415968.
Add
accidentally mess
up with transitive dependencies of downstream projects. A downstream
project that embeds Jackrabbit but still wants the Tika update can
still do so locally by explicitly upgrading the version of the Tika
dependency.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505811#comment-13505811
]
Jukka Zitting commented on JCR-3465:
The current implementation works just as documented
to use workarounds like the extra jcr:primaryType setting in
the index nodes.
BR,
Jukka Zitting
Hi,
On Tue, Nov 27, 2012 at 12:56 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
I did some work along these lines already earlier with the
CopyAndMoveAwareJsopDiff class you can find inside KernelRootBuilder,
but couldn't make it work properly. Based on discussions with Michael
last week I
avoid with OAK-468). If we can keep that goal up, and
further optimize JSON processing at the MK level, it should be
possible also for an Oak stack to work as outlined in the Kafka
document.
BR,
Jukka Zitting
Hi,
On Fri, Nov 23, 2012 at 4:21 PM, Stefan Guggisberg
stefan.guggisb...@gmail.com wrote:
On Thu, Nov 22, 2012 at 4:56 PM, Jukka Zitting jukka.zitt...@gmail.com
wrote:
See the attachment in https://issues.apache.org/jira/browse/OAK-468
i committed the API changes, MicroKernelImpl support
Hi,
On Wed, Nov 21, 2012 at 11:00 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
On Tue, Nov 20, 2012 at 8:01 PM, Stefan Guggisberg
stefan.guggisb...@gmail.com wrote:
- do you have a proposal for the suggested MicroKernel API (java doc)
changes?
I'll have one to share shortly...
See
CMS as support for the current
Confluence export + svn checkout mechanism is going to be discontinued
at the end of the year. The good part about migrating is that site
changes will then be reflected on the public web site in just a few
seconds instead of the hours of delay we now have.
BR,
Jukka
this:
getNodes(/) = { a: { :id: :id:x } }
getNodes(:id:x) = { b: { :id: :id:y } }
getNodes(:id:y) = { c: { :id: :id:z} }
getNodes(:id:z) = {}
- do you have a proposal for the suggested MicroKernel API (java doc)
changes?
I'll have one to share shortly...
BR,
Jukka Zitting
by a bug in the Pax Exam
tool we're using for the OSGi integration tests:
testMicroKernel:OSGiIT.testMicroKernel:NativeContainer:
org.apache.felix.framework.FrameworkFactory@2d04faf8(org.apache.jackrabbit.oak.osgi.OSGiIT):
this instance has already been disposed
BR,
Jukka Zitting
build also runs the MongoMK tests.)
BR,
Jukka Zitting
Hi,
On Tue, Nov 20, 2012 at 2:02 PM, build...@apache.org wrote:
BUILD FAILED: failed compile
Oops, sorry about that. I'm on it.
BR,
Jukka Zitting
the update limit high enough so that the
functionality is only triggered in custom test cases and in normal use
the much lower purge limit in RootImpl takes care of branch handling.
BR,
Jukka Zitting
instance being available to be automatically
skipped (instead of failing the build) when such an instance is not
found.
See below for relevant details I added to the README.
BR,
Jukka Zitting
MongoDB integration
---
Parts of the Oak build expects a MongoDB instance
for hash maps and where one doesnt have an
application
server to cache the node instances in memory across requests.
That sounds more like a performance issue to be addressed in the
language binding or the remoting implementation rather than a
conceptual API design issue.
BR,
Jukka Zitting
.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13492467#comment-13492467
]
Jukka Zitting commented on JCR-3440:
For 2.4 and 2.2 it would be nice to find
out of extra space.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3258.
Resolution: Not A Problem
Jackrabbit is designed to work directly as an XA resource, which means
[
https://issues.apache.org/jira/browse/JCR-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491266#comment-13491266
]
Jukka Zitting commented on JCR-3258:
We need autocommit since Jackrabbit is using long
of code crying out in terror and being suddenly
removed. It'll be like something terrible happening. ;-)
BR,
Jukka Zitting
Jackrabbit
3.x releases. And since Jackrabbit 3.0 will be based on a fresh new
underlying architecture from Oak, it's likely that we'll encounter a
number of smaller issues to be fixed or improved.
WDYT?
[1] http://markmail.org/message/ga4mn2x2xqsvzwg6
BR,
Jukka Zitting
701 - 800 of 6233 matches
Mail list logo
