[bookkeeper] branch asf-site updated: Updated site at revision 0b01c12

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new cf7adf3  Updated site at revision 0b01c12
cf7adf3 is described below

commit cf7adf3353138001658891eef731c6e5ae8ee34f
Author: jenkins <bu...@apache.org>
AuthorDate: Thu May 3 20:07:04 2018 +0000

    Updated site at revision 0b01c12
---
 content/bps/BP-32-advisory-write-close/index.html | 15 ++++++++-------
 content/community/bookkeeper_proposals/index.html |  2 +-
 2 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/content/bps/BP-32-advisory-write-close/index.html b/content/bps/BP-32-advisory-write-close/index.html
index d89e21c..1efa2ac 100644
--- a/content/bps/BP-32-advisory-write-close/index.html
+++ b/content/bps/BP-32-advisory-write-close/index.html
@@ -234,7 +234,7 @@
         <section class="bk-community-content">
           <h3 id="motivation">Motivation</h3>
 
-<p>With entrylog per ledger feature (https://github.com/apache/bookkeeper/issues/570) there will be dedicated entrylog for each ledger and it provides EntryLogManagerForEntryLogPerLedger (EntryLogManager). Since there is going to be entrylog per ledger, with the current Bookie implementation there is no way for EntryLogManagerForEntryLogPerLedger (EntryLogManager) to know when the entrylog is writeclosed, so that entrylog for the active ledger can be rotated. So it would be ideal to have [...]
+<p>With <a href="https://github.com/apache/bookkeeper/issues/570">entrylog per ledger feature</a> there will be dedicated entrylog for each ledger and it provides EntryLogManagerForEntryLogPerLedger (EntryLogManager). Since there is going to be entrylog per ledger, with the current Bookie implementation there is no way for EntryLogManagerForEntryLogPerLedger (EntryLogManager) to know when the entrylog is writeclosed, so that entrylog for the active ledger can be rotated. So it would be i [...]
 
 <h3 id="proposed-changes">Proposed Changes</h3>
 
@@ -263,15 +263,16 @@
 
 <p>As explained above, this advisory write close should be transparent to Bookkeeper API user, this should be piggybagged in writehandle close call and other internal Bookie / BookieClient internal class methods (ReadEntryProcessorV3.readrequest and LedgerFragmentReplicator). But this feature introduces new protobuf message between Client and Bookie.</p>
 
-<p>message WriteCloseRequest {
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>message WriteCloseRequest {
     required int64 ledgerId = 1;
-    required bytes masterKey = 2;  <br />
-}</p>
+    required bytes masterKey = 2;    
+}
 
-<p>message WriteCloseResponse {
+message WriteCloseResponse {
     required StatusCode status = 1;
-    required int64 ledgerId = 2;<br />
-}</p>
+    required int64 ledgerId = 2;  
+}
+</code></pre></div></div>
 
 <h3 id="compatibility-deprecation-and-migration-plan">Compatibility, Deprecation, and Migration Plan</h3>
 
diff --git a/content/community/bookkeeper_proposals/index.html b/content/community/bookkeeper_proposals/index.html
index 093920a..a8da941 100644
--- a/content/community/bookkeeper_proposals/index.html
+++ b/content/community/bookkeeper_proposals/index.html
@@ -418,7 +418,7 @@ of the thread is of the format <code class="highlighter-rouge">[DISCUSS] BP-&lt;
     </tr>
     <tr>
       <td style="text-align: left"><a href="../../bps/BP-32-advisory-write-close">BP-32: Advisory (optimistic) write close</a></td>
-      <td style="text-align: left">Draft</td>
+      <td style="text-align: left">Accepted</td>
     </tr>
   </tbody>
 </table>

-- 
To stop receiving notification emails like this one, please contact
git-site-role@apache.org.