sonarcloud[bot] commented on PR #1086:
URL: https://github.com/apache/jackrabbit-oak/pull/1086#issuecomment-1798306885
SonarCloud Quality Gate failed. [
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsu
github-actions[bot] closed pull request #183: OAK-8910 - Improve OAK Lucene
Index Documentation
URL: https://github.com/apache/jackrabbit-oak/pull/183
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
github-actions[bot] commented on PR #183:
URL: https://github.com/apache/jackrabbit-oak/pull/183#issuecomment-1284813125
This PR is stale because it has been open 24 months with no activity. Remove
stale label or comment or this will be closed in 30 days.
--
This is an automated message f
tihom88 merged PR #589:
URL: https://github.com/apache/jackrabbit-oak/pull/589
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@jackrabbi
tihom88 commented on code in PR #589:
URL: https://github.com/apache/jackrabbit-oak/pull/589#discussion_r897641422
##
oak-search/src/main/java/org/apache/jackrabbit/oak/plugins/index/search/IndexDefinition.java:
##
@@ -488,6 +491,8 @@ protected IndexDefinition(NodeState root, No
fabriziofortino commented on code in PR #589:
URL: https://github.com/apache/jackrabbit-oak/pull/589#discussion_r893311381
##
oak-lucene/src/test/java/org/apache/jackrabbit/oak/plugins/index/lucene/LucenePropertyIndexTest.java:
##
@@ -3032,6 +3089,50 @@ public void testRepSimila
thomasmueller merged pull request #318:
URL: https://github.com/apache/jackrabbit-oak/pull/318
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev
thomasmueller opened a new pull request #318:
URL: https://github.com/apache/jackrabbit-oak/pull/318
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mai
tihom88 merged pull request #298:
URL: https://github.com/apache/jackrabbit-oak/pull/298
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, p
tihom88 opened a new pull request #298:
URL: https://github.com/apache/jackrabbit-oak/pull/298
…minimal
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about t
Hi ,
I am trying to query with Lucene index but getting the empty result and
below errors in the log,
Traversal query (query without index): select [jcr:path] from [nt:base]
where isdescendantnode('/test') and name='World'; consider creating an index
[async] The
On Sun, Aug 16, 2015 at 9:48 PM, Clay Ferguson wrote:
> Fellow Jackrabbits:
>
> Encountered the unrecoverable Lucene error again yesterday:
>
> Could not access the Lucene index at /oak:index/lastModifiedIndex
> java.io.FileNotFoundException: _g.si
>
> The next time it happe
[
https://issues.apache.org/jira/browse/JCR-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella closed JCR-3798.
-
Bulk close for 2.8.1
> NPE while building path in lucene index consistency chec
[
https://issues.apache.org/jira/browse/JCR-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Unico Hommes resolved JCR-3798.
---
Resolution: Fixed
> NPE while building path in lucene index consistency chec
[
https://issues.apache.org/jira/browse/JCR-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Unico Hommes updated JCR-3798:
--
Fix Version/s: 3.0
2.8.1
2.6.6
> NPE while building path in luc
Unico Hommes created JCR-3798:
-
Summary: NPE while building path in lucene index consistency
checker
Key: JCR-3798
URL: https://issues.apache.org/jira/browse/JCR-3798
Project: Jackrabbit Content
[
https://issues.apache.org/jira/browse/JCR-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3506:
---
Fix Version/s: (was: 2.6)
> Add ability to check lucene index for missing no
[
https://issues.apache.org/jira/browse/JCR-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3506:
---
Fix Version/s: (was: 2.7)
2.6
> Add ability to check lucene index
[
https://issues.apache.org/jira/browse/JCR-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Unico Hommes resolved JCR-3506.
---
Resolution: Fixed
> Add ability to check lucene index for missing no
[
https://issues.apache.org/jira/browse/JCR-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Unico Hommes updated JCR-3506:
--
Fix Version/s: 2.6
> Add ability to check lucene index for missing no
3878.
> Add ability to check lucene index for missing nodes
> ---
>
> Key: JCR-3506
> URL: https://issues.apache.org/jira/browse/JCR-3506
> Project: Jackrabbit Content Repository
[
https://issues.apache.org/jira/browse/JCR-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Unico Hommes updated JCR-3506:
--
Component/s: jackrabbit-core
indexing
> Add ability to check lucene index
Unico Hommes created JCR-3506:
-
Summary: Add ability to check lucene index for missing nodes
Key: JCR-3506
URL: https://issues.apache.org/jira/browse/JCR-3506
Project: Jackrabbit Content Repository
Hi,
We have a fairly large CQ 5.2.1 repository (~4m digital image assets, ~10m
BLOBs) which crashed, resulting in index corruption. We removed the index
and are now rebuilding it. The process is going rather slowly; at current
rate of progress it will take 5 days, which we cannot afford.
Analys
DirectoryManager implementations.
svn revision: 718218
> org.apache.jackrabbit.core.query.lucene.SearchIndex with in-memory lucene
> index
> ---
>
> Key: JCR-1747
> URL: https:/
directories that are not index segments.
> org.apache.jackrabbit.core.query.lucene.SearchIndex with in-memory lucene
> index
> ---
>
> Key: JCR-1747
> URL: https://issues.apache.o
two
implementations currently:
- FSDirectoryManager, this is the default, which matches the current behaviour
- RAMDirectoryManager, this one allows you to have an index that is completely
held in memory
> org.apache.jackrabbit.core.query.lucene.SearchIndex with in-memory lucene
>
org.apache.jackrabbit.core.query.lucene.SearchIndex with in-memory lucene index
---
Key: JCR-1747
URL: https://issues.apache.org/jira/browse/JCR-1747
Project: Jackrabbit
roperties you see in the lucene document are all reference
> properties. Those must also be *stored* in the index to resolve them in a
> jcr:deref() statement.
>
>> We've noticed that for large result sets (1000+ nodes), the performance
>> can
>> drag because
e can
drag because each Node lookup requires at least one database query. Since
we are only interested in data contained in the Lucene index, it would be
nice if we would get that data from the index and not have to go through the
Jackrabbit PM at all.
this is because the index does not store the prop
at some point?
We've noticed that for large result sets (1000+ nodes), the performance can
drag because each Node lookup requires at least one database query. Since
we are only interested in data contained in the Lucene index, it would be
nice if we would get that data from the index and not h
43 matches
Mail list logo
