jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "Oakathon August 2017" by ThomasMueller
Date Fri, 18 Aug 2017 13:38:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "Oakathon August 2017" page has been changed by ThomasMueller:
https://wiki.apache.org/jackrabbit/Oakathon%20August%202017?action=diff&rev1=30&rev2=31

  ||Example||Describe what the topic is about. Is is mainly a discussion, implementing a feature,
or a POC? Add links to further information and details.||The expected effort. 2h, 1d, full
week, etc.||Add names of participants.||
  ||Key Signing Party||To update the [[https://www.apache.org/dev/release-signing.html#key-signing-party|Oak
team's WOT]].  ||1h||Open to anyone.||
  ||Update OSGi Annotations in Oak||Proposal to update the OSGi annotation to latest standard
[[https://blog.osoco.de/2016/05/migrating-from-the-apache-felix-scr-annotations-to-the-osgi-declarative-services-annotations/|as
described here]]. Mostly removal or ''org.apache.felix.scr.annotations'', others can be tackled
if found.  ||1 day||AlexD, Robert||
- ||Workload-aware Property Index ||The workload-aware index aims to improve update performance
and reduce the number of index conflicts. Discussion of an implementation in Oak. ||2h||Kevin
Wellenzohn||
+ ||Workload-aware Property Index ||The workload-aware index aims to improve update performance
and reduce the number of index conflicts. Discussion of an implementation in Oak. ||2h||Kevin
Wellenzohn, Thomas Mueller (tentative)||
- ||[[Synchronous Lucene Property Indexes|Hybrid Index v2|]] ||Next phase of hybrid index
to enable support for unique index and sync indexes ||2 d||Chetan Mehrotra||
+ ||[[Synchronous Lucene Property Indexes|Hybrid Index v2|]] ||Next phase of hybrid index
to enable support for unique index and sync indexes ||2 d||Chetan Mehrotra, Thomas Mueller
(tentative)||
- ||[[Journal based Async Indexer|Journal basedAsync Indexer|]] || New scalable design for
async indexer ||2 d||Chetan Mehrotra||
+ ||[[Journal based Async Indexer|Journal basedAsync Indexer|]] || New scalable design for
async indexer ||2 d||Chetan Mehrotra, Thomas Mueller (tentative)||
  ||Finalize and review composite node store||Make sure the current version is ready for production||2d||Robert
Munteanu, Tomek Rekawek||
- ||Implement metrics||Implement Metrics across Oak and prototype RRDTool persistence||3d||Marcel||
+ ||Implement metrics||Implement Metrics across Oak and prototype RRDTool persistence||3d||Marcel,
Thomas Mueller (tentative)||
- ||Modularization||Anythign left to be done here? Robert: Split out oak-core more possibly
- document-based storage is a candidate||3d||Robert (if composite and OSGi annotations are
done in time), Marcel||
+ ||Modularization||Anythign left to be done here? Robert: Split out oak-core more possibly
- document-based storage is a candidate||3d||Robert (if composite and OSGi annotations are
done in time), Marcel, Thomas Mueller (tentative)||
  ||Manage Jenkins configurations in SVN||Stop relying on the Jenkins UI for configuration,
but instead use a Jenkinsfile or the DSL Job plugin||0.5d ||Robert ||
  ||Segment store analyser|| Implement a tool to analyse the content of a segment store ||2-5d
|| Michael ||
  ||Provide JCR node info to blob store||Prototype a way to provide JCR node information -
path, node type, properties and property values - to blob store, for [[Composite Blob Store]]||2
d||Matt Ryan||
  ||Unmanaged binary support||Deliver a prototype demo of at least one unmanaged binary support
use case (see [[JCR Binary Usecase]] UC1, UC5, UC6, UC13).  UC13 is proposed but could be
another.||5 d||Matt Ryan||
- ||Cache pre-filling with ML||Work out a way to: (1) gather data about sequences of nodes
read from the DocumentStore, (2) use this data to predict what nodes will be requested soon||5d||Tomek
Rekawek||
+ ||Cache pre-filling with ML||Work out a way to: (1) gather data about sequences of nodes
read from the DocumentStore, (2) use this data to predict what nodes will be requested soon||5d||Tomek
Rekawek, Thomas Mueller (tentative)||
  
  = Agenda Proposal =
  

Mime
View raw message