Author: thomasm Date: Fri May 17 12:31:03 2019 New Revision: 1859431 URL: http://svn.apache.org/viewvc?rev=1859431&view=rev Log: OAK-936: Site checkin for project Oak Documentation-1.14-SNAPSHOT Added: jackrabbit/site/live/oak/docs/oakathons.html Modified: jackrabbit/site/live/oak/docs/nodestore/document/mongo-document-store.html jackrabbit/site/live/oak/docs/query/query-engine.html Modified: jackrabbit/site/live/oak/docs/nodestore/document/mongo-document-store.html URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/nodestore/document/mongo-document-store.html?rev=1859431&r1=1859430&r2=1859431&view=diff ============================================================================== --- jackrabbit/site/live/oak/docs/nodestore/document/mongo-document-store.html (original) +++ jackrabbit/site/live/oak/docs/nodestore/document/mongo-document-store.html Fri May 17 12:31:03 2019 @@ -1,13 +1,13 @@ - + Jackrabbit Oak – MongoDB DocumentStore @@ -142,9 +142,9 @@
@@ -170,6 +170,7 @@
+
+ + + +
+ +
+

Oakathons

+

The Oak developers hold fairly regular Oak meetups called “Oakathons.” These community-driven meetups are open to anyone working on or with Oak to attend, either in person or remotely via videoconference.

+

Oakathons follow loose, community-driven schedules that evolve in real time to address the needs of the group.

+
+

Purpose

+

Oakathons serve three primary purposes which all hold equal importance: * To conduct a “state of the project” review, where we can discuss major Oak components and the strategic direction. * To provide time and space for free-form, synchronized discussions on issues important to key project components as well as issues impacting the whole project. * To hack on Oak itself - trying experiments, implementing new features, fixing bugs, or collaborating with others on such efforts.

+

Prior to each Oakathon we attempt to identify clear outcomes, both technical accomplishments and discussion results, that we intend to accomplish.

+
+

Cadence

+

Oakathons take place roughly once every three months - roughly every March, June, September, and December. They are generally held at the Adobe office in Basel, Switzerland unless otherwise specified. Oakathons take place over four days, Monday through Thursday, with Friday being an optional extra day.

+

Prior to the beginning of the Oakathon, the initial schedule will be announced on oak-dev@. This usually consists of just the starting time for the first day. The rest of the schedule evolves throughout the week.

+
+

Planning

+

Planning for an Oakathon is as follows: * The PMC determines a specific date for the next Oakathon. This is done usually between six and twelve weeks in advance of the selected date, to allow opportunity for remote attendees who wish to attend to obtain travel budget and make appropriate plans. * An issue is created in the Oak issue tracker to gather input and feedback on proposed discussion topics and projects. * The upcoming Oakathon is announced on the public mailing list (oak-dev@). * Proposals for discussion topics or projects for the Oakathon continue to be collected in the Oakathon issue up until the Oakathon begins - and sometimes even during the Oakathon itself.

+
+
+
+
+ + + \ No newline at end of file Modified: jackrabbit/site/live/oak/docs/query/query-engine.html URL: http://svn.apache.org/viewvc/jackrabbit/site/live/oak/docs/query/query-engine.html?rev=1859431&r1=1859430&r2=1859431&view=diff ============================================================================== --- jackrabbit/site/live/oak/docs/query/query-engine.html (original) +++ jackrabbit/site/live/oak/docs/query/query-engine.html Fri May 17 12:31:03 2019 @@ -1,13 +1,13 @@ - + Jackrabbit Oak – The Query Engine @@ -142,9 +142,9 @@
@@ -169,6 +169,7 @@
  • Document NodeStore
  • @@ -764,7 +766,36 @@ select * from [nt:base] as a where issam union select * from [nt:base] as a where issamenode(a, '/lib') -

    XPath functions “fn:string-length” and “fn:local-name”.

    +

    XPath functions “fn:string-length” and “fn:local-name”.

    +
    +

    Temporarily Blocking Queries

    + +
    +
    +
    @since 1.14.0
    +
    + +

    Application code can run bad queries that read a lot of data or consume a lot of memory. The best solution is to fix the application, however this can take some time. Queries can be blocked at runtime using validator patterns, without having to immediately change the application. Validator patterns can be set and inspected using the JMX QueryEngineSettingsMBean as follows:

    + +

    When adding a new pattern, it is recommended to first set failQuery to false to verify the pattern is correct (only a warning is logged when running matching queries). Once the pattern is correct, set failQuery to true. Validator patterns can be stored in the repository under /oak:index/queryValidator/<patternKey> (nodetype e.g. nt:unstructured) as follows:

    + +

    If the pattern is set using the multi-valued string, then the regular expression pattern is constructed from this array of texts. In this case, no escaping is needed. Example patterns are:

    + +

    Patterns are evaluated in alphabetical order. They are only read once, at startup.

    +

    See also OAK-8294