jackrabbit

Checkout Tools
  • last updated 7 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates

Changeset 1854055 is being indexed.

OAK-8072 - aggregate jcr:content search results as their parents
OAK-8054 RepMembersConflictHandler creates property with wrong type

- backport

OAK-8068: Update slf4j dependency to 1.7.26
OAK-8070: The date-based copy-versions directive doesn't work correctly with include-paths
OAK-8070: The date-based copy-versions directive doesn't work correctly with include-paths
OAK-8070: The date-based copy-versions directive doesn't work correctly with include-paths
OAK-8070: The date-based copy-versions directive doesn't work correctly with include-paths
OAK-8023 : AccessControlManagerImpl can not handle repository level when editing policies by principal (merge r1853441 into 1.10 branch)
OAK-8052: PersistentCache: failure during construction may lead to resource leak
JCR-4416: Update slf4j dependency to 1.7.26
OAK-8065 : AbstractSecurityTest.getAccessControlManager: should use getNamePathMapper() instead of DEFAULT
OAK-8046: Result items are not always correctly counted against the configured read limit if a query uses a lucene index (backported r1853969, r1853997 from trunk)

1. Initial implementation

2. Fix test cases. I had earlier assumed that index tag chooses even

aggregate index (compatVersion=1) but it doesn't. So, now we have

different type of indexes and query according to which one we want to

get picked.

OAK-8046: Result items are not always correctly counted against the configured read limit if a query uses a lucene index (backported r1853997 from trunk)

Fix test cases. I had earlier assumed that index tag chooses even

aggregate index (compatVersion=1) but it doesn't. So, now we have

different type of indexes and query according to which one we want to

get picked.

OAK-8046: Result items are not always correctly counted against the configured read limit if a query uses a lucene index

Fix test cases. I had earlier assumed that index tag chooses even

aggregate index (compatVersion=1) but it doesn't. So, now we have

different type of indexes and query according to which one we want to

get picked.

OAK-8046: Result items are not always correctly counted against the configured read limit if a query uses a lucene index (backport r1853969 from trunk)

OAK-8046: Result items are not always correctly counted against the configured read limit if a query uses a lucene index
OAK-8058: RDB*Store: update Tomcat JDBC pool dependency to 8.5.38 (ported to 1.8)
OAK-8058: RDB*Store: update Tomcat JDBC pool dependency to 8.5.38 (ported to 1.10)
OAK-8059: Update Jackson dependency to 2.9.8 (ported to 1.10)
JCR-4415: Update Jetty dependency to 9.2.26.v20180806
OAK-7960: RDB: add to Oak documentationRDB: add to Oak documentation (ported to 1.8)
    • ?
    /oak/branches/1.8/oak-doc/src/site/site.xml
OAK-7960: RDB: add to Oak documentationRDB: add to Oak documentation (ported to 1.10)
    • ?
    /oak/branches/1.10/oak-doc/src/site/site.xml
OAK-7960: RDB: add to Oak documentation - link to oak-run rdbddldump description
site checkin
OAK-8043: RDB: expose DDL generation functionality in oak-run - update oak-doc
OAK-8035: a message is logged when similar costs come from the same index type

test cleanup, use LogCustomizer, remove assertj dependency

OAK-8059: Update Jackson dependency to 2.9.8
OAK-8054 RepMembersConflictHandler creates property with wrong type

OAK-8058: RDB*Store: update Tomcat JDBC pool dependency to 8.5.38
OAK-8060: Incorrect read preference when parentId refers to NodeDocument.NULL