You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by Apache Wiki <wi...@apache.org> on 2017/11/08 09:45:20 UTC

[Jackrabbit Wiki] Update of "Oakathon November 2017" by AndreiDulceanu

Dear Wiki user,

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

The "Oakathon November 2017" page has been changed by AndreiDulceanu:
https://wiki.apache.org/jackrabbit/Oakathon%20November%202017?action=diff&rev1=18&rev2=19

Comment:
Added myself as attender to TarMK on HDFS topic

  || Versioning and adoption || probably related to m12n, discuss how we think about Oak adoption when new feature are implemented, but upstream modules cannot take unstable versions || 2h || everyone interested || Alex ||
  || TarMK roadmap || Sketch out a roadmap for the TarMK for the upcoming months.  || 1d || Andrei, Francesco, Valentin, Michael and everyone interested || Michael ||
  || TarMK pain points || Based on the current feedback, write down the list of (major) issues encountered by users when operating a TarMK deployment. Identify the main focus areas and prioritize to help defining the roadmap. || 2-3h || Andrei, Francesco, Valentin, Michael and everyone interested || Valentin ||
- || TarMK on HDFS || Could it be possible to store segments on HDFS instead of a local disk? From a quick analysis this could be easier the intuitively perceived. HDFS scales exceptionally for parallel reads and writes of blocks. || 2-3d || Tomek, Francesco, Michael and everyone interested || PhilippSuter ||
+ || TarMK on HDFS || Could it be possible to store segments on HDFS instead of a local disk? From a quick analysis this could be easier the intuitively perceived. HDFS scales exceptionally for parallel reads and writes of blocks. || 2-3d || Tomek, Francesco, Michael, Andrei and everyone interested || PhilippSuter ||
  || No page caching for TarMK || Page caching produces notorious side effects, especially for storing very large repositories. Could it be possible to use JVM managed memory to achieve similar cache hit ratios? || 2-3d || Andrei, Valentin, Francesco, Michael and everyone interested || PhilippSuter ||
  || In or out? || Go through [[https://issues.apache.org/jira/issues/?jql=project%20%3D%20OAK%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20in%20(1.7.11%2C%201.7.12%2C%201.7.13%2C%201.7.14%2C%201.7.15%2C%201.8)|open issues]] and decide what goes into 1.8 and what needs to be deferred. Committers familiar with a module should do a first pass before the Oakathon and use the time with the team to discuss issues that are controversial, on a tight schedule or require attention for some other reason. || 2-4h || everyone || Marcel ||
  || Wrap up CompositeDataStore || I think CompositeDataStore is almost across the finish line, let's tie a bow on it || 2-4h || MattR + 1-2 committers familiar with data store || Matt Ryan ||