Slack Channel

[Sijie Guo]

Hi all,

The slack channel https://apachebookkeeper.slack.com is live now. If you
have emails (@apache.org), you can signup with
https://apachebookkeeper.slack.com/signup.

If you don't have apache emails, you can auto-invite yourself in
https://apachebookkeeper.herokuapp.com/

If you were already in apache distributedlog slack before, you don't need
to sign up this time.

Let me know if you have any questions.

- Sijie

Re: [VOTE] Slack Channel for BookKeeper

[Sijie Guo]

Closed the vote. 4 binding +1 votes, 5 non-binding +1 votes. The vote is
passed. I will proceed with the next steps to hand over the channel to BK
PMC.


Binding votes:

- Ivan Kelly
- JV
- Matteo Merli
- Sijie Guo

Non binding votes:

- atracymartin
- Enrico Olivelli
- Francesco Caliumi
- Jia Zhai
- Leigh Stewart


On Thu, Jul 27, 2017 at 11:02 AM, Sijie Guo <guosi...@gmail.com> wrote:

> Start a vote thread for transferring the DL slack channel to BK.
>
> The propose is:
>
> - transfer the dl slack channel apachedistributedlog.slack.com to
> apachebookkeeper.slack.com
> - the owner will be BookKeeper PMC (priv...@bookkeeper.apache.org)
>
> One note:
>
> - the slack channel is for informal/immediate discussion. no decisions are
> made in slack channel. decision related discussions should be recorded in
> ASF (either mailing list, JIR or wiki)
>
> Please vote +1, 0, -1. The vote will be open for 72 hours.
>
> - Sijie
>
>
>

Re: [VOTE] Slack Channel for BookKeeper

[Sijie Guo]

On Fri, Jul 28, 2017 at 8:21 AM, Venkateswara Rao Jujjuri <jujj...@gmail.com
> wrote:

> +1
> Just curious on why decided to transfer rather than create a new one.
> Fine either way.
>

This came out when we transfers the DL project to BK PMC. The slack team
has to be transferred to BK PMC anyway. so an easy operation is just
transfer it as BK slack team.

- Sijie

>
> On Fri, Jul 28, 2017 at 12:22 AM, Francesco Caliumi - Diennea <
> francesco.cali...@diennea.com> wrote:
>
> > +1 non binding
> >
> > On Thu, 2017-07-27 at 21:45 +0200, Ivan Kelly wrote:
> >
> > +1
> >
> > On Thu, Jul 27, 2017 at 8:10 PM, Matteo Merli <matteo.me...@gmail.com<
> > mailto:matteo.me...@gmail.com>> wrote:
> >
> >
> > +1
> >
> > --
> > Matteo Merli
> > <matteo.me...@gmail.com<mailto:matteo.me...@gmail.com>>
> >
> > On Thu, Jul 27, 2017 at 11:06 AM, Enrico Olivelli <eolive...@gmail.com
> > <mailto:eolive...@gmail.com>>
> > wrote:
> >
> >
> >
> > +1 non binding
> >
> > Enrico
> >
> > Il gio 27 lug 2017, 20:02 Sijie Guo <guosi...@gmail.com<mailto:guo
> > si...@gmail.com>> ha scritto:
> >
> >
> >
> > Start a vote thread for transferring the DL slack channel to BK.
> >
> > The propose is:
> >
> > - transfer the dl slack channel apachedistributedlog.slack.com to
> > apachebookkeeper.slack.com
> > - the owner will be BookKeeper PMC (priv...@bookkeeper.apache.org
>  > priv...@bookkeeper.apache.org>)
> >
> > One note:
> >
> > - the slack channel is for informal/immediate discussion. no decisions
> >
> >
> > are
> >
> >
> > made in slack channel. decision related discussions should be recorded in
> > ASF (either mailing list, JIR or wiki)
> >
> > Please vote +1, 0, -1. The vote will be open for 72 hours.
> >
> > - Sijie
> >
> >
> >
> > --
> >
> >
> > -- Enrico Olivelli
> >
> >
> >
> > --
> >
> > Francesco Caliumi
> > Developer @ Diennea - MagNews
> > Tel.: (+39) 0546 066100 - Int. 266
> > Viale G.Marconi 30/14 - 48018 Faenza (RA)
> >
> > [Magnews.it]<http://www.magnews.it/it>
> >
> > [Linkedin]<http://www.linkedin.com/company/diennea---magnews>
> >  [Twitter] <http://twitter.com/DienneaMagNews>  [Facebook] <
> > http://www.facebook.com/pages/MagNews/197617841797>  [Newsletter] <
> > http://www.magnews.it/it/iscriviti-alla-newsletter>
> >
> > 
> >
> > Iscriviti alla nostra newsletter per rimanere aggiornato su digital ed
> > email marketing! http://www.magnews.it/newsletter/
> >
> > The information in this email is confidential and may be legally
> > privileged. If you are not the intended recipient please notify the
> sender
> > immediately and destroy this email. Any unauthorized, direct or indirect,
> > disclosure, copying, storage, distribution or other use is strictly
> > forbidden.
> >
>
>
>
> --
> Jvrao
> ---
> First they ignore you, then they laugh at you, then they fight you, then
> you win. - Mahatma Gandhi
>

[VOTE] Slack Channel for BookKeeper

[Sijie Guo]

Start a vote thread for transferring the DL slack channel to BK.

The propose is:

- transfer the dl slack channel apachedistributedlog.slack.com to
apachebookkeeper.slack.com
- the owner will be BookKeeper PMC (priv...@bookkeeper.apache.org)

One note:

- the slack channel is for informal/immediate discussion. no decisions are
made in slack channel. decision related discussions should be recorded in
ASF (either mailing list, JIR or wiki)

Please vote +1, 0, -1. The vote will be open for 72 hours.

- Sijie

Re: [DISCUSS] Slack Channel for BookKeeper

[Sijie Guo]

As we discussed in today's community meeting
<https://cwiki.apache.org/confluence/display/BOOKKEEPER/2017-07-27+Meeting+Notes>,
I will start a vote thread for that.

- Sijie

On Mon, Jul 24, 2017 at 5:11 PM, Sijie Guo <guosi...@gmail.com> wrote:

> Hi all,
>
> What do you guys all think about having a dedicated slack channel for
> informal discussion for the community? There are a handful of Apache
> projects are doing that already, there are also ways to have a bot that
> sends daily digest of the conversation to the mailing lists (to keep the
> records in ASF infrastructure).
>
> As the followup steps for merging DL into BookKeeper, we are transferring
> the DL slack channel to BookKeeper PMC. We can just make it a BK slack
> channel, and have different channels under it for different discussions.
>
> Thoughts?
>
> - Sijie
>

Re: [Discuss] Release DL 0.5.0

[Sijie Guo]

Thank you, Jia.

There is a release guid in the website (
https://github.com/apache/incubator-distributedlog/blob/master/website/community/release_guide.md).
It should be easy and straightforward to follow. I can work together with
you on the 0.5.0 release.

However I think INFRA has not completed moving DL from incubator, so you
probably are not able to really proceed the release until INFRA completes
its tasks. But you can start follow the release guide and drive the 0.5.0
release.

Let me know if you have any questions.

- Sijie

On Wed, Jul 26, 2017 at 6:10 PM, Jia Zhai <zhaiji...@gmail.com> wrote:

> Hi sijie,
> I am inserested to be the release manager for 0.5.0, but there will be some
> instruction and help needed from you guys. :)
>
> Thanks.
> -Jia
>
> On Thu, Jul 27, 2017 at 1:35 AM, Sijie Guo <guosi...@gmail.com> wrote:
>
> > +1. Jia, thank you for raising this up.
> >
> > I have a few questions:
> >
> > - Release Manager:
> >   Any volunteers on driving this release?
> >
> > - Pending changes:
> >   What are the pending changes that are blocking DL upgrade BK to 4.5.0
> > (both BK and DL side)?
> >
> > Any thoughts?
> >
> > - Sijie
> >
> >
> >
> > On Tue, Jul 25, 2017 at 6:17 PM, Jia Zhai <zhaiji...@gmail.com> wrote:
> >
> > > Hi All,
> > > Because DL is merged to BK, if BK is going to release 4.5.0, it would
> be
> > > good that DL can release 0.5.0 as well.  What do you think of this？ :)
> > >
> > > Thanks a lot.
> > > -Jia
> > >
> >
>

Re: [DISCUSS] Slack Channel for BookKeeper

[Sijie Guo]

On Wed, Jul 26, 2017 at 3:50 AM, atracymartin <atracymar...@gmail.com>
wrote:

> I am interested in learning more about the decision to merge DL into BK.
> What will that look like, and when will it be available?  What can I do to
> help?
>

Thank you Martin.

In short, DL (especially the core library) is more an extension to BK to
provide continuous log stream abstraction over bookkeeper.
Merge DL into BK is to bring a high level API on bookkeeper to simplify the
usage of BookKeeper and consolidate the efforts on building log stream
abstraction over BookKeeper. The vote
<http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3CCAO2yDya-%3D0cBfUM0SsL5kuf9HJ1G%3DpL7Z_%3D7Ps%2BTQgqwJs%3DCaA%40mail.gmail.com%3E>
link provides more insights about the considerations behind this.

>> What will that look like, and when will it be available?

DL has become a sub-project of BookKeeper already. But there are a few
INFRA tasks that BK PMC is working with INFRA team on it.
The git repo, mailing lists will remain same in the following few months.

At the same time, there are a couple of things happening (or will happen):

- the documentation, release procedure, ci builds will be aligned between
projects.
- we are working with Pulsar community for combining its managedledger
library (built over bookkeeper) with DL to provide a more robust log stream
library over bookkeeper.


>> What can I do to help?

Both BK and DL have some good projects for contributions.

Specially on the topic of merging DL into BK, there is one big outstanding
topic is to work with Pulsar community for combining its managedledger
library with DL to provide a unified log stream library on bookkeeper.
We started a gist a while ago -
https://gist.github.com/sijie/d7a242eb7d185e182b9a72c63534830b If you are
interested in this topic, feel free to participant.

Besides features/projects,

- Documentation is an area that need more contributions. Both BK and DL
don't have good documentation - the internal details of bookkeeper (for
developers), how to use it (for users), how to deploy and operate a cluster
(for administrators).
  It can be a good start to help us writing documentation around how to use
it and examples.
- Automate builds and release procedure can be another good area to
contribute as well.

Hope this helps.

- Sijie









>
>
> Sent from my T-Mobile 4G LTE Device
> ---- Original message From: Sijie Guo <guosi...@gmail.com>
> Date: 7/25/17  8:22 PM  (GMT-05:00) To: d...@bookkeeper.apache.org Cc:
> dev@distributedlog.incubator.apache.org Subject: Re: [DISCUSS] Slack
> Channel for BookKeeper
> Currently BK doesn't has one yet.
>
> On Tue, Jul 25, 2017 at 9:29 AM, Henry Saputra <henry.sapu...@gmail.com>
> wrote:
>
> > Is Apache BookKeeper has its own Slack team? If it has then we could just
> > add a channel for DistLog.
> >
> > - Henry
> >
> > On Mon, Jul 24, 2017 at 11:42 PM, Enrico Olivelli <eolive...@gmail.com>
> > wrote:
> >
> > > Awesome +1
> > >
> > > Il mar 25 lug 2017, 05:39 Dustin Castor <dustincas...@yahoo.com.invali
> d>
> > > ha
> > > scritto:
> > >
> > > > Agreed! Or an IRC.
> > > >
> > > > On Monday, July 24, 2017, 6:50:22 PM PDT, Jia Zhai <
> > zhaiji...@gmail.com>
> > > > wrote:
> > > >
> > > >  It is great to have a slack channel. It make things more effective
> > and
> > > > smooth.
> > > >
> > > > On Tue, Jul 25, 2017 at 8:11 AM, Sijie Guo <guosi...@gmail.com>
> wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > What do you guys all think about having a dedicated slack channel
> for
> > > > > informal discussion for the community? There are a handful of
> Apache
> > > > > projects are doing that already, there are also ways to have a bot
> > that
> > > > > sends daily digest of the conversation to the mailing lists (to
> keep
> > > the
> > > > > records in ASF infrastructure).
> > > > >
> > > > > As the followup steps for merging DL into BookKeeper, we are
> > > transferring
> > > > > the DL slack channel to BookKeeper PMC. We can just make it a BK
> > slack
> > > > > channel, and have different channels under it for different
> > > discussions.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > - Sijie
> > > > >
> > >
> > > --
> > >
> > >
> > > -- Enrico Olivelli
> > >
> >
>

Re: [Discuss] Release DL 0.5.0

[Sijie Guo]

+1. Jia, thank you for raising this up.

I have a few questions:

- Release Manager:
  Any volunteers on driving this release?

- Pending changes:
  What are the pending changes that are blocking DL upgrade BK to 4.5.0
(both BK and DL side)?

Any thoughts?

- Sijie



On Tue, Jul 25, 2017 at 6:17 PM, Jia Zhai  wrote:

> Hi All,
> Because DL is merged to BK, if BK is going to release 4.5.0, it would be
> good that DL can release 0.5.0 as well.  What do you think of this？ :)
>
> Thanks a lot.
> -Jia
>

Re: [DISCUSS] Slack Channel for BookKeeper

[Sijie Guo]

Currently BK doesn't has one yet.

On Tue, Jul 25, 2017 at 9:29 AM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> Is Apache BookKeeper has its own Slack team? If it has then we could just
> add a channel for DistLog.
>
> - Henry
>
> On Mon, Jul 24, 2017 at 11:42 PM, Enrico Olivelli <eolive...@gmail.com>
> wrote:
>
> > Awesome +1
> >
> > Il mar 25 lug 2017, 05:39 Dustin Castor <dustincas...@yahoo.com.invalid>
> > ha
> > scritto:
> >
> > > Agreed! Or an IRC.
> > >
> > > On Monday, July 24, 2017, 6:50:22 PM PDT, Jia Zhai <
> zhaiji...@gmail.com>
> > > wrote:
> > >
> > >  It is great to have a slack channel. It make things more effective
> and
> > > smooth.
> > >
> > > On Tue, Jul 25, 2017 at 8:11 AM, Sijie Guo <guosi...@gmail.com> wrote:
> > >
> > > > Hi all,
> > > >
> > > > What do you guys all think about having a dedicated slack channel for
> > > > informal discussion for the community? There are a handful of Apache
> > > > projects are doing that already, there are also ways to have a bot
> that
> > > > sends daily digest of the conversation to the mailing lists (to keep
> > the
> > > > records in ASF infrastructure).
> > > >
> > > > As the followup steps for merging DL into BookKeeper, we are
> > transferring
> > > > the DL slack channel to BookKeeper PMC. We can just make it a BK
> slack
> > > > channel, and have different channels under it for different
> > discussions.
> > > >
> > > > Thoughts?
> > > >
> > > > - Sijie
> > > >
> >
> > --
> >
> >
> > -- Enrico Olivelli
> >
>

[DISCUSS] Slack Channel for BookKeeper

[Sijie Guo]

Hi all,

What do you guys all think about having a dedicated slack channel for
informal discussion for the community? There are a handful of Apache
projects are doing that already, there are also ways to have a bot that
sends daily digest of the conversation to the mailing lists (to keep the
records in ASF infrastructure).

As the followup steps for merging DL into BookKeeper, we are transferring
the DL slack channel to BookKeeper PMC. We can just make it a BK slack
channel, and have different channels under it for different discussions.

Thoughts?

- Sijie

Re: [Discuss] Try Github issues for Issue tracking

[Sijie Guo]

+1. Since we are moving DL as the subproject of BookKeeper, it aligns our
goal for making the procedures between BK and DL consistent.

- Sijie

On Mon, Jun 19, 2017 at 8:07 PM, Jia Zhai  wrote:

> Hi all,
>
> Recently, Apache BookKeeper community discussed and decided to have a try
> on "github issues" for issue tracking,  What do you think of DistributedLog
> also have a try on “github issues”? :)
>
>
> At here, you could find the related discussion of BookKeeper here:
> http://mail-archives.apache.org/mod_mbox/bookkeeper-dev/
> 201706.mbox/thread?2
>
>
> And here is a proposal for BookKeeper github issues:
>
> https://cwiki.apache.org/confluence/display/BOOKKEEPER/
> BP-9+-+Github+issues+for+Issue+Tracking
>
>
> Thanks a lot.
>
> -Jia
>

Re: Github repo isn't in-sync with the git repo

[Sijie Guo]

I didn't do anything to it. I think it was just a delay on propagating the
changes from apache git to github mirror.

- Sijie

On Wed, Jun 14, 2017 at 9:52 AM, Jia Zhai <zhaiji...@gmail.com> wrote:

> That's great, Thanks Sijie.
> How is this happen, and Is there anything that we could do to avoid it? :)
>
> On Wed, Jun 14, 2017 at 1:58 AM, Enrico Olivelli <eolive...@gmail.com>
> wrote:
>
> > Now I see on apache git repo this sha
> > 07852d35856dca232450135913090bac27b29abe and on github the same
> > 07852d35856dca232450135913090bac27b29abe
> >
> > Thank you Sijie
> > -- Enrico
> >
> > 2017-06-12 21:49 GMT+02:00 Sijie Guo <guosi...@gmail.com>:
> > > It seems that the recent merged changes are not propagated into the
> > github
> > > mirror. it seems something is broken in INFRA. try to asking INFRA
> team.
> >
>

Github repo isn't in-sync with the git repo

[Sijie Guo]

It seems that the recent merged changes are not propagated into the github
mirror. it seems something is broken in INFRA. try to asking INFRA team.

Re: [VOTE] Merge DistributedLog as the subproject of Apache BookKeeper

[Sijie Guo]

(dropping general@)

- Sijie

On Thu, Jun 8, 2017 at 5:21 PM, Sijie Guo <guosi...@gmail.com> wrote:

> ( /cc bookkeeper dev@ and incubator general@ for awareness )
>
> Hi all,
>
> There was a joint discussion between BookKeeper PMC and DistributedLog
> PPMC about moving the development of DistributedLog as part of Apache
> BookKeeper. The reasons behind it are:
>
> First, DistributedLog is born as an extension to BookKeeper, to offer
> continuous log streams as the service. The ledger API in bookkeeper is a
> lower level API and has learning curves, while the log stream API in
> distributedlog is a higher level API that simplifies the usage. The
> combination of ledger API and stream API would offer a better
> developer/user experience for applications.
>
> Secondly, using ledgers to build continuous (re-openable) log stream is a
> very common pattern for BookKeeper use cases. We did this for HDFS namenode
> journal, for Hedwig, for DistributedLog, and for Pulsar. The same pattern
> has been implemented again and again. Merge DistributedLog (also
> ManagedLedger in Pulsar) with BookKeeper will consolidate all the
> development efforts around this common 'log stream' pattern.
>
> Thirdly, the 'log' stream abstraction is a good abstraction for both
> messaging and streaming. Internally at BookKeeper, there are a few places
> that can use such 'messaging' facility to improve bookkeeper itself. the
> log stream in DistributedLog can be used internally at bookkeeper for
> streaming changes as well.
>
> We choose merging DistributedLog as subproject rather than modules. It is
> a softer starting point to avoid disrupting the folks who are depending on
> the ledger api alone. The BookKeeper PMC and DistributedLog PPMC has
> achieved initial consensus on this merge. There is an official VOTE ongoing
> in bookkeeper PMC. We'd like to bring this to the distributedlog community
> for a community vote following the guidelines here
> <http://incubator.apache.org/guides/graduation.html#subproject>.
>
> Please vote +1 if in favor of merging DistributedLog to BookKeeper, and -1
> if not. The vote will be open until Tuesday 13rd June, 18:00 PST.
>
> - Sijie
>
>
>
>
>
>
>

Re: [VOTE] Merge DistributedLog as the subproject of Apache BookKeeper

[Sijie Guo]

On Thu, Jun 8, 2017 at 5:47 PM, John D. Ament <johndam...@apache.org> wrote:

> On Thu, Jun 8, 2017 at 8:44 PM Sijie Guo <guosi...@gmail.com> wrote:
>
> > Sure.
> >
> > The discussion email thread between BookKeeper PMC and DistributedLog
> PPMC:
> >
> > https://mail-search.apache.org/pmc/private-arch/
> bookkeeper-private/201706.mbox/%3CCAO2yDyZu+R1EaePyHZuFxe_W0qAkHNYxNnmn5+
> zx6q520uz...@mail.gmail.com%3E
> >
> > The BookKeeper PMC VOTE email thread (it is still ongoing):
> >
> > https://mail-search.apache.org/pmc/private-arch/
> bookkeeper-private/201706.mbox/%3CCAO2yDyacdXuXh==iw1OqrRiuGoxHprP_
> htnofojot5rxmv6...@mail.gmail.com%3E
> >
> > As our mentor suggested, I am following the process here :
> > http://incubator.apache.org/guides/graduation.html#subproject
> > This is the community vote for the first step. Let me know if I missed
> > anything.
> >
>
> You mean this is the vote on the PPMC?  If so please drop general@.
>

Yeah, it is the vote on the PPMC. The document is saying to copy the vote
to incubator general list when the VOTE is proposed.

I will drop general@ then.

- Sijie


>
>
> >
> > - Sijie
> >
> >
> >
> > On Thu, Jun 8, 2017 at 5:37 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > Sije,
> > >
> > > Can you provide links to the PPMC and PMC votes going on for this move?
> > >
> > > John
> > >
> > > On Thu, Jun 8, 2017 at 8:21 PM Sijie Guo <guosi...@gmail.com> wrote:
> > >
> > > > ( /cc bookkeeper dev@ and incubator general@ for awareness )
> > > >
> > > > Hi all,
> > > >
> > > > There was a joint discussion between BookKeeper PMC and
> DistributedLog
> > > PPMC
> > > > about moving the development of DistributedLog as part of Apache
> > > > BookKeeper. The reasons behind it are:
> > > >
> > > > First, DistributedLog is born as an extension to BookKeeper, to offer
> > > > continuous log streams as the service. The ledger API in bookkeeper
> is
> > a
> > > > lower level API and has learning curves, while the log stream API in
> > > > distributedlog is a higher level API that simplifies the usage. The
> > > > combination of ledger API and stream API would offer a better
> > > > developer/user experience for applications.
> > > >
> > > > Secondly, using ledgers to build continuous (re-openable) log stream
> > is a
> > > > very common pattern for BookKeeper use cases. We did this for HDFS
> > > namenode
> > > > journal, for Hedwig, for DistributedLog, and for Pulsar. The same
> > pattern
> > > > has been implemented again and again. Merge DistributedLog (also
> > > > ManagedLedger in Pulsar) with BookKeeper will consolidate all the
> > > > development efforts around this common 'log stream' pattern.
> > > >
> > > > Thirdly, the 'log' stream abstraction is a good abstraction for both
> > > > messaging and streaming. Internally at BookKeeper, there are a few
> > places
> > > > that can use such 'messaging' facility to improve bookkeeper itself.
> > the
> > > > log stream in DistributedLog can be used internally at bookkeeper for
> > > > streaming changes as well.
> > > >
> > > > We choose merging DistributedLog as subproject rather than modules.
> It
> > > is a
> > > > softer starting point to avoid disrupting the folks who are depending
> > on
> > > > the ledger api alone. The BookKeeper PMC and DistributedLog PPMC has
> > > > achieved initial consensus on this merge. There is an official VOTE
> > > ongoing
> > > > in bookkeeper PMC. We'd like to bring this to the distributedlog
> > > community
> > > > for a community vote following the guidelines here
> > > > <http://incubator.apache.org/guides/graduation.html#subproject>.
> > > >
> > > > Please vote +1 if in favor of merging DistributedLog to BookKeeper,
> and
> > > -1
> > > > if not. The vote will be open until Tuesday 13rd June, 18:00 PST.
> > > >
> > > > - Sijie
> > > >
> > >
> >
>

Re: [VOTE] Merge DistributedLog as the subproject of Apache BookKeeper

[Sijie Guo]

Sure.

The discussion email thread between BookKeeper PMC and DistributedLog PPMC:
https://mail-search.apache.org/pmc/private-arch/bookkeeper-private/201706.mbox/%3ccao2ydyzu+r1eaepyhzufxe_w0qakhnyxnnmn5+zx6q520uz...@mail.gmail.com%3E

The BookKeeper PMC VOTE email thread (it is still ongoing):
https://mail-search.apache.org/pmc/private-arch/bookkeeper-private/201706.mbox/%3CCAO2yDyacdXuXh==iw1oqrriugoxhprp_htnofojot5rxmv6...@mail.gmail.com%3E

As our mentor suggested, I am following the process here :
http://incubator.apache.org/guides/graduation.html#subproject
This is the community vote for the first step. Let me know if I missed
anything.

- Sijie



On Thu, Jun 8, 2017 at 5:37 PM, John D. Ament <johndam...@apache.org> wrote:

> Sije,
>
> Can you provide links to the PPMC and PMC votes going on for this move?
>
> John
>
> On Thu, Jun 8, 2017 at 8:21 PM Sijie Guo <guosi...@gmail.com> wrote:
>
> > ( /cc bookkeeper dev@ and incubator general@ for awareness )
> >
> > Hi all,
> >
> > There was a joint discussion between BookKeeper PMC and DistributedLog
> PPMC
> > about moving the development of DistributedLog as part of Apache
> > BookKeeper. The reasons behind it are:
> >
> > First, DistributedLog is born as an extension to BookKeeper, to offer
> > continuous log streams as the service. The ledger API in bookkeeper is a
> > lower level API and has learning curves, while the log stream API in
> > distributedlog is a higher level API that simplifies the usage. The
> > combination of ledger API and stream API would offer a better
> > developer/user experience for applications.
> >
> > Secondly, using ledgers to build continuous (re-openable) log stream is a
> > very common pattern for BookKeeper use cases. We did this for HDFS
> namenode
> > journal, for Hedwig, for DistributedLog, and for Pulsar. The same pattern
> > has been implemented again and again. Merge DistributedLog (also
> > ManagedLedger in Pulsar) with BookKeeper will consolidate all the
> > development efforts around this common 'log stream' pattern.
> >
> > Thirdly, the 'log' stream abstraction is a good abstraction for both
> > messaging and streaming. Internally at BookKeeper, there are a few places
> > that can use such 'messaging' facility to improve bookkeeper itself. the
> > log stream in DistributedLog can be used internally at bookkeeper for
> > streaming changes as well.
> >
> > We choose merging DistributedLog as subproject rather than modules. It
> is a
> > softer starting point to avoid disrupting the folks who are depending on
> > the ledger api alone. The BookKeeper PMC and DistributedLog PPMC has
> > achieved initial consensus on this merge. There is an official VOTE
> ongoing
> > in bookkeeper PMC. We'd like to bring this to the distributedlog
> community
> > for a community vote following the guidelines here
> > <http://incubator.apache.org/guides/graduation.html#subproject>.
> >
> > Please vote +1 if in favor of merging DistributedLog to BookKeeper, and
> -1
> > if not. The vote will be open until Tuesday 13rd June, 18:00 PST.
> >
> > - Sijie
> >
>

[VOTE] Merge DistributedLog as the subproject of Apache BookKeeper

[Sijie Guo]

( /cc bookkeeper dev@ and incubator general@ for awareness )

Hi all,

There was a joint discussion between BookKeeper PMC and DistributedLog PPMC
about moving the development of DistributedLog as part of Apache
BookKeeper. The reasons behind it are:

First, DistributedLog is born as an extension to BookKeeper, to offer
continuous log streams as the service. The ledger API in bookkeeper is a
lower level API and has learning curves, while the log stream API in
distributedlog is a higher level API that simplifies the usage. The
combination of ledger API and stream API would offer a better
developer/user experience for applications.

Secondly, using ledgers to build continuous (re-openable) log stream is a
very common pattern for BookKeeper use cases. We did this for HDFS namenode
journal, for Hedwig, for DistributedLog, and for Pulsar. The same pattern
has been implemented again and again. Merge DistributedLog (also
ManagedLedger in Pulsar) with BookKeeper will consolidate all the
development efforts around this common 'log stream' pattern.

Thirdly, the 'log' stream abstraction is a good abstraction for both
messaging and streaming. Internally at BookKeeper, there are a few places
that can use such 'messaging' facility to improve bookkeeper itself. the
log stream in DistributedLog can be used internally at bookkeeper for
streaming changes as well.

We choose merging DistributedLog as subproject rather than modules. It is a
softer starting point to avoid disrupting the folks who are depending on
the ledger api alone. The BookKeeper PMC and DistributedLog PPMC has
achieved initial consensus on this merge. There is an official VOTE ongoing
in bookkeeper PMC. We'd like to bring this to the distributedlog community
for a community vote following the guidelines here
.

Please vote +1 if in favor of merging DistributedLog to BookKeeper, and -1
if not. The vote will be open until Tuesday 13rd June, 18:00 PST.

- Sijie

Re: DistributedLog Podling Report Draft - May 2017

[Sijie Guo]

I updated the wiki page.

Mentors, can you guys check the wiki page?

https://wiki.apache.org/incubator/May2017

- Sijie


On Wed, May 3, 2017 at 5:07 PM, Sijie Guo <guosi...@gmail.com> wrote:

> Thank you folks.
>
> I will update the wiki page then.
>
> - Sijie
>
> On Tue, May 2, 2017 at 9:02 AM, Jia Zhai <zhaiji...@gmail.com> wrote:
>
>> +1
>>
>> On Tue, May 2, 2017 at 8:54 AM, Franck Cuny <fc...@apache.org> wrote:
>>
>> > +1
>> >
>> > On Mon, May 1, 2017 at 10:02 AM Leigh Stewart
>> <lstew...@twitter.com.invalid
>> > >
>> > wrote:
>> >
>> > > +1
>> > >
>> > > On Mon, May 1, 2017 at 9:43 AM, Sijie Guo <guosi...@gmail.com> wrote:
>> > >
>> > > > Hi, all,
>> > > >
>> > > > Here is the draft of podling report for May 2017. Please help review
>> > it.
>> > > >
>> > > > =
>> > > >
>> > > > DistributedLog
>> > > >
>> > > > DistributedLog is a high-performance replicated log service. It
>> offers
>> > > > durability, replication and strong consistency, which provides a
>> > > > fundamental building block for building reliable distributed
>> systems.
>> > > > DistributedLog has been incubating since 2016-06-24.
>> > > >
>> > > > Three most important issues to address in the move towards
>> graduation:
>> > > >
>> > > > 1.Continue to grow the community, and increase diversity of
>> community.
>> > > > 2.Improve documentation, including documentation of project and
>> > > processes.
>> > > > 3.Successful releases.
>> > > >
>> > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
>> be
>> > > aware
>> > > > of?
>> > > >
>> > > > None.
>> > > >
>> > > > How has the community developed since the last report?
>> > > >
>> > > > 1. community
>> > > >
>> > > > - Sijie gave a talk about DistributedLog at Strata+Hadoop San Jose.
>> > > > - The DistributedLog paper is accepted at ICDE 2017.
>> > > > - Leigh Stewart gave a presentation about DistributedLog at ICDE.
>> > > >
>> > > > 2. 44 people subscribed to dev mail list,
>> > > > 8 improvement proposal in progress,
>> > > > and 72 open issues.
>> > > >
>> > > > How has the project developed since the last report?
>> > > >
>> > > > - We have released the first Apache version : 0.4.0-incubating on
>> April
>> > > 25.
>> > > > - We start the work on release 0.5.0-incubating.
>> > > >
>> > > > - Sijie
>> > > >
>> > >
>> > --
>> > -franck
>> >
>>
>
>

Re: DistributedLog Podling Report Draft - May 2017

[Sijie Guo]

Thank you folks.

I will update the wiki page then.

- Sijie

On Tue, May 2, 2017 at 9:02 AM, Jia Zhai <zhaiji...@gmail.com> wrote:

> +1
>
> On Tue, May 2, 2017 at 8:54 AM, Franck Cuny <fc...@apache.org> wrote:
>
> > +1
> >
> > On Mon, May 1, 2017 at 10:02 AM Leigh Stewart
> <lstew...@twitter.com.invalid
> > >
> > wrote:
> >
> > > +1
> > >
> > > On Mon, May 1, 2017 at 9:43 AM, Sijie Guo <guosi...@gmail.com> wrote:
> > >
> > > > Hi, all,
> > > >
> > > > Here is the draft of podling report for May 2017. Please help review
> > it.
> > > >
> > > > =
> > > >
> > > > DistributedLog
> > > >
> > > > DistributedLog is a high-performance replicated log service. It
> offers
> > > > durability, replication and strong consistency, which provides a
> > > > fundamental building block for building reliable distributed systems.
> > > > DistributedLog has been incubating since 2016-06-24.
> > > >
> > > > Three most important issues to address in the move towards
> graduation:
> > > >
> > > > 1.Continue to grow the community, and increase diversity of
> community.
> > > > 2.Improve documentation, including documentation of project and
> > > processes.
> > > > 3.Successful releases.
> > > >
> > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > aware
> > > > of?
> > > >
> > > > None.
> > > >
> > > > How has the community developed since the last report?
> > > >
> > > > 1. community
> > > >
> > > > - Sijie gave a talk about DistributedLog at Strata+Hadoop San Jose.
> > > > - The DistributedLog paper is accepted at ICDE 2017.
> > > > - Leigh Stewart gave a presentation about DistributedLog at ICDE.
> > > >
> > > > 2. 44 people subscribed to dev mail list,
> > > > 8 improvement proposal in progress,
> > > > and 72 open issues.
> > > >
> > > > How has the project developed since the last report?
> > > >
> > > > - We have released the first Apache version : 0.4.0-incubating on
> April
> > > 25.
> > > > - We start the work on release 0.5.0-incubating.
> > > >
> > > > - Sijie
> > > >
> > >
> > --
> > -franck
> >
>

Re: Podling Report Reminder - May 2017

[Sijie Guo]

Hi Henry, I already started an email about that.

- Sijie

On Mon, May 1, 2017 at 11:05 PM, Henry Saputra 
wrote:

> Anyone would like to volunteer to write up  the report for DistLog podling?
>
> - Henry
>
> On Mon, May 1, 2017 at 8:12 PM,  wrote:
>
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 17 May 2017, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, May 03).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/May2017
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
>

DistributedLog Podling Report Draft - May 2017

[Sijie Guo]

Hi, all,

Here is the draft of podling report for May 2017. Please help review it.

=

DistributedLog

DistributedLog is a high-performance replicated log service. It offers
durability, replication and strong consistency, which provides a
fundamental building block for building reliable distributed systems.
DistributedLog has been incubating since 2016-06-24.

Three most important issues to address in the move towards graduation:

1.Continue to grow the community, and increase diversity of community.
2.Improve documentation, including documentation of project and processes.
3.Successful releases.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

None.

How has the community developed since the last report?

1. community

- Sijie gave a talk about DistributedLog at Strata+Hadoop San Jose.
- The DistributedLog paper is accepted at ICDE 2017.
- Leigh Stewart gave a presentation about DistributedLog at ICDE.

2. 44 people subscribed to dev mail list,
8 improvement proposal in progress,
and 72 open issues.

How has the project developed since the last report?

- We have released the first Apache version : 0.4.0-incubating on April 25.
- We start the work on release 0.5.0-incubating.

- Sijie

[ANNOUNCE] Apache DistributedLog 0.4.0-incubating Release

[Sijie Guo]

The Apache DistributedLog team would like to announce the release of Apache
DistributedLog 0.4.0-incubating.

Apache DistributedLog (incubating) is a high performance replicated log
store. It provides replicated-log as the storage primitive for building
real-time services. Its serves as a fundamental building block for
distributed applications that requires durability, replication and strong
consistency.

The highlights of 0.4.0-incubating are:

- Refactor the codebase to abstract the core metadata and data operations
for the log store into interfaces. So developers can easily integrate
DistributedLog with other metadata stores like etcd, and integrate
DistributedLog with other cold data stores like HDFS, S3.
- A new read ahead implementation for the log reader to better handle slow
storage nodes.
- Provide the log stream placement policy on the proxy service, to develop
and experiment with different placement policies and integrate with
different auto-scaling mechanisms.

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/distributedlog/0.4.0-incubating/

All JIRAs completed for this release are tagged with 'FixVersion =
0.4.0-incubating'; the JIRA release notes can be found here:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320620=12337980

Release notes are available at:

https://distributedlog.incubator.apache.org/docs/latest/start/download

More details regarding Apache DistributedLog (incubating) can be found here:
https://distributedlog.incubator.apache.org/

We thank everyone who made this release possible.

Thanks!
The Apache DistributedLog Team



DISCLAIMER:

Apache DistributedLog is an effort undergoing incubation at The Apache
Software Foundation (ASF),
sponsored by the Apache Incubator PMC. Incubation is required of all newly
accepted projects until
a further review indicates that the infrastructure, communications, and
decision making process have
stabilized in a manner consistent with other successful ASF projects. While
incubation status is not
necessarily a reflection of the completeness or stability of the code, it
does indicate that the
project has yet to be fully endorsed by the ASF.

Re: [RESULT] [VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

Oh, my bad. I didn't check that. I was just counting the votes. So we need
one more binding vote for approving this release?

- Sijie

On Mon, Apr 24, 2017 at 5:11 PM, John D. Ament <johndam...@apache.org>
wrote:

> Sijie,
>
> I can't find anyone by the name of Ivam Firestone on the IPMC.  Please
> double check your binding votes.
>
> http://home.apache.org/phonebook.html?ctte=incubator
>
> John
>
> On Mon, Apr 24, 2017 at 6:44 PM Sijie Guo <guosi...@gmail.com> wrote:
>
> > There are 3 binding approving votes, all of which are following:
> >
> > - Ivam Firestone
> > - John D. Ament
> > - Henry Saputra
> >
> > There are no disapproving votes.
> >
> > We will proceed with this release as staged.
> >
> > Thanks everyone!
> >
> > - Sijie
> >
> >
> >
> > On Mon, Apr 17, 2017 at 11:55 PM, Sijie Guo <guosi...@gmail.com> wrote:
> >
> > > Hi all,
> > >
> > > Please review and vote on the release candidate #4 for the Apache
> > > DistributedLog version 0.4.0-incubating, as follows:
> > >
> > > [ ] +1, Approve the release
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > >
> > > The complete staging area is available for your review, which includes:
> > >
> > > * JIRA release notes [1],
> > > * the official Apache source release to be deployed to
> > dist.apache.org
> > >  [2],
> > > * all artifacts to be deployed to the Maven Central Repository
> > [3][4],
> > > * source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
> > > "v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
> > > * website pull request listing the release [7] and publishing the
> API
> > > reference manual.
> > >
> > > The Apache DistributedLog community has unanimously approved this
> release
> > > [8].
> > >
> > > As customary, the vote will be open for at least 72 hours. It is
> adopted
> > > by a majority approval with at least three PMC affirmative votes. If
> > > approved, we will proceed with the release.
> > >
> > > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
> > > ersion=12337980==12320620
> > > [2] https://dist.apache.org/repos/dist/dev/incubator/distrib
> > > utedlog/0.4.0-incubating-RC4/
> > > [3] https://repository.apache.org/content/repositories/orgap
> > > achedistributedlog-1007/
> > > [4] https://repository.apache.org/content/repositories/orgap
> > > achedistributedlog-1008/
> > > [5] https://github.com/apache/incubator-distributedlog/tree/
> > > v0.4.0-incubating-RC4_2.11
> > > [6] https://github.com/apache/incubator-distributedlog/tree/
> > > v0.4.0-incubating-RC4_2.10
> > > [7] https://github.com/apache/incubator-distributedlog/pull/109
> > > [8] http://mail-archives.apache.org/mod_mbox/incubator-
> > > distributedlog-dev/201704.mbox/%3CCAO2yDybFhsNJcPkWC%3DriW9rJfesHA0_
> > > iC2NaS7pabpBV1ey5tg%40mail.gmail.com%3E
> > >
> >
>

Re: [DISCUSS] DP-8: Symlinked Log

[Sijie Guo]

Agreed that a general reconfiguration approach will be ideal for solving
the problems

However currently DL is using a metadata store (e.g. ZooKeeper) for storing
and managing the metadata part. So the capabilities of metadata
reconfiguration is kind of limited by the features offered by the metadata
store. For example, zookeeper doesn't support rename operations. A symlink
approach here is try to address the metadata reconfiguration problem when
the underneath metadata store lacks such ability. Beside that, moving a
flat namespace to a hierarchical namespace in general is a long-duration
operation. So an approach should exist to allow both co-exist for a while
and allow rolling back and forward.

- Sijie

On Wed, Apr 19, 2017 at 8:14 AM, Dan Benediktson <dbenedikt...@twitter.com>
wrote:

> It seems to me that the fact that the namespace format needs to be changed
> is the specific, immediate problem, but the bigger problem is that there
> isn't a mechanism to perform an atomic reconfiguration step for log
> metadata. Namespace format change is one example of a reconfiguration (if
> we start viewing namespace format as a part of log metadata, which just
> happens to currently be unspecified since there is no format other than the
> flat one), but there are already other metadata reconfiguration changes
> that are desired: https://issues.apache.org/jira/browse/DL-74 and
> https://issues.apache.org/jira/browse/DL-77. I think we should try to
> solve the general reconfiguration problem correctly first, and then that
> should enable us to solve both this problem and those two more naturally. I
> expect that a correct reconfiguration solution would obviate the need for
> this sub-task: https://issues.apache.org/jira/browse/DL-201.
>
> On Tue, Apr 18, 2017 at 1:06 PM, Leigh Stewart <lstew...@twitter.com>
> wrote:
>
>> + Dan
>>
>> On Tue, Apr 18, 2017 at 1:04 PM, Sijie Guo <guosi...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I created a proposal for supporting symlinks in Dlog, in order to
>>> migrate a namespace from flat namespace to a hierarchical namespace.
>>>
>>> https://cwiki.apache.org/confluence/display/DL/DP-8+-+Symlinked+Log
>>>
>>> Please take a look and let me know your thoughts.
>>>
>>> - Sijie
>>>
>>>
>>
>

[VOTE] Apache DistributedLog release 0.4.0-incubating (RC#4)

[Sijie Guo]

Hi all,

Please review and vote on the release candidate #4 for the Apache
DistributedLog version 0.4.0-incubating, as follows:

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which includes:

* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
 [2],
* all artifacts to be deployed to the Maven Central Repository [3][4],
* source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
"v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
* website pull request listing the release [7] and publishing the API
reference manual.

The Apache DistributedLog community has unanimously approved this release
[8].

As customary, the vote will be open for at least 72 hours. It is adopted by a
majority approval with at least three PMC affirmative votes. If approved, we
will proceed with the release.

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
ersion=12337980==12320620
[2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
incubating-RC4/
[3] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1007/
[4] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1008/
[5] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC4_2.11
[6] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC4_2.10
[7] https://github.com/apache/incubator-distributedlog/pull/109
[8]
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201704.mbox/%3CCAO2yDybFhsNJcPkWC%3DriW9rJfesHA0_iC2NaS7pabpBV1ey5tg%40mail.gmail.com%3E

Re: [VOTE] Release 0.4.0, release candidate #4

[Sijie Guo]

I am happy to announce that we have unanimously approved this release.

There are 6 +1 votes and no disapproving votes.

Thanks everyone!

On Thu, Apr 13, 2017 at 12:36 AM, Sijie Guo <guosi...@gmail.com> wrote:

> Hi all,
>
> Please review and vote on the release candidate #4 for the version 0.4.0,
> as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
>  [2],
> * all artifacts to be deployed to the Maven Central Repository [3][4],
> * source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
> "v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
> * website pull request listing the release [7] and publishing the API
> reference manual.
>
> A simple instruction for validation the source and binary packages.
>
> - source package: building the package with "*mvn clean apache-rat:check
> package findbugs:check -DskipTests*"
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PPMC affirmative votes.
>
> Thanks,
> Sijie
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
> ersion=12337980==12320620
> [2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating-RC4/
> [3] https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1007/
> [4] https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1008/
> [5] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC4_2.11
> [6] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC4_2.10
> [7] https://github.com/apache/incubator-distributedlog/pull/109
>

Vote Release 0.4.0 RC#4

[Sijie Guo]

Due to some license header issue, the IPMC rejected the RC #3. We just
fixed the license header issue. RC#4 is out. Please take your time to check
it out and vote.

- Sijie

[VOTE] Release 0.4.0, release candidate #4

[Sijie Guo]

Hi all,

Please review and vote on the release candidate #4 for the version 0.4.0,
as follows:

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which includes:

* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
 [2],
* all artifacts to be deployed to the Maven Central Repository [3][4],
* source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
"v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
* website pull request listing the release [7] and publishing the API
reference manual.

A simple instruction for validation the source and binary packages.

- source package: building the package with "*mvn clean apache-rat:check
package findbugs:check -DskipTests*"

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PPMC affirmative votes.

Thanks,
Sijie

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
version=12337980==12320620
[2]
https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-incubating-RC4/
[3]
https://repository.apache.org/content/repositories/orgapachedistributedlog-1007/
[4]
https://repository.apache.org/content/repositories/orgapachedistributedlog-1008/
[5]
https://github.com/apache/incubator-distributedlog/tree/v0.4.0-incubating-RC4_2.11
[6]
https://github.com/apache/incubator-distributedlog/tree/v0.4.0-incubating-RC4_2.10
[7] https://github.com/apache/incubator-distributedlog/pull/109

Re: [DISCUSS] Combining the NOTICE, LICENSE, and DISCLAIMER files

[Sijie Guo]

I created https://issues.apache.org/jira/browse/DL-198 for combining those
asf files.

https://github.com/apache/incubator-distributedlog/pull/128 is out for
review.

Can mentors take a look to make sure I am doing the right thing for asf
files?

- Sijie

On Mon, Apr 10, 2017 at 11:52 PM, Sijie Guo <guosi...@gmail.com> wrote:

> I think this is doable - we can change the binary package assembly
> configuration (src/assemble/bin/xml) to include NOTICE/DISCLAIMER/LICENSE
> from root directly.
>
> Let me file one JIRA and send out a pull request for it.
>
> - Sijie
>
> On Mon, Apr 10, 2017 at 5:02 PM, Henry Saputra <henry.sapu...@gmail.com>
> wrote:
>
>> Hi All,
>>
>> Seemed like we have 2 locations of the ASF license files:
>>
>> one in the root
>> and one in src/main/resources
>>
>> The problem is that content of the files are different.
>>
>> Could we change the build system to bundle them using the ones in root
>> location instead?
>>
>> Thanks,
>>
>> - Henry
>>
>
>

Re: [DISCUSS] Combining the NOTICE, LICENSE, and DISCLAIMER files

[Sijie Guo]

I think this is doable - we can change the binary package assembly
configuration (src/assemble/bin/xml) to include NOTICE/DISCLAIMER/LICENSE
from root directly.

Let me file one JIRA and send out a pull request for it.

- Sijie

On Mon, Apr 10, 2017 at 5:02 PM, Henry Saputra 
wrote:

> Hi All,
>
> Seemed like we have 2 locations of the ASF license files:
>
> one in the root
> and one in src/main/resources
>
> The problem is that content of the files are different.
>
> Could we change the build system to bundle them using the ones in root
> location instead?
>
> Thanks,
>
> - Henry
>

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

Awesome. I learned a lot from this discussion. We will address these
comments and call another vote.

- Sijie

On Mon, Apr 10, 2017 at 3:11 PM, Marvin Humphrey 
wrote:

> On Mon, Apr 10, 2017 at 2:28 PM, Henry Saputra 
> wrote:
> > The question is whether we need to keep this section:
> >
> > Portions of this software were developed by Twitter.
> > Copyright Twitter, 2017
> >
> > in the NOTICE file. Since Twitter already signed off the source
> > contributions, we could probably remove this section.
>
> Only Twitter's authorized representative may legally remove Twitter's
> copyright notice.  Everyone else must leave it alone.
>
> Unless something unusual has occurred (like a new SGA from Twitter in
> 2017),
> there should not have been a need to update Twitter's copyright.  Josh was
> right to flag that as weird.
>
> Sijie, I see that it was your commit that changed the copyright year in
> NOTICE.  It was correct to update the ASF copyright, so please leave that
> as
> 2017 (and continue to updated it in future years).  For the Twitter
> copyright,
> please either restore the 2016 date or discuss any unusual circumstances.
> (Feel free to ask questions, we're here to help.)
>
> Josh was also right to flag the addition of the "Copyright 2017 The Apache
> Software Foundation" notices in source headers.
>
> http://www.apache.org/legal/src-headers.html#headers
>
> 2. Each source file should include the following license header -- note
>that there should be no copyright notice in the header:
>
> For individual files, contributors continue to hold copyright on their
> contributions.  The ASF (unlike some other entities such as the FSF) does
> not
> require copyright assignment.  Thus the ASF only holds copyright in the
> collection; that's what's expressed in the NOTICE file ASF copyright
> notice.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

Hi everyone,

Please review and vote on the release candidate #3 for the Apache
DistributedLog version 0.4.0-incubating, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which includes:

* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
 [2],
* all artifacts to be deployed to the Maven Central Repository [3],
* source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
"v0.4.0-incubating-RC1_2.10" (for scala 2.10) [4][5],
* website pull request listing the release [6] and publishing the API
reference manual.

The Apache DistributedLog community has unanimously approved this release
[7].

As customary, the vote will be open for at least 72 hours. It is adopted by a
majority approval with at least three PMC affirmative votes. If approved, we
will proceed with the release.

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
version=12337980==12320620
[2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
incubating-RC3/
[3] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1006/
[4] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC3_2.11
[5] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC3_2.10
[6] https://github.com/apache/incubator-distributedlog/pull/109
[7]
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201704.mbox/%3CCAO2yDyY7DxeQ0Xnm9sPmXTjwF_yhc8nAHN%2B4VxmD7jjGbyoGjQ%40mail.gmail.com%3E

Re: [VOTE] Release 0.4.0, release candidate #3

[Sijie Guo]

I am happy to announce that we have unanimously approved this release.

There are 8 +1 votes and no disapproving votes.

Thanks everyone!

- Sijie

On Tue, Mar 28, 2017 at 3:29 PM, Sijie Guo <guosi...@gmail.com> wrote:

> Hi all,
>
> Please review and vote on the release candidate #3 for the version 0.4.0,
> as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
>  [2],
> * all artifacts to be deployed to the Maven Central Repository [3],
> * source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [4][5],
> * website pull request listing the release [6] and publishing the API
> reference manual.
>
> A simple instruction for validation the source and binary packages.
>
> - source package: building the package with "*mvn clean apache-rat:check
> package findbugs:check -DskipTests*"
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PPMC affirmative votes.
>
> Thanks,
> Sijie
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12337980==12320620
> [2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating-RC3/
> [3] https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1006/
> [4] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC3_2.11
> [5] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC3_2.10
> [6] https://github.com/apache/incubator-distributedlog/pull/109
>

Re: [VOTE] Release 0.4.0, release candidate #3

[Sijie Guo]

Can any mentors take a look at this release? If it looks good, I will try
voting in incubator mail list.

- Sijie

On Tue, Apr 4, 2017 at 1:50 AM, Jay Juma <jayk.j...@gmail.com> wrote:

> +1 (non-binding)
>
>
>
> On Tue, Mar 28, 2017 at 3:29 PM, Sijie Guo <guosi...@gmail.com> wrote:
>
> > Hi all,
> >
> > Please review and vote on the release candidate #3 for the version 0.4.0,
> > as follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staging area is available for your review, which includes:
> >
> > * JIRA release notes [1],
> > * the official Apache source release to be deployed to
> dist.apache.org
> >  [2],
> > * all artifacts to be deployed to the Maven Central Repository [3],
> > * source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> > "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [4][5],
> > * website pull request listing the release [6] and publishing the API
> > reference manual.
> >
> > A simple instruction for validation the source and binary packages.
> >
> > - source package: building the package with "*mvn clean apache-rat:check
> > package findbugs:check -DskipTests*"
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PPMC affirmative votes.
> >
> > Thanks,
> > Sijie
> >
> > [1]
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12337980==12320620
> > [2]
> > https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> > incubating-RC3/
> > [3]
> > https://repository.apache.org/content/repositories/
> > orgapachedistributedlog-1006/
> > [4]
> > https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC3_2.11
> > [5]
> > https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC3_2.10
> > [6] https://github.com/apache/incubator-distributedlog/pull/109
> >
>

Re: Apache BookKeeper Talk at #lfvault

[Sijie Guo]

Henry,

(sorry I missed your email here)

It went pretty well. There were quite a lot of attendees and quite a few
questions at the end of talk. Hope it would help the community on BK and DL.

- Sijie

On Fri, Mar 24, 2017 at 4:28 PM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> Nice! How did it go?
>
> On Thu, Mar 23, 2017 at 3:00 PM, Sijie Guo <guosi...@gmail.com> wrote:
>
> > FYI.
> >
> > This is the slides of the bookkeeper talk JV and me gave at #lfvault. You
> > can check it out if you are interested in.
> >
> > https://vault2017.sched.com/event/A4wM/apache-bookkeeper-
> > a-high-performance-and-low-latency-cloud-storage-service-
> sijie-guo-twitter
> >
> > http://www.slideshare.net/hustlmsp/apache-bookkeeper-a-
> > high-performance-and-low-latency-storage-service
> >
> > - Sijie
> >
>

Re: [VOTE] Release 0.4.0, release candidate #3

[Sijie Guo]

I think apache-rat:check will fail because of
https://issues.apache.org/jira/browse/DL-195. But I don't think it is a
blocker for the release.

- Sijie

On Tue, Mar 28, 2017 at 3:29 PM, Sijie Guo <guosi...@gmail.com> wrote:

> Hi all,
>
> Please review and vote on the release candidate #3 for the version 0.4.0,
> as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
>  [2],
> * all artifacts to be deployed to the Maven Central Repository [3],
> * source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [4][5],
> * website pull request listing the release [6] and publishing the API
> reference manual.
>
> A simple instruction for validation the source and binary packages.
>
> - source package: building the package with "*mvn clean apache-rat:check
> package findbugs:check -DskipTests*"
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PPMC affirmative votes.
>
> Thanks,
> Sijie
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12337980==12320620
> [2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating-RC3/
> [3] https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1006/
> [4] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC3_2.11
> [5] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC3_2.10
> [6] https://github.com/apache/incubator-distributedlog/pull/109
>

Re: release 0.4.0

[Sijie Guo]

Got back on the release. Will cut a new release RC on the weekend.

- Sijie

On Mon, Feb 13, 2017 at 10:00 AM, Sijie Guo <si...@apache.org> wrote:

> It seems that we already got all the issues addressed in the pull
> requests. I will try to cut a new release candidate soon. (I am traveling
> these days, so my time is not very guaranteed. I will try to do my best to
> cut an RC).
>
> - Sijie
>
> On Mon, Jan 30, 2017 at 6:22 PM, Sijie Guo <si...@apache.org> wrote:
>
>> The release is rejected by IPMC. There are 3 issues:
>>
>> - missing disclaimer file : https://github.com/apache/in
>> cubator-distributedlog/pull/120
>> - notice file year is wrong: https://github.com/apac
>> he/incubator-distributedlog/pull/119
>> - copyright year is wrong: https://github.com/apac
>> he/incubator-distributedlog/pull/121
>>
>> We need to address these issues and cut another RC.
>>
>> Can anyone review these? It would be great if the mentors can take a look
>> at those fixes too.
>>
>> - Sijie
>>
>
>

Re: release 0.4.0

[Sijie Guo]

It seems that we already got all the issues addressed in the pull requests.
I will try to cut a new release candidate soon. (I am traveling these days,
so my time is not very guaranteed. I will try to do my best to cut an RC).

- Sijie

On Mon, Jan 30, 2017 at 6:22 PM, Sijie Guo <si...@apache.org> wrote:

> The release is rejected by IPMC. There are 3 issues:
>
> - missing disclaimer file : https://github.com/apache/
> incubator-distributedlog/pull/120
> - notice file year is wrong: https://github.com/apache/incubator-
> distributedlog/pull/119
> - copyright year is wrong: https://github.com/apache/incubator-
> distributedlog/pull/121
>
> We need to address these issues and cut another RC.
>
> Can anyone review these? It would be great if the mentors can take a look
> at those fixes too.
>
> - Sijie
>

Re: DistributedLog Podling Report Draft - Feb 2017

[Sijie Guo]

I updated this to the incubator wiki page -
https://wiki.apache.org/incubator/February2017

Please take a look and let me know if you have any questions.

Can mentors take a look and sign off?

- Sijie

On Wed, Feb 1, 2017 at 1:10 PM, Sijie Guo <si...@apache.org> wrote:

> If there is no objection here, I would like to update the incubator board
> report.
>
> Can any mentors take a look too?
>
> - Sijie
>
> On Wed, Feb 1, 2017 at 9:17 AM, Khurrum Nasim <khurrumnas...@gmail.com>
> wrote:
>
>> +1 thank you for putting this up, Sijie.
>>
>> - KN
>>
>> On Tue, Jan 31, 2017 at 11:17 PM, Xi Liu <xi.liu@gmail.com> wrote:
>>
>> > lgtm. +1
>> >
>> > it might be good to mention the slack channel for community development.
>> >
>> > - Xi
>> >
>> > On Tue, Jan 31, 2017 at 2:01 PM, Sijie Guo <si...@apache.org> wrote:
>> >
>> > > Hi, all,
>> > >
>> > > Here is the draft of podling report for Feb 2017. Please help review
>> it.
>> > >
>> > > =
>> > >
>> > > DistributedLog
>> > >
>> > > DistributedLog is a high-performance replicated log service. It offers
>> > > durability, replication and strong consistency, which provides a
>> > > fundamental building block for building reliable distributed systems.
>> > > DistributedLog has been incubating since 2016-06-24.
>> > >
>> > > Three most important issues to address in the move towards graduation:
>> > >
>> > > 1.Continue to grow the community, and increase diversity of community.
>> > > 2.Improve documentation, including documentation of project and
>> > processes.
>> > > 3.Successful releases.
>> > >
>> > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> > aware
>> > > of?
>> > >
>> > > None
>> > >
>> > > How has the community developed since the last report?
>> > >
>> > > 1. Increase in contributions from community.
>> > >- 127 created and 103 resolved issues in community JIRA between Nov
>> > 2016
>> > > and Feb 2017.
>> > > 2. Lots of engagements on feature proposals - 7 improvement proposals.
>> > > 3. Increased traffic on the mailing list, in particular, due to
>> > committers
>> > > engaging more actively with contributors.
>> > >- we have 43 people subscribed mail list.
>> > >
>> > > How has the project developed since the last report?
>> > >
>> > > The community is voting for release 0.4.0-incubating.
>> > >
>> > > - Sijie
>> > >
>> >
>>
>
>

release 0.4.0

[Sijie Guo]

The release is rejected by IPMC. There are 3 issues:

- missing disclaimer file :
https://github.com/apache/incubator-distributedlog/pull/120
- notice file year is wrong:
https://github.com/apache/incubator-distributedlog/pull/119
- copyright year is wrong:
https://github.com/apache/incubator-distributedlog/pull/121

We need to address these issues and cut another RC.

Can anyone review these? It would be great if the mentors can take a look
at those fixes too.

- Sijie

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

Gotcha. Cancelling the vote. Will address the concerns in new RC.

Thanks John!

- Sijie

On Thu, Jan 26, 2017 at 5:46 PM, John D. Ament <johndam...@apache.org>
wrote:

> On Thu, Jan 26, 2017 at 8:27 PM Sijie Guo <si...@apache.org> wrote:
>
> > On Thu, Jan 26, 2017 at 6:06 AM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > Its not clear if you intended this to be the IPMC vote or the dev vote.
> > >
> >
> > Sorry. it is my first time doing incubator project release. If I made
> > something wrong, please let me know.
> >
> > This is vote is intended to for the IPMC vote.
> >
> >
> > >
> > > -1 Since the release does not include the DISCLAIMER file and README
> does
> > > not include the DISCLAIMER text (either would be fine per policy, but
> > > generally we look for DISCLAIMER).
> > >
> >
> > Gotcha. We will try to add this.
> >
> >
> > >
> > > There were no binaries in the source.
> >
> >
> > The source package only includes source codes. The binaries are shipped
> as
> > two separated packages, one is service package, the other one is
> benchmark
> > package. Is there a policy about packaging?
> >
> >
> > > NOTICE should be updated for 2017.
> > >
> >
> > Will update this.
> >
> >
> > > I'm not sure why the NOTICE includes Hadoop references.  Do you still
> > ship
> > > modified versions?
> > >
> >
> > Ah, here is the discussion about the NOTICE includes Hadoop references.
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201701.mbox/browser
> >
> > I think we are following what other projects were doing when we are
> making
> > a similar code change. And there is a JIRA to follow up after this
> release.
> > Do you see a major concern here? If so, we will address it in the new RC.
> >
> >
> Yes.  the incubation policies are pretty clear -
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> Missing disclaimer is all I see as an issue.  I believe if you fix this,
> you should be good.
>
>
> > Thanks,
> >
> > Sijie
> >
> >
> >
> > >
> > > On Thu, Jan 26, 2017 at 1:36 AM Sijie Guo <si...@apache.org> wrote:
> > >
> > > >   Hi everyone,
> > > >
> > > > Please review and vote on the release candidate #2 for the Apache
> > > > DistributedLog version 0.4.0-incubating, as follows:
> > > > [ ] +1, Approve the release
> > > > [ ] -1, Do not approve the release (please provide specific
> > comments)
> > > >
> > > >
> > > > The complete staging area is available for your review, which
> > > includes:
> > > > * JIRA release notes [1],
> > > > * the official Apache source release to be deployed to
> > > dist.apache.org
> > > > [2],
> > > > * all artifacts to be deployed to the Maven Central Repository
> > > [3][4],
> > > > * source code tag "v0.4.0-RC0" [4],
> > > > * code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> > > > "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
> > > > * website pull request listing the release [7] and publishing the
> > API
> > > > reference manual.
> > > >
> > > > The Apache DistributedLog community has unanimously approved this
> > > > release [8].
> > > >
> > > > As customary, the vote will be open for at least 72 hours. It is
> > > > adopted by
> > > > a majority approval with at least three PMC affirmative votes. If
> > > > approved,
> > > > we will proceed with the release.
> > > >
> > > > Thanks!
> > > >
> > > > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
> > > > rojectId=12320620=12337980
> > > > [2] https://dist.apache.org/repos/dist/dev/incubator/
> > > distributedlog/0.4.0-
> > > > incubating-RC2/
> > > > <
> > https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> > > incubating-RC2/>
> > > > [3] https://repository.apache.org/content/repositories/
> > > > orgapachedistributedlog-1003/
> > > > [4] https://repository.apache.org/content/repositories/
> > > > orgapachedistributedlog-1004/
> > > > [5] https://github.com/apache/incubator-distributedlog/tree/
> > > > v0.4.0-incubating-RC1_2.11
> > > > [6] https://github.com/apache/incubator-distributedlog/tree/
> > > > v0.4.0-incubating-RC1_2.10
> > > > [7] https://github.com/apache/incubator-distributedlog/pull/109
> > > > [8]
> > > >
> > > > http://mail-archives.apache.org/mod_mbox/incubator-
> > > distributedlog-dev/201701.mbox/%3CCAO2yDyYwQgg%3DSRuBdxTPC%
> > > 3DT3bkZO4O0EULwq9tUB_Uno01XW7A%40mail.gmail.com%3E
> > > >
> > >
> >
>

Re: [VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

On Thu, Jan 26, 2017 at 6:06 AM, John D. Ament <johndam...@apache.org>
wrote:

> Its not clear if you intended this to be the IPMC vote or the dev vote.
>

Sorry. it is my first time doing incubator project release. If I made
something wrong, please let me know.

This is vote is intended to for the IPMC vote.


>
> -1 Since the release does not include the DISCLAIMER file and README does
> not include the DISCLAIMER text (either would be fine per policy, but
> generally we look for DISCLAIMER).
>

Gotcha. We will try to add this.


>
> There were no binaries in the source.


The source package only includes source codes. The binaries are shipped as
two separated packages, one is service package, the other one is benchmark
package. Is there a policy about packaging?


> NOTICE should be updated for 2017.
>

Will update this.


> I'm not sure why the NOTICE includes Hadoop references.  Do you still ship
> modified versions?
>

Ah, here is the discussion about the NOTICE includes Hadoop references.
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201701.mbox/browser

I think we are following what other projects were doing when we are making
a similar code change. And there is a JIRA to follow up after this release.
Do you see a major concern here? If so, we will address it in the new RC.

Thanks,

Sijie



>
> On Thu, Jan 26, 2017 at 1:36 AM Sijie Guo <si...@apache.org> wrote:
>
> >   Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the Apache
> > DistributedLog version 0.4.0-incubating, as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> >
> > The complete staging area is available for your review, which
> includes:
> > * JIRA release notes [1],
> > * the official Apache source release to be deployed to
> dist.apache.org
> > [2],
> > * all artifacts to be deployed to the Maven Central Repository
> [3][4],
> > * source code tag "v0.4.0-RC0" [4],
> > * code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> > "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
> > * website pull request listing the release [7] and publishing the API
> > reference manual.
> >
> > The Apache DistributedLog community has unanimously approved this
> > release [8].
> >
> > As customary, the vote will be open for at least 72 hours. It is
> > adopted by
> > a majority approval with at least three PMC affirmative votes. If
> > approved,
> > we will proceed with the release.
> >
> > Thanks!
> >
> > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
> > rojectId=12320620=12337980
> > [2] https://dist.apache.org/repos/dist/dev/incubator/
> distributedlog/0.4.0-
> > incubating-RC2/
> > <https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating-RC2/>
> > [3] https://repository.apache.org/content/repositories/
> > orgapachedistributedlog-1003/
> > [4] https://repository.apache.org/content/repositories/
> > orgapachedistributedlog-1004/
> > [5] https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC1_2.11
> > [6] https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC1_2.10
> > [7] https://github.com/apache/incubator-distributedlog/pull/109
> > [8]
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/201701.mbox/%3CCAO2yDyYwQgg%3DSRuBdxTPC%
> 3DT3bkZO4O0EULwq9tUB_Uno01XW7A%40mail.gmail.com%3E
> >
>

[VOTE] Apache DistributedLog release 0.4.0-incubating

[Sijie Guo]

  Hi everyone,

Please review and vote on the release candidate #2 for the Apache
DistributedLog version 0.4.0-incubating, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
[2],
* all artifacts to be deployed to the Maven Central Repository [3][4],
* source code tag "v0.4.0-RC0" [4],
* code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
"v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
* website pull request listing the release [7] and publishing the API
reference manual.

The Apache DistributedLog community has unanimously approved this
release [8].

As customary, the vote will be open for at least 72 hours. It is
adopted by
a majority approval with at least three PMC affirmative votes. If
approved,
we will proceed with the release.

Thanks!

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
rojectId=12320620=12337980
[2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
incubating-RC2/
[3] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1003/
[4] https://repository.apache.org/content/repositories/
orgapachedistributedlog-1004/
[5] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC1_2.11
[6] https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC1_2.10
[7] https://github.com/apache/incubator-distributedlog/pull/109
[8]
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201701.mbox/%3CCAO2yDyYwQgg%3DSRuBdxTPC%3DT3bkZO4O0EULwq9tUB_Uno01XW7A%40mail.gmail.com%3E

Re: [RESULT] [VOTE] Release 0.4.0, release candidate #2

[Sijie Guo]

Not yet. Unfortunately I think I need to run another vote in
gene...@incubator.apache.org since we are still in incubation.

I will start a vote thread in general@ today.

- Sijie

On Wed, Jan 25, 2017 at 12:21 AM, Asko Kauppi <asko.kau...@zalando.fi>
wrote:

> Is there a URL / newsfeed that I could share about the release with my
> organization?
>
> Asko Kauppi
> Zalando Tech Helsinki
>
> For Zalando internal messages, I prefer HipChat
>
> > On 25 Jan 2017, at 8.24, Sijie Guo <si...@apache.org> wrote:
> >
> > I am happy to announce that we have unanimously approved this release.
> >
> > There are 8 +1 votes and no disapproving votes.
> >
> > Thanks everyone!
> >
> > - Sijie
> >
> >
> >
> >
> >
> > On Tue, Jan 10, 2017 at 11:56 PM, Sijie Guo <si...@apache.org> wrote:
> >
> >> Hi all,
> >>
> >> Please review and vote on the release candidate #2 for the version
> 0.4.0,
> >> as follows:
> >>
> >> [ ] +1, Approve the release
> >> [ ] -1, Do not approve the release (please provide specific comments)
> >>
> >> The complete staging area is available for your review, which includes:
> >>
> >>* JIRA release notes [1],
> >>* the official Apache source release to be deployed to
> dist.apache.org
> >> [2],
> >>* all artifacts to be deployed to the Maven Central Repository
> [3][4],
> >>* source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> >> "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
> >>* website pull request listing the release [7] and publishing the API
> >> reference manual.
> >>
> >> A simple instruction for validation the source and binary packages.
> >>
> >> - source package: building the package with "*mvn clean apache-rat:check
> >> package findbugs:check -DskipTests*"
> >>
> >> The vote will be open for at least 72 hours. It is adopted by majority
> >> approval, with at least 3 PPMC affirmative votes.
> >>
> >> Thanks,
> >> Sijie
> >>
> >> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
> >> rojectId=12320620=12337980
> >> [2] https://dist.apache.org/repos/dist/dev/incubator/
> distributedlog/0.4.0-
> >> incubating-RC2/
> >> [3] https://repository.apache.org/content/repositories/
> >> orgapachedistributedlog-1003/
> >> [4] https://repository.apache.org/content/repositories/
> >> orgapachedistributedlog-1004/
> >> [5] https://github.com/apache/incubator-distributedlog/tree/
> >> v0.4.0-incubating-RC1_2.11
> >> [6] https://github.com/apache/incubator-distributedlog/tree/
> >> v0.4.0-incubating-RC1_2.10
> >> [7] https://github.com/apache/incubator-distributedlog/pull/109
> >>
>
>

[RESULT] [VOTE] Release 0.4.0, release candidate #2

[Sijie Guo]

I am happy to announce that we have unanimously approved this release.

There are 8 +1 votes and no disapproving votes.

Thanks everyone!

- Sijie





On Tue, Jan 10, 2017 at 11:56 PM, Sijie Guo <si...@apache.org> wrote:

> Hi all,
>
> Please review and vote on the release candidate #2 for the version 0.4.0,
> as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
>  [2],
> * all artifacts to be deployed to the Maven Central Repository [3][4],
> * source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
> * website pull request listing the release [7] and publishing the API
> reference manual.
>
> A simple instruction for validation the source and binary packages.
>
> - source package: building the package with "*mvn clean apache-rat:check
> package findbugs:check -DskipTests*"
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PPMC affirmative votes.
>
> Thanks,
> Sijie
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?p
> rojectId=12320620=12337980
> [2] https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating-RC2/
> [3] https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1003/
> [4] https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1004/
> [5] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC1_2.11
> [6] https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC1_2.10
> [7] https://github.com/apache/incubator-distributedlog/pull/109
>

Re: [VOTE] Release 0.4.0, release candidate #2

[Sijie Guo]

On Jan 17, 2017 2:58 PM, "Flavio Junqueira" <f...@apache.org> wrote:

+1, I have checked the following:

- Built both 2.10 and 2.11 from source (skipped tests)
- Checksums and signatures
- NOTICE and LICENSE
- Rat

Questions:
1- I'm wondering if the text about Hadoop in NOTICE is necessary. How did
you guys end up including it?


Ah, I need to check that. Can't remember why it was brought in right now.

2- The tgz bundles do not include any jar directly, so there is no real
concern about bundling the bits from other projects that could require more
sections in the NOTICE file, is it right?


I am clear about this part. Any principles to follow in Apache?


-Flavio

> On 17 Jan 2017, at 17:12, Leigh Stewart <lstew...@twitter.com.INVALID>
wrote:
>
> +1
>
> On Mon, Jan 16, 2017 at 8:13 AM, Jon Derrick <jonathan.derri...@gmail.com>
> wrote:
>
>> +1
>>
>> LGTM. compiled the source packages and ran dbench. the license files look
>> good.
>>
>> - jd
>>
>> On Tue, Jan 10, 2017 at 11:56 PM, Sijie Guo <si...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> Please review and vote on the release candidate #2 for the version
0.4.0,
>>> as follows:
>>>
>>> [ ] +1, Approve the release
>>> [ ] -1, Do not approve the release (please provide specific comments)
>>>
>>> The complete staging area is available for your review, which includes:
>>>
>>>* JIRA release notes [1],
>>>* the official Apache source release to be deployed to
>> dist.apache.org
>>> [2],
>>>* all artifacts to be deployed to the Maven Central Repository
>> [3][4],
>>>* source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
>>> "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
>>>* website pull request listing the release [7] and publishing the API
>>> reference manual.
>>>
>>> A simple instruction for validation the source and binary packages.
>>>
>>> - source package: building the package with "*mvn clean apache-rat:check
>>> package findbugs:check -DskipTests*"
>>>
>>> The vote will be open for at least 72 hours. It is adopted by majority
>>> approval, with at least 3 PPMC affirmative votes.
>>>
>>> Thanks,
>>> Sijie
>>>
>>> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12320620=12337980
>>> [2]
>>> https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
>>> incubating-RC2/
>>> [3]
>>> https://repository.apache.org/content/repositories/
>>> orgapachedistributedlog-1003/
>>> [4]
>>> https://repository.apache.org/content/repositories/
>>> orgapachedistributedlog-1004/
>>> [5]
>>> https://github.com/apache/incubator-distributedlog/tree/
>>> v0.4.0-incubating-RC1_2.11
>>> [6]
>>> https://github.com/apache/incubator-distributedlog/tree/
>>> v0.4.0-incubating-RC1_2.10
>>> [7] https://github.com/apache/incubator-distributedlog/pull/109
>>>
>>
>>
>>
>> --
>> - jderrick
>>

Re: [VOTE] Release 0.4.0, release candidate #2

[Sijie Guo]

On Jan 12, 2017 6:59 PM, "liang xie" <xieliang...@gmail.com> wrote:

I am not good at here, per my knowledge, we should add the bindings
into benchmark package, at least in next release.


Agree. Do you mind creating a Jira for this?


On Fri, Jan 13, 2017 at 12:42 AM, Sijie Guo <si...@apache.org> wrote:
> I think we turned the log4j binding scope to test sometime ago. The
thought
> was not to conflict bindings when DL is used as a library in other
projects.
>
> For binaries, it seems worth brining the bindings in. What does other
> projects do for slf4j bindings?
>
> Sijie
>
> On Jan 12, 2017 12:58 AM, "liang xie" <xieliang...@gmail.com> wrote:
>
> Verified source package with provided command and looks good to me.
>
> Seems missing slf4j-log4j12-1.6.4.jar in benchmark lib directory ?
> since i saw this error if execute "dbench write":
>
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
> further details.
>
>
>
> On Wed, Jan 11, 2017 at 3:56 PM, Sijie Guo <si...@apache.org> wrote:
>> Hi all,
>>
>> Please review and vote on the release candidate #2 for the version 0.4.0,
>> as follows:
>>
>> [ ] +1, Approve the release
>> [ ] -1, Do not approve the release (please provide specific comments)
>>
>> The complete staging area is available for your review, which includes:
>>
>> * JIRA release notes [1],
>> * the official Apache source release to be deployed to
dist.apache.org
>>  [2],
>> * all artifacts to be deployed to the Maven Central Repository
[3][4],
>> * source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
>> "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
>> * website pull request listing the release [7] and publishing the API
>> reference manual.
>>
>> A simple instruction for validation the source and binary packages.
>>
>> - source package: building the package with "*mvn clean apache-rat:check
>> package findbugs:check -DskipTests*"
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PPMC affirmative votes.
>>
>> Thanks,
>> Sijie
>>
>> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12320620=12337980
>> [2]
>> https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating-RC2/
>> [3]
>> https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1003/
>> [4]
>> https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1004/
>> [5]
>> https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC1_2.11
>> [6]
>> https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC1_2.10
>> [7] https://github.com/apache/incubator-distributedlog/pull/109

Re: [VOTE] Release 0.4.0, release candidate #2

[Sijie Guo]

I think we turned the log4j binding scope to test sometime ago. The thought
was not to conflict bindings when DL is used as a library in other projects.

For binaries, it seems worth brining the bindings in. What does other
projects do for slf4j bindings?

Sijie

On Jan 12, 2017 12:58 AM, "liang xie" <xieliang...@gmail.com> wrote:

Verified source package with provided command and looks good to me.

Seems missing slf4j-log4j12-1.6.4.jar in benchmark lib directory ?
since i saw this error if execute "dbench write":

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
further details.



On Wed, Jan 11, 2017 at 3:56 PM, Sijie Guo <si...@apache.org> wrote:
> Hi all,
>
> Please review and vote on the release candidate #2 for the version 0.4.0,
> as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
>  [2],
> * all artifacts to be deployed to the Maven Central Repository [3][4],
> * source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
> * website pull request listing the release [7] and publishing the API
> reference manual.
>
> A simple instruction for validation the source and binary packages.
>
> - source package: building the package with "*mvn clean apache-rat:check
> package findbugs:check -DskipTests*"
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PPMC affirmative votes.
>
> Thanks,
> Sijie
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320620=12337980
> [2]
> https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
incubating-RC2/
> [3]
> https://repository.apache.org/content/repositories/
orgapachedistributedlog-1003/
> [4]
> https://repository.apache.org/content/repositories/
orgapachedistributedlog-1004/
> [5]
> https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC1_2.11
> [6]
> https://github.com/apache/incubator-distributedlog/tree/
v0.4.0-incubating-RC1_2.10
> [7] https://github.com/apache/incubator-distributedlog/pull/109

Re: [VOTE] Release 0.4.0, release candidate #1

[Sijie Guo]

Yeah, currently some of the tests are time dependent. So they failed
sometimes when the machine is slow. There were efforts on improving this
and will also do this in next release.

Sijie

On Jan 12, 2017 3:32 AM, "Flavio Junqueira" <f...@apache.org> wrote:

> Ok, so I've seen the following test cases showing errors:
>
> TestBKDistributedLogManager.testNumberOfTransactionsWithIn
> progressAtEnd:325
> TestAsyncReaderLock.testReaderLockDlmClosed » Cancellation
>
> They don't seem to fail consistently for me, though.
>
> -Flavio
>
> > On 10 Jan 2017, at 18:10, Sijie Guo <si...@apache.org> wrote:
> >
> > Liang had a pull request for the assembly issue. Going to cancel this
> vote
> > and produce a new RC.
> >
> > Flavio, what are the tests failed in your case?
> >
> > Sijie
> >
> > On Jan 10, 2017 9:10 AM, "Flavio Junqueira" <f...@apache.org  f...@apache.org>> wrote:
> >
> > Yeah, I can't build because of the same issue:
> >
> >[ERROR] Failed to execute goal org.apache.maven.plugins:
> > maven-assembly-plugin:2.2.1:single (default) on project
> > distributedlog-service: Failed to create assembly: Error adding file to
> >archive: distributedlog-0.4.0-incubating/distributedlog-
> service/../README.md
> > isn't a file. -> [Help 1]
> >
> > The command I ran is:
> >
> >   mvn clean apache-rat:check package findbugs:check -DskipTests
> >
> > I also tried other commands, and they all seem to fail on tests.
> >
> > -Flavio
> >
> >> On 10 Jan 2017, at 07:24, Xi Liu <xi.liu@gmail.com> wrote:
> >>
> >> On Mon, Jan 9, 2017 at 8:00 PM, liang xie <xieliang...@gmail.com
> <mailto:xieliang...@gmail.com>  > xieliang...@gmail.com>> wrote:
> >>
> >>> Glad to see 0.4 will be release soon :)
> >>> I could not find tutorials package from link[2], it should be released
> >>> as well, please correct me if i am wrong.
> >>> I can pass this command with current git master code: "mvn clean
> >>> apache-rat:check package findbugs:check -DskipTests", but failed with
> >>> from distributedlog-0.4.0-incubating-src.tar.gz which downloaded from
> >>> dist.apache.org, the error msg:
> >>>
> >>> [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
> >>> on project distributedlog-service: Failed to create assembly: Error
> >>> adding file to archive:
> >>> /tmp/distributedlog-0.4.0-incubating/distributedlog-
> service/../README.md
> >>> isn't a file. -> [Help 1]
> >>>
> >>
> >> I also saw this issue.
> >>
> >>
> >>>
> >>> And none of you saw this : DL-181, it can be reproduced on my local
> >>> box always w/o patched,  weird...
> >>>
> >>> On Mon, Jan 9, 2017 at 12:04 PM, Sijie Guo <si...@apache.org> wrote:
> >>>> Hi all,
> >>>>
> >>>> Please review and vote on the release candidate #1 for the version
> > 0.4.0,
> >>>> as follows:
> >>>>
> >>>> [ ] +1, Approve the release
> >>>> [ ] -1, Do not approve the release (please provide specific comments)
> >>>>
> >>>> The complete staging area is available for your review, which
> includes:
> >>>>
> >>>>   * JIRA release notes [1],
> >>>>   * the official Apache source release to be deployed to
> >>> dist.apache.org
> >>>> [2],
> >>>>   * all artifacts to be deployed to the Maven Central Repository [3],
> >>>>   * source code tag "v0.4.0-RC1" [4],
> >>>>   * website pull request listing the release [5] and publishing the
> API
> >>>> reference manual.
> >>>>
> >>>> A simple instruction for validation the source and binary packages.
> >>>>
> >>>> - source package: run "*./scripts/integration/smoketest.sh*" after
> >>> building
> >>>> the package with "*mvn clean apache-rat:check package findbugs:check
> >>>> -DskipTests*"
> >>>>
> >>>> The vote will be open for at least 72 hours. It is adopted by majority
> >>>> approval, with at least 3 PPMC affirmative votes.
> >>>>
> >>>> Thanks,
> >>>> Sijie
> >>>>
> >>>> [1]
> >>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >>> projectId=12320620=12337980
> >>>> [2]
> >>>> https://dist.apache.org/repos/dist/dev/incubator/
> distributedlog/0.4.0-
> >>> incubating/
> >>>> [3]
> >>>> https://repository.apache.org/content/repositories/
> >>> orgapachedistributedlog-1001/
> >>>> [4]
> >>>> https://github.com/apache/incubator-distributedlog/tree/
> >>> v0.4.0-incubating-RC1
> >>>> [5] https://github.com/apache/incubator-distributedlog/pull/109
>
>

[VOTE] Release 0.4.0, release candidate #2

[Sijie Guo]

Hi all,

Please review and vote on the release candidate #2 for the version 0.4.0,
as follows:

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which includes:

* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
 [2],
* all artifacts to be deployed to the Maven Central Repository [3][4],
* source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
"v0.4.0-incubating-RC1_2.10" (for scala 2.10) [5][6],
* website pull request listing the release [7] and publishing the API
reference manual.

A simple instruction for validation the source and binary packages.

- source package: building the package with "*mvn clean apache-rat:check
package findbugs:check -DskipTests*"

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PPMC affirmative votes.

Thanks,
Sijie

[1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12320620=12337980
[2]
https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-incubating-RC2/
[3]
https://repository.apache.org/content/repositories/orgapachedistributedlog-1003/
[4]
https://repository.apache.org/content/repositories/orgapachedistributedlog-1004/
[5]
https://github.com/apache/incubator-distributedlog/tree/v0.4.0-incubating-RC1_2.11
[6]
https://github.com/apache/incubator-distributedlog/tree/v0.4.0-incubating-RC1_2.10
[7] https://github.com/apache/incubator-distributedlog/pull/109

Re: [VOTE] Release 0.4.0, release candidate #1

[Sijie Guo]

Liang had a pull request for the assembly issue. Going to cancel this vote
and produce a new RC.

Flavio, what are the tests failed in your case?

Sijie

On Jan 10, 2017 9:10 AM, "Flavio Junqueira" <f...@apache.org> wrote:

Yeah, I can't build because of the same issue:

[ERROR] Failed to execute goal org.apache.maven.plugins:
maven-assembly-plugin:2.2.1:single (default) on project
distributedlog-service: Failed to create assembly: Error adding file to
archive: distributedlog-0.4.0-incubating/distributedlog-service/../README.md
isn't a file. -> [Help 1]

The command I ran is:

   mvn clean apache-rat:check package findbugs:check -DskipTests

I also tried other commands, and they all seem to fail on tests.

-Flavio

> On 10 Jan 2017, at 07:24, Xi Liu <xi.liu@gmail.com> wrote:
>
> On Mon, Jan 9, 2017 at 8:00 PM, liang xie <xieliang...@gmail.com > wrote:
>
>> Glad to see 0.4 will be release soon :)
>> I could not find tutorials package from link[2], it should be released
>> as well, please correct me if i am wrong.
>> I can pass this command with current git master code: "mvn clean
>> apache-rat:check package findbugs:check -DskipTests", but failed with
>> from distributedlog-0.4.0-incubating-src.tar.gz which downloaded from
>> dist.apache.org, the error msg:
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
>> on project distributedlog-service: Failed to create assembly: Error
>> adding file to archive:
>> /tmp/distributedlog-0.4.0-incubating/distributedlog-service/../README.md
>> isn't a file. -> [Help 1]
>>
>
> I also saw this issue.
>
>
>>
>> And none of you saw this : DL-181, it can be reproduced on my local
>> box always w/o patched,  weird...
>>
>> On Mon, Jan 9, 2017 at 12:04 PM, Sijie Guo <si...@apache.org> wrote:
>>> Hi all,
>>>
>>> Please review and vote on the release candidate #1 for the version
0.4.0,
>>> as follows:
>>>
>>> [ ] +1, Approve the release
>>> [ ] -1, Do not approve the release (please provide specific comments)
>>>
>>> The complete staging area is available for your review, which includes:
>>>
>>>* JIRA release notes [1],
>>>* the official Apache source release to be deployed to
>> dist.apache.org
>>> [2],
>>>* all artifacts to be deployed to the Maven Central Repository [3],
>>>* source code tag "v0.4.0-RC1" [4],
>>>* website pull request listing the release [5] and publishing the API
>>> reference manual.
>>>
>>> A simple instruction for validation the source and binary packages.
>>>
>>> - source package: run "*./scripts/integration/smoketest.sh*" after
>> building
>>> the package with "*mvn clean apache-rat:check package findbugs:check
>>> -DskipTests*"
>>>
>>> The vote will be open for at least 72 hours. It is adopted by majority
>>> approval, with at least 3 PPMC affirmative votes.
>>>
>>> Thanks,
>>> Sijie
>>>
>>> [1]
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12320620=12337980
>>> [2]
>>> https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
>> incubating/
>>> [3]
>>> https://repository.apache.org/content/repositories/
>> orgapachedistributedlog-1001/
>>> [4]
>>> https://github.com/apache/incubator-distributedlog/tree/
>> v0.4.0-incubating-RC1
>>> [5] https://github.com/apache/incubator-distributedlog/pull/109

Re: [VOTE] Release 0.4.0, release candidate #1

[Sijie Guo]

On Mon, Jan 9, 2017 at 5:32 PM, Sijie Guo <si...@apache.org> wrote:

> Thank you for your suggestion, Khurrum. Comment inline. I'd like to
> collect more feedbacks and then cut another RC.
>
>
> On Mon, Jan 9, 2017 at 11:43 AM, Khurrum Nasim <khurrumnas...@gmail.com>
> wrote:
>
>> Thanks Sijie for working on this. A couple of comments:
>>
>> - do we need to publish artifacts for both scala 2.10 and 2.11 (probably
>> also 2.12)? as DL uses some scala libraries as the dependencies.
>>
>
> Ah, ah, good catch. We need to publish both 2.10 and 2.11.
>
>
>> - the source jar is also missing. do we need it? it is usually useful to
>> have a source jar so that people who uses any IDE tool can easily navigate
>> to the source code.
>>
>
> It is a good suggestion. We don't have source maven plugin configured. We
> need to configure that.
>

Create https://issues.apache.org/jira/browse/DL-183 for generating the
source jar.

>
>
>
>
>>
>> - KN
>>
>> On Sun, Jan 8, 2017 at 8:04 PM, Sijie Guo <si...@apache.org> wrote:
>>
>> > Hi all,
>> >
>> > Please review and vote on the release candidate #1 for the version
>> 0.4.0,
>> > as follows:
>> >
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific comments)
>> >
>> > The complete staging area is available for your review, which includes:
>> >
>> > * JIRA release notes [1],
>> > * the official Apache source release to be deployed to
>> dist.apache.org
>> > [2],
>> > * all artifacts to be deployed to the Maven Central Repository [3],
>> > * source code tag "v0.4.0-RC1" [4],
>> > * website pull request listing the release [5] and publishing the
>> API
>> > reference manual.
>> >
>> > A simple instruction for validation the source and binary packages.
>> >
>> > - source package: run "*./scripts/integration/smoketest.sh*" after
>> > building
>> > the package with "*mvn clean apache-rat:check package findbugs:check
>> > -DskipTests*"
>> >
>> > The vote will be open for at least 72 hours. It is adopted by majority
>> > approval, with at least 3 PPMC affirmative votes.
>> >
>> > Thanks,
>> > Sijie
>> >
>> > [1]
>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> > projectId=12320620=12337980
>> > [2]
>> > https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
>> > incubating/
>> > [3]
>> > https://repository.apache.org/content/repositories/
>> > orgapachedistributedlog-1001/
>> > [4]
>> > https://github.com/apache/incubator-distributedlog/tree/
>> > v0.4.0-incubating-RC1
>> > [5] https://github.com/apache/incubator-distributedlog/pull/109
>> >
>>
>
>

Re: [VOTE] Release 0.4.0, release candidate #1

[Sijie Guo]

On Mon, Jan 9, 2017 at 8:00 PM, liang xie <xieliang...@gmail.com> wrote:

> Glad to see 0.4 will be release soon :)
> I could not find tutorials package from link[2], it should be released
> as well, please correct me if i am wrong.
>

I was thinking it might be necessary to release tutorials as a separated
bin package. since they are tutorials, people can download the src package
and build from there. A service binary package for deployment and a
benchmark binary package for benchmarking are probably enough.

But I am open to release tutorials as a separated binary package. Not sure
how does other apache project do. I'd like to see other people's opinions.


> I can pass this command with current git master code: "mvn clean
> apache-rat:check package findbugs:check -DskipTests", but failed with
> from distributedlog-0.4.0-incubating-src.tar.gz which downloaded from
> dist.apache.org, the error msg:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
> on project distributedlog-service: Failed to create assembly: Error
> adding file to archive:
> /tmp/distributedlog-0.4.0-incubating/distributedlog-service/../README.md
> isn't a file. -> [Help 1]
>
>
Ah, nice catch.

I think the src/assemble/bin.xml and src/assemble/src.xml have inconsistent
settings.

the bin.xml is looking for README.md


  ../README.md
  /
  644


however, the src.xml doesn't include README.md in the source package.

  
**/README



> And none of you saw this : DL-181, it can be reproduced on my local
> box always w/o patched,  weird...
>
>
I think I fixed that before. It is probably not pushed to master but in the
release branch. I merged your change to both master and
release-0.4.0-incubating branch. so it should be okay now.


> On Mon, Jan 9, 2017 at 12:04 PM, Sijie Guo <si...@apache.org> wrote:
> > Hi all,
> >
> > Please review and vote on the release candidate #1 for the version 0.4.0,
> > as follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staging area is available for your review, which includes:
> >
> > * JIRA release notes [1],
> > * the official Apache source release to be deployed to
> dist.apache.org
> > [2],
> > * all artifacts to be deployed to the Maven Central Repository [3],
> > * source code tag "v0.4.0-RC1" [4],
> > * website pull request listing the release [5] and publishing the API
> > reference manual.
> >
> > A simple instruction for validation the source and binary packages.
> >
> > - source package: run "*./scripts/integration/smoketest.sh*" after
> building
> > the package with "*mvn clean apache-rat:check package findbugs:check
> > -DskipTests*"
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PPMC affirmative votes.
> >
> > Thanks,
> > Sijie
> >
> > [1]
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320620=12337980
> > [2]
> > https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating/
> > [3]
> > https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1001/
> > [4]
> > https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC1
> > [5] https://github.com/apache/incubator-distributedlog/pull/109
>

Re: [VOTE] Release 0.4.0, release candidate #1

[Sijie Guo]

On Mon, Jan 9, 2017 at 11:07 PM, Sijie Guo <si...@apache.org> wrote:

>
>
> On Mon, Jan 9, 2017 at 8:00 PM, liang xie <xieliang...@gmail.com> wrote:
>
>> Glad to see 0.4 will be release soon :)
>> I could not find tutorials package from link[2], it should be released
>> as well, please correct me if i am wrong.
>>
>
> I was thinking it might be necessary to release tutorials as a separated
> bin package. since they are tutorials, people can download the src package
> and build from there. A service binary package for deployment and a
> benchmark binary package for benchmarking are probably enough.
>
> But I am open to release tutorials as a separated binary package. Not sure
> how does other apache project do. I'd like to see other people's opinions.
>
>
>> I can pass this command with current git master code: "mvn clean
>> apache-rat:check package findbugs:check -DskipTests", but failed with
>> from distributedlog-0.4.0-incubating-src.tar.gz which downloaded from
>> dist.apache.org, the error msg:
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
>> on project distributedlog-service: Failed to create assembly: Error
>> adding file to archive:
>> /tmp/distributedlog-0.4.0-incubating/distributedlog-service/../README.md
>> isn't a file. -> [Help 1]
>>
>>
> Ah, nice catch.
>
> I think the src/assemble/bin.xml and src/assemble/src.xml have
> inconsistent settings.
>
> the bin.xml is looking for README.md
>
> 
>   ../README.md
>   /
>   644
> 
>
> however, the src.xml doesn't include README.md in the source package.
>
>   
> **/README
>

Created https://issues.apache.org/jira/browse/DL-182 .

Liang, do you want to help fix it?


>
>
>
>> And none of you saw this : DL-181, it can be reproduced on my local
>> box always w/o patched,  weird...
>>
>>
> I think I fixed that before. It is probably not pushed to master but in
> the release branch. I merged your change to both master and
> release-0.4.0-incubating branch. so it should be okay now.
>
>
>> On Mon, Jan 9, 2017 at 12:04 PM, Sijie Guo <si...@apache.org> wrote:
>> > Hi all,
>> >
>> > Please review and vote on the release candidate #1 for the version
>> 0.4.0,
>> > as follows:
>> >
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific comments)
>> >
>> > The complete staging area is available for your review, which includes:
>> >
>> > * JIRA release notes [1],
>> > * the official Apache source release to be deployed to
>> dist.apache.org
>> > [2],
>> > * all artifacts to be deployed to the Maven Central Repository [3],
>> > * source code tag "v0.4.0-RC1" [4],
>> > * website pull request listing the release [5] and publishing the
>> API
>> > reference manual.
>> >
>> > A simple instruction for validation the source and binary packages.
>> >
>> > - source package: run "*./scripts/integration/smoketest.sh*" after
>> building
>> > the package with "*mvn clean apache-rat:check package findbugs:check
>> > -DskipTests*"
>> >
>> > The vote will be open for at least 72 hours. It is adopted by majority
>> > approval, with at least 3 PPMC affirmative votes.
>> >
>> > Thanks,
>> > Sijie
>> >
>> > [1]
>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
>> ctId=12320620=12337980
>> > [2]
>> > https://dist.apache.org/repos/dist/dev/incubator/distributed
>> log/0.4.0-incubating/
>> > [3]
>> > https://repository.apache.org/content/repositories/orgapache
>> distributedlog-1001/
>> > [4]
>> > https://github.com/apache/incubator-distributedlog/tree/v0.
>> 4.0-incubating-RC1
>> > [5] https://github.com/apache/incubator-distributedlog/pull/109
>>
>
>

Re: [VOTE] Release 0.4.0, release candidate #1

[Sijie Guo]

yeah, you need a clean repo before running apache-rat:check in master.

On Mon, Jan 9, 2017 at 9:01 PM, liang xie <xieliang...@gmail.com> wrote:

> Master issue gone now after checking rat.txt and removing the log
> files generated by privious tests.
>
> On Tue, Jan 10, 2017 at 12:05 PM, liang xie <xieliang...@gmail.com> wrote:
> > oops, "mvn clean apache-rat:check package findbugs:check -DskipTests"
> > failed at the latest master code with another diff err msg:
> > Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check
> > (default-cli) on project distributedlog-service: Too many unapproved
> > licenses: 5
> >
> >
> > On Tue, Jan 10, 2017 at 12:00 PM, liang xie <xieliang...@gmail.com>
> wrote:
> >> Glad to see 0.4 will be release soon :)
> >> I could not find tutorials package from link[2], it should be released
> >> as well, please correct me if i am wrong.
> >> I can pass this command with current git master code: "mvn clean
> >> apache-rat:check package findbugs:check -DskipTests", but failed with
> >> from distributedlog-0.4.0-incubating-src.tar.gz which downloaded from
> >> dist.apache.org, the error msg:
> >>
> >> [ERROR] Failed to execute goal
> >> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
> >> on project distributedlog-service: Failed to create assembly: Error
> >> adding file to archive:
> >> /tmp/distributedlog-0.4.0-incubating/distributedlog-
> service/../README.md
> >> isn't a file. -> [Help 1]
> >>
> >> And none of you saw this : DL-181, it can be reproduced on my local
> >> box always w/o patched,  weird...
> >>
> >> On Mon, Jan 9, 2017 at 12:04 PM, Sijie Guo <si...@apache.org> wrote:
> >>> Hi all,
> >>>
> >>> Please review and vote on the release candidate #1 for the version
> 0.4.0,
> >>> as follows:
> >>>
> >>> [ ] +1, Approve the release
> >>> [ ] -1, Do not approve the release (please provide specific comments)
> >>>
> >>> The complete staging area is available for your review, which includes:
> >>>
> >>> * JIRA release notes [1],
> >>> * the official Apache source release to be deployed to
> dist.apache.org
> >>> [2],
> >>> * all artifacts to be deployed to the Maven Central Repository [3],
> >>> * source code tag "v0.4.0-RC1" [4],
> >>> * website pull request listing the release [5] and publishing the
> API
> >>> reference manual.
> >>>
> >>> A simple instruction for validation the source and binary packages.
> >>>
> >>> - source package: run "*./scripts/integration/smoketest.sh*" after
> building
> >>> the package with "*mvn clean apache-rat:check package findbugs:check
> >>> -DskipTests*"
> >>>
> >>> The vote will be open for at least 72 hours. It is adopted by majority
> >>> approval, with at least 3 PPMC affirmative votes.
> >>>
> >>> Thanks,
> >>> Sijie
> >>>
> >>> [1]
> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320620=12337980
> >>> [2]
> >>> https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating/
> >>> [3]
> >>> https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1001/
> >>> [4]
> >>> https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC1
> >>> [5] https://github.com/apache/incubator-distributedlog/pull/109
>

Re: [VOTE] Release 0.4.0, release candidate #1

[Sijie Guo]

Thank you for your suggestion, Khurrum. Comment inline. I'd like to collect
more feedbacks and then cut another RC.


On Mon, Jan 9, 2017 at 11:43 AM, Khurrum Nasim <khurrumnas...@gmail.com>
wrote:

> Thanks Sijie for working on this. A couple of comments:
>
> - do we need to publish artifacts for both scala 2.10 and 2.11 (probably
> also 2.12)? as DL uses some scala libraries as the dependencies.
>

Ah, ah, good catch. We need to publish both 2.10 and 2.11.


> - the source jar is also missing. do we need it? it is usually useful to
> have a source jar so that people who uses any IDE tool can easily navigate
> to the source code.
>

It is a good suggestion. We don't have source maven plugin configured. We
need to configure that.




>
> - KN
>
> On Sun, Jan 8, 2017 at 8:04 PM, Sijie Guo <si...@apache.org> wrote:
>
> > Hi all,
> >
> > Please review and vote on the release candidate #1 for the version 0.4.0,
> > as follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staging area is available for your review, which includes:
> >
> > * JIRA release notes [1],
> > * the official Apache source release to be deployed to
> dist.apache.org
> > [2],
> > * all artifacts to be deployed to the Maven Central Repository [3],
> > * source code tag "v0.4.0-RC1" [4],
> > * website pull request listing the release [5] and publishing the API
> > reference manual.
> >
> > A simple instruction for validation the source and binary packages.
> >
> > - source package: run "*./scripts/integration/smoketest.sh*" after
> > building
> > the package with "*mvn clean apache-rat:check package findbugs:check
> > -DskipTests*"
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PPMC affirmative votes.
> >
> > Thanks,
> > Sijie
> >
> > [1]
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12320620=12337980
> > [2]
> > https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> > incubating/
> > [3]
> > https://repository.apache.org/content/repositories/
> > orgapachedistributedlog-1001/
> > [4]
> > https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC1
> > [5] https://github.com/apache/incubator-distributedlog/pull/109
> >
>

[VOTE] Release 0.4.0, release candidate #1

[Sijie Guo]

Hi all,

Please review and vote on the release candidate #1 for the version 0.4.0,
as follows:

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which includes:

* JIRA release notes [1],
* the official Apache source release to be deployed to dist.apache.org
[2],
* all artifacts to be deployed to the Maven Central Repository [3],
* source code tag "v0.4.0-RC1" [4],
* website pull request listing the release [5] and publishing the API
reference manual.

A simple instruction for validation the source and binary packages.

- source package: run "*./scripts/integration/smoketest.sh*" after building
the package with "*mvn clean apache-rat:check package findbugs:check
-DskipTests*"

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PPMC affirmative votes.

Thanks,
Sijie

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320620=12337980
[2]
https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-incubating/
[3]
https://repository.apache.org/content/repositories/orgapachedistributedlog-1001/
[4]
https://github.com/apache/incubator-distributedlog/tree/v0.4.0-incubating-RC1
[5] https://github.com/apache/incubator-distributedlog/pull/109

Re: [Discuss] Transaction Support

[Sijie Guo]

On Thu, Jan 5, 2017 at 10:56 PM, Xi Liu <xi.liu@gmail.com> wrote:

> Asko and Sijie,
>
> Thank you so much for your feedbacks.
>
> We are not targeting at building a general XA transaction coordinator. The
> feature we want is be able to write data to multiple log streams in an
> atomic way.
>

So in other words, that means this feature is 'atomic writes across log
streams', no?


>
> I totally agreed with you about building minimal logic. We also don't want
> to enforce this feature to all the users of DL. Building the TC as a
> separated service sounds clear to me. We will do it follow your suggestion.
>
> I am also replying the comments to you and Leigh on the doc. Hopefully we
> can come to an agreement so that our changes can be accepted.
>
> - Xi
>
> On Wed, Jan 4, 2017 at 1:14 AM, Asko Kauppi <asko.kau...@zalando.fi>
> wrote:
>
> > > Beside that, I have one general question - What is the major goal for
> > this
> > > feature? Are you targeting on building a general XA transaction
> > coordinator
> > > or just for supporting things like `copy-modify-write' style workflow?
> >
> > The use case I would have for transactions - at some level of the stack -
> > is supporting dynamic configurations.
> >
> > If a config changes in e.g. three lines, some of the changes may
> logically
> > belong together. E.g. changing both “host” and “port” (if separate
> > entries). One shouldn’t be able to read a state, even temporarily, that
> has
> > new host but old port.
> >
> > I can do this in the application level - it does not need to be part of
> > the DL protocol.
> >
> >
> > Asko Kauppi
> > Zalando Tech Helsinki
> >
> > > On 4 Jan 2017, at 9.18, Sijie Guo <si...@apache.org> wrote:
> > >
> > > Sorry for late response. I think Leigh and you already had some very
> > > valuable discussions in the doc. I will try to add some of my questions
> > to
> > > the discussion.
> > >
> > > Beside that, I had a discussion with Leigh today about this. first of
> > all,
> > > I think it is very good to add transaction support in distributedlog.
> It
> > is
> > > one of the primitives that would help building distributed service. But
> > we
> > > have a concern about making this system become complicated and
> introduce
> > > operational overhead when it runs in the large scale system on
> > production.
> > > There are two major suggestions that I have for this feature -
> > >
> > > Build the 'minimum' logic in core - I think the minimum logic that need
> > to
> > > be added to the core is -  the special control records (begin, commit
> and
> > > abort) and make the reader be able to detect those special control
> > records
> > > and know what do they mean and how to interrupt with them. Since they
> are
> > > special control records, there is not overhead to other readers that
> > > doesn't require this feature.
> > >
> > > Build the transaction coordinator as a separated proxy service  - I
> think
> > > the major concern that we have is putting more complexities into the
> > 'write
> > > proxy' service. We architected distributedlog in a more
> microservice-like
> > > way - we have the core as the stream store, the proxy for serving write
> > and
> > > read traffic. It would be good that the transaction feature can be done
> > in
> > > a similar way. So the architecture would be like this -
> > >
> > > *[ write service ] [ read service ] [ transaction coordinator ]*
> > > *[ stream store
> > >]*
> > >
> > > if people doesn't need the transaction feature, they can turn if off
> > > completely without any operational overhead.
> > >
> > > Beside that, I have one general question - What is the major goal for
> > this
> > > feature? Are you targeting on building a general XA transaction
> > coordinator
> > > or just for supporting things like `copy-modify-write' style workflow?
> > >
> > >
> > > Thanks,
> > > Sijie
> > >
> > >
> > >
> > >
> > >
> > > On Wed, Dec 28, 2016 at 1:12 PM, Xi Liu <xi.liu@gmail.com> wrote:
> > >
> > >> Ping?
> > >>
> > >> On Mon, Dec 19, 2016 at 8:28 AM, Xi Liu <xi.liu@gmail.com> wrote:
> > >>
> > >>> Sijie,
> > >>>
> > >>> No. I thought it might

Re: [Review] The first release of Apache DistributedLog

[Sijie Guo]

Yes. it is part of the plan.

On Thu, Jan 5, 2017 at 11:27 PM, Xi Liu <xi.liu@gmail.com> wrote:

> It would be great to include any performance numbers.
>
> On Thu, Jan 5, 2017 at 5:51 PM, Sijie Guo <si...@apache.org> wrote:
>
> > Cool to see you here, Enrico. And thank you for your suggestion.
> >
> > I will try to write a separate one for DL and BK. Try to keep this one
> > focus on a short release post.
> >
> > - Sijie
> >
> > On Thu, Jan 5, 2017 at 1:43 PM, Enrico Olivelli <eolive...@gmail.com>
> > wrote:
> >
> > > Hi Sijie,
> > > I am following this release and the great work DL comunity is doing.
> > > Maybe it would be worth to write some paragraph about the difference
> from
> > > BookKeeper and/or the relation with it.
> > >
> > >
> > > Enrico
> > >
> > > Il gio 5 gen 2017, 19:13 Asko Kauppi <asko.kau...@zalando.fi> ha
> > scritto:
> > >
> > > > Hi Sijie,
> > > >
> > > > most readers will likely not know about DistributedLog. A short
> > > comparison
> > > > - or a link to one - e.g. with Kafka might help set the stage for
> them.
> > > > i.e. why does it exist?
> > > >
> > > > This is even more important since Uber recently also publicized their
> > > > persistent message bus solution. If these start dropping down, there
> > > needs
> > > > to be more (technical) reason than just another vendor opening their
> > > chest.
> > > > :)
> > > >
> > > > Other than that, the structure seemed nice but it can be slightly
> > > shorter.
> > > >
> > > > Just my 2c
> > > > - asko
> > > >
> > > >
> > > > On 4 January 2017 at 10:38, Sijie Guo <si...@apache.org> wrote:
> > > >
> > > > > I drafted a blog post for announcing the first apache release. Here
> > is
> > > > the
> > > > > draft. Please help review it :D
> > > > >
> > > > > https://docs.google.com/document/d/1IXVmP2cHkf4ydeUHUJN9p5ZWTpA1a
> > > > > uwBhfqMnYBu4A0/edit
> > > > >
> > > > > - Sijie
> > > > >
> > > >
> > > --
> > >
> > >
> > > -- Enrico Olivelli
> > >
> >
>

Re: vote process for proposals?

[Sijie Guo]

seems reasonable to me. do you want to update the wiki to reflect it?

On Thu, Jan 5, 2017 at 11:32 PM, Xi Liu <xi.liu@gmail.com> wrote:

> I think there is not a lot of activities on proposals. A 'lazy approval'
> might be just good enough - a proposal with lazy approval  is implicitly
> allowed/accepted unless a  -1 vote is received. That's probably the best
> for now. what do you think?
>
> On Wed, Jan 4, 2017 at 12:50 AM, Sijie Guo <si...@apache.org> wrote:
>
> > Ping?
> >
> > Xi, Jon, any updates about this? Do any of you want to drive this?
> >
> > - Sijie
> >
> >
> >
> > On Thu, Dec 15, 2016 at 11:18 AM, Sijie Guo <sij...@twitter.com.invalid>
> > wrote:
> >
> > > Xi, Jon, are any of you interested in making a draft about about the
> > > proposal workflow?
> > >
> > > On Wed, Dec 14, 2016 at 6:14 PM, Jon Derrick <
> > jonathan.derri...@gmail.com>
> > > wrote:
> > >
> > > > I think it really worth having a voting proposal, as sometime I might
> > > lose
> > > > track of if a proposal is accepted or not and whether it is under
> > > > development.
> > > >
> > > > Beam's process looks promising. You can try to start with that.
> > > >
> > > > Another suggestion is it would be awesome if the DL jira queue can
> have
> > > new
> > > > type, called 'Proposal'. Then we can enforce the proposal workflow in
> > the
> > > > jira.
> > > >
> > >
> > > I think it is possible to ask INFRA team to create a new jira
> > type/workflow
> > > for us, if we can come up with more details. Can you tell us more about
> > > your thoughts?
> > >
> > > - Sijie
> > >
> > >
> > > >
> > > > On Tue, Dec 13, 2016 at 1:10 AM, Xi Liu <xi.liu@gmail.com>
> wrote:
> > > >
> > > > > Thank you Sijie. I feel it is good to have a voting process, so
> that
> > it
> > > > > would be good to track if a proposal is accepted for developing or
> > > > > discarded due to any reasons. I will start with my proposal and see
> > how
> > > > it
> > > > > is going with the community.
> > > > >
> > > > > - Xi
> > > > >
> > > > > On Thu, Dec 8, 2016 at 9:11 PM, Sijie Guo <si...@apache.org>
> wrote:
> > > > >
> > > > > > Xi, thank you for raising this up. I don't think we have a formal
> > > > process
> > > > > > for track proposals. I think we can learn the proposals from
> other
> > > > apache
> > > > > > projects. For example, beam has very nice documentation on
> > > contribution
> > > > > > guide (http://beam.incubator.apache.org/contribute/contribution-
> > > guide/
> > > > ).
> > > > > > We
> > > > > > probably can adopt it.
> > > > > >
> > > > > > I don't feel strong about the voting process. If it is easier for
> > > > making
> > > > > > conclusion on the proposal discussion, let's vote for any
> discussed
> > > > > > proposal.
> > > > > >
> > > > > > - Sijie
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, Dec 8, 2016 at 9:10 AM, Xi Liu <xi.liu@gmail.com>
> > wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > It is great that we have a process to track/discuss proposals.
> > but
> > > > the
> > > > > > > process is still a bit unclear to me. do we need a vote phase
> to
> > > > adopt
> > > > > > the
> > > > > > > proposals? and shall we document the process in wiki page?
> > > > > > >
> > > > > > > my basic understand about the process is:
> > > > > > >
> > > > > > > - create a proposal wiki page to describe the proposal
> > > > > > > - start the '[discussion]' email thread for the proposal
> > > > > > > - conversation will happen in the '[discussion]' email thread
> and
> > > the
> > > > > > wiki
> > > > > > > page will be refined
> > > > > > >
> > > > > > > I feel there will be a phase to decide whether this proposal
> will
> > > be
> > > > > > > accepted or discarded and update the state of the proposals.
> > shall
> > > I
> > > > > vote
> > > > > > > DP-2?
> > > > > > >
> > > > > > > - Xi
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > - jderrick
> > > >
> > >
> >
>

Re: [Review] The first release of Apache DistributedLog

[Sijie Guo]

Cool to see you here, Enrico. And thank you for your suggestion.

I will try to write a separate one for DL and BK. Try to keep this one
focus on a short release post.

- Sijie

On Thu, Jan 5, 2017 at 1:43 PM, Enrico Olivelli <eolive...@gmail.com> wrote:

> Hi Sijie,
> I am following this release and the great work DL comunity is doing.
> Maybe it would be worth to write some paragraph about the difference from
> BookKeeper and/or the relation with it.
>
>
> Enrico
>
> Il gio 5 gen 2017, 19:13 Asko Kauppi <asko.kau...@zalando.fi> ha scritto:
>
> > Hi Sijie,
> >
> > most readers will likely not know about DistributedLog. A short
> comparison
> > - or a link to one - e.g. with Kafka might help set the stage for them.
> > i.e. why does it exist?
> >
> > This is even more important since Uber recently also publicized their
> > persistent message bus solution. If these start dropping down, there
> needs
> > to be more (technical) reason than just another vendor opening their
> chest.
> > :)
> >
> > Other than that, the structure seemed nice but it can be slightly
> shorter.
> >
> > Just my 2c
> > - asko
> >
> >
> > On 4 January 2017 at 10:38, Sijie Guo <si...@apache.org> wrote:
> >
> > > I drafted a blog post for announcing the first apache release. Here is
> > the
> > > draft. Please help review it :D
> > >
> > > https://docs.google.com/document/d/1IXVmP2cHkf4ydeUHUJN9p5ZWTpA1a
> > > uwBhfqMnYBu4A0/edit
> > >
> > > - Sijie
> > >
> >
> --
>
>
> -- Enrico Olivelli
>

Re: [Review] The first release of Apache DistributedLog

[Sijie Guo]

Thank you for your suggestion, Asko.

Try to make the announcement post shorter and keep it focused on release.
Will try to prepare another post for education.

- Sijie


On Thu, Jan 5, 2017 at 10:13 AM, Asko Kauppi <asko.kau...@zalando.fi> wrote:

> Hi Sijie,
>
> most readers will likely not know about DistributedLog. A short comparison
> - or a link to one - e.g. with Kafka might help set the stage for them.
> i.e. why does it exist?
>
> This is even more important since Uber recently also publicized their
> persistent message bus solution. If these start dropping down, there needs
> to be more (technical) reason than just another vendor opening their chest.
> :)
>
> Other than that, the structure seemed nice but it can be slightly shorter.
>
> Just my 2c
> - asko
>
>
> On 4 January 2017 at 10:38, Sijie Guo <si...@apache.org> wrote:
>
> > I drafted a blog post for announcing the first apache release. Here is
> the
> > draft. Please help review it :D
> >
> > https://docs.google.com/document/d/1IXVmP2cHkf4ydeUHUJN9p5ZWTpA1a
> > uwBhfqMnYBu4A0/edit
> >
> > - Sijie
> >
>

Re: [Discuss] Transaction Support

[Sijie Guo]

Xi, I added more comments. We are looking forward to your reply and seeing
this happen.

- Sijie

On Tue, Jan 3, 2017 at 11:18 PM, Sijie Guo <si...@apache.org> wrote:

> Sorry for late response. I think Leigh and you already had some very
> valuable discussions in the doc. I will try to add some of my questions to
> the discussion.
>
> Beside that, I had a discussion with Leigh today about this. first of all,
> I think it is very good to add transaction support in distributedlog. It is
> one of the primitives that would help building distributed service. But we
> have a concern about making this system become complicated and introduce
> operational overhead when it runs in the large scale system on production.
> There are two major suggestions that I have for this feature -
>
> Build the 'minimum' logic in core - I think the minimum logic that need to
> be added to the core is -  the special control records (begin, commit and
> abort) and make the reader be able to detect those special control records
> and know what do they mean and how to interrupt with them. Since they are
> special control records, there is not overhead to other readers that
> doesn't require this feature.
>
> Build the transaction coordinator as a separated proxy service  - I think
> the major concern that we have is putting more complexities into the 'write
> proxy' service. We architected distributedlog in a more microservice-like
> way - we have the core as the stream store, the proxy for serving write and
> read traffic. It would be good that the transaction feature can be done in
> a similar way. So the architecture would be like this -
>
> *[ write service ] [ read service ] [ transaction coordinator ]*
> *[ stream store
>   ]*
>
> if people doesn't need the transaction feature, they can turn if off
> completely without any operational overhead.
>
> Beside that, I have one general question - What is the major goal for this
> feature? Are you targeting on building a general XA transaction coordinator
> or just for supporting things like `copy-modify-write' style workflow?
>
>
> Thanks,
> Sijie
>
>
>
>
>
> On Wed, Dec 28, 2016 at 1:12 PM, Xi Liu <xi.liu@gmail.com> wrote:
>
>> Ping?
>>
>> On Mon, Dec 19, 2016 at 8:28 AM, Xi Liu <xi.liu@gmail.com> wrote:
>>
>> > Sijie,
>> >
>> > No. I thought it might be easier for people to comment on a google doc
>> to
>> > gather the initial feedback. I will put the content back to wiki page
>> once
>> > addressing the comments. Does that sound good to you?
>> >
>> > And thank you in advance.
>> >
>> > - Xi
>> >
>> >
>> >
>> > On Sun, Dec 18, 2016 at 8:48 AM, Sijie Guo <si...@apache.org> wrote:
>> >
>> >> Hi Xi,
>> >>
>> >> sorry for late response. I will review it soon.
>> >>
>> >> regarding this, a separate question "are we going to use google doc
>> >> instead
>> >> of email thread for any discussion"? I am a bit worried that the
>> >> discussion
>> >> will become lost after moving to google doc. No idea on how other
>> apache
>> >> projects are doing.
>> >>
>> >> - Sijie
>> >>
>> >> On Wed, Dec 14, 2016 at 11:41 PM, Xi Liu <xi.liu@gmail.com> wrote:
>> >>
>> >> > Hi all,
>> >> >
>> >> > I finalized the first version of the design. This time I used a
>> google
>> >> doc
>> >> > so that it is easier for commenting and add a link the wiki page. I
>> will
>> >> > update this to the wiki page once we come to the finalized design.
>> >> >
>> >> > https://docs.google.com/document/d/14Ns05M8Z5a6DF6fHmWQwISyD5jjeK
>> >> > bSIGgSzXuTI5BA/edit
>> >> >
>> >> > Let me know if you have any questions. Appreciate your reviews!
>> >> >
>> >> > - Xi
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Fri, Oct 28, 2016 at 7:58 AM, Leigh Stewart
>> >> > <lstew...@twitter.com.invalid
>> >> > > wrote:
>> >> >
>> >> > > Interesting proposal. A couple quick notes while you continue to
>> flesh
>> >> > this
>> >> > > out.
>> >> > >
>> >> > > a. just to be sure - does this eliminate the need to save seqno
>> with
>> >> > &g

Re: [Discuss] Transaction Support

[Sijie Guo]

On Wed, Jan 4, 2017 at 1:14 AM, Asko Kauppi <asko.kau...@zalando.fi> wrote:

> > Beside that, I have one general question - What is the major goal for
> this
> > feature? Are you targeting on building a general XA transaction
> coordinator
> > or just for supporting things like `copy-modify-write' style workflow?
>
> The use case I would have for transactions - at some level of the stack -
> is supporting dynamic configurations.
>
> If a config changes in e.g. three lines, some of the changes may logically
> belong together. E.g. changing both “host” and “port” (if separate
> entries). One shouldn’t be able to read a state, even temporarily, that has
> new host but old port.
>
> I can do this in the application level - it does not need to be part of
> the DL protocol.
>

Yeah, I can see 'transaction' as a large atomic write in DL is very useful.
Currently DL limits the record size to 1MB. If people wants to write a
record larger than 1MB, it will potentially produce a `partial` write if
application breaks their record into multiple records.

Your use case falls into this category.

I think the minimal support is large atomic write. That is good enough for
most of the log use cases.

Having a separated TC (transaction coordinator) is cool. but it can be an
opt-in solution.



>
>
> Asko Kauppi
> Zalando Tech Helsinki
>
> > On 4 Jan 2017, at 9.18, Sijie Guo <si...@apache.org> wrote:
> >
> > Sorry for late response. I think Leigh and you already had some very
> > valuable discussions in the doc. I will try to add some of my questions
> to
> > the discussion.
> >
> > Beside that, I had a discussion with Leigh today about this. first of
> all,
> > I think it is very good to add transaction support in distributedlog. It
> is
> > one of the primitives that would help building distributed service. But
> we
> > have a concern about making this system become complicated and introduce
> > operational overhead when it runs in the large scale system on
> production.
> > There are two major suggestions that I have for this feature -
> >
> > Build the 'minimum' logic in core - I think the minimum logic that need
> to
> > be added to the core is -  the special control records (begin, commit and
> > abort) and make the reader be able to detect those special control
> records
> > and know what do they mean and how to interrupt with them. Since they are
> > special control records, there is not overhead to other readers that
> > doesn't require this feature.
> >
> > Build the transaction coordinator as a separated proxy service  - I think
> > the major concern that we have is putting more complexities into the
> 'write
> > proxy' service. We architected distributedlog in a more microservice-like
> > way - we have the core as the stream store, the proxy for serving write
> and
> > read traffic. It would be good that the transaction feature can be done
> in
> > a similar way. So the architecture would be like this -
> >
> > *[ write service ] [ read service ] [ transaction coordinator ]*
> > *[ stream store
> >]*
> >
> > if people doesn't need the transaction feature, they can turn if off
> > completely without any operational overhead.
> >
> > Beside that, I have one general question - What is the major goal for
> this
> > feature? Are you targeting on building a general XA transaction
> coordinator
> > or just for supporting things like `copy-modify-write' style workflow?
> >
> >
> > Thanks,
> > Sijie
> >
> >
> >
> >
> >
> > On Wed, Dec 28, 2016 at 1:12 PM, Xi Liu <xi.liu@gmail.com> wrote:
> >
> >> Ping?
> >>
> >> On Mon, Dec 19, 2016 at 8:28 AM, Xi Liu <xi.liu@gmail.com> wrote:
> >>
> >>> Sijie,
> >>>
> >>> No. I thought it might be easier for people to comment on a google doc
> to
> >>> gather the initial feedback. I will put the content back to wiki page
> >> once
> >>> addressing the comments. Does that sound good to you?
> >>>
> >>> And thank you in advance.
> >>>
> >>> - Xi
> >>>
> >>>
> >>>
> >>> On Sun, Dec 18, 2016 at 8:48 AM, Sijie Guo <si...@apache.org> wrote:
> >>>
> >>>> Hi Xi,
> >>>>
> >>>> sorry for late response. I will review it soon.
> >>>>
> >>>> regarding this, a separate question "are we going to use google doc
> >>>> instead
> >>>> of email t

Re: [DISCUSSION] First Release

[Sijie Guo]

cool! Thank you so much for rebasing this.

- Sijie

On Wed, Jan 4, 2017 at 6:20 PM, liang xie <xieliang...@gmail.com> wrote:

> The conflicted DL-167 change has been rebased, please help to review :)
>
> On Thu, Jan 5, 2017 at 8:53 AM, Sijie Guo <si...@apache.org> wrote:
> > FYI. I merged the repackage script and repackage the namespace under
> > org.apache.distributedlog. All the changes for 0.4.0 are merged (except
> one
> > test case change - waiting for Liang's response). Ready to cut the first
> > release candidate.
> >
> > - Sijie
> >
> > On Thu, Dec 29, 2016 at 8:40 PM, Sijie Guo <si...@apache.org> wrote:
> >
> >> I've merged all the pull requests that need to be included in 0.4.0 (and
> >> both Jenkins and CI builds are green now). Also I moved inactive jiras
> to
> >> 0.5.0.
> >>
> >> There are a few issues remaining - https://issues.apache.org/
> >> jira/issues/?jql=project%20%3D%20DL%20AND%20resolution%20%
> >> 3D%20Unresolved%20AND%20fixVersion%20%3D%200.4.0%
> >> 20ORDER%20BY%20priority%20DESC
> >>
> >> Most of them already have pull requests (but need to be rebased to
> latest
> >> master). So I can merge them.
> >>
> >> Hopefully I will be able to cut 0.4.0 release in following few days.
> >>
> >> - Sijie
> >>
> >> On Thu, Dec 8, 2016 at 9:16 PM, Sijie Guo <si...@apache.org> wrote:
> >>
> >>> I will start check the jiras that need to be included in 0.4.0 release
> at
> >>> the weekend. If there is any jiras that need to be included in 0.4.0,
> >>> please comment in the jira.
> >>>
> >>> - Sijie
> >>>
> >>> On Fri, Dec 2, 2016 at 8:28 PM, Sijie Guo <si...@apache.org> wrote:
> >>>
> >>>> FYI.
> >>>>
> >>>> https://issues.apache.org/jira/browse/DL-81 is created for tracking
> >>>> building the process.
> >>>>
> >>>> https://issues.apache.org/jira/browse/INFRA-13024 and
> >>>> https://issues.apache.org/jira/browse/INFRA-13023 for setting the
> dists
> >>>> for DL.
> >>>>
> >>>> - Sijie
> >>>>
> >>>> On Fri, Dec 2, 2016 at 8:05 PM, Sijie Guo <si...@apache.org> wrote:
> >>>>
> >>>>> Thank you for all the feedbacks. I will drive the release for this
> >>>>> version. So that we can have all the procedures documented in the
> wiki.
> >>>>>
> >>>>> I created the wiki page here for documenting the procedure:
> >>>>> https://cwiki.apache.org/confluence/display/DL/Pr
> >>>>> eparing+DistributedLog+Releases
> >>>>>
> >>>>> - Sijie
> >>>>>
> >>>>>
> >>>>> On Mon, Nov 21, 2016 at 7:10 PM, Jia Zhai <zhaiji...@gmail.com>
> wrote:
> >>>>>
> >>>>>> +1
> >>>>>> Great to know the commitment of merge twitter's branch. Looking
> >>>>>> forward to
> >>>>>> see bookkeeper 4.5.
> >>>>>>
> >>>>>> On Mon, Nov 21, 2016 at 6:36 PM, Flavio Junqueira <f...@apache.org>
> >>>>>> wrote:
> >>>>>>
> >>>>>> > It does make sense, Sijie, thanks for the update.
> >>>>>> >
> >>>>>> > -Flavio
> >>>>>> >
> >>>>>> > > On 17 Nov 2016, at 05:12, Sijie Guo <si...@apache.org> wrote:
> >>>>>> > >
> >>>>>> > > Flavio,
> >>>>>> > >
> >>>>>> > > I totally agreed that not using an official Apache  version is
> not
> >>>>>> great
> >>>>>> > > for the community. We had a bookkeeper meetup last night. We've
> >>>>>> discussed
> >>>>>> > > the current situation with the community. We came to a
> commitment
> >>>>>> to
> >>>>>> > merge
> >>>>>> > > Twitter's branch back into bookkeeper 4.5. After that we won't
> >>>>>> maintain
> >>>>>> > our
> >>>>>> > > own branch and switch to 4.5.
> >>>>>> > >
> >>>>>> > > Hope this make sense.
> >>>>>> > >

Re: Git Workflow on Windows

[Sijie Guo]

Chris,

This is very informative and useful. Thank you so much for sharing this. I
will try this out.

Yeah I think most of the issues come from path and symlinks. I think Tracy
already figured the problems out. Looking forward to the contribution.

- Sijie

On Wed, Jan 4, 2017 at 11:24 AM, Chris Nauroth  wrote:

> Microsoft offers free MSDN licenses to Apache committers.  The request
> process is documented here:
>
> https://s.apache.org/BDIK
>
> You'll need to be able to authenticate with your ASF account to access that
> link.
>
> This means that for committers who don't usually work on Windows, you have
> an option for running a Windows VM at no personal cost, in case you want to
> verify a patch running on Windows.  The approval process for the license
> can take a long time though.
>
> From past experience working on Windows compatibility for other projects
> like Hadoop and ZooKeeper, it's very common for software developed
> initially on Linux to assume '/' as the file path separator, and it looks
> like that's what is happening here.  If DistributedLog wants to support
> Windows as a development platform, then the effort would involve tracking
> down incompatibilities like this and fixing them.
>
> This could be a great area for a developer working on Windows to start
> contributing some patches too!
>
>
>
> Chris Nauroth
>
> On Wed, Jan 4, 2017 at 4:56 AM, Tracy Martin 
> wrote:
>
> > Pasted log here:
> >
> > https://gist.github.com/adamtracymartin/2ec2585d9d8efa8f81cbbcaaa2a2ed90
> >
> >
> > -Original Message-
> > From: Franck Cuny [mailto:franck.c...@gmail.com]
> > Sent: Tuesday, January 03, 2017 7:57 PM
> > To: dev@distributedlog.incubator.apache.org
> > Subject: Re: Git Workflow on Windows
> >
> > Hello Tracy,
> >
> > could you paste the complete output of the command you run somewhere ?
> >
> > As far as I know, we haven't tried to build DLog on a windows system, and
> > I don't think we've made any effort to support this so far.
> >
> > On Tue, Jan 3, 2017 at 11:35 AM Tracy Martin 
> > wrote:
> >
> > > I am fixing DL-28 after the merge, and I am following the "Git
> Workflow"
> > > described here:
> > >
> > > https://cwiki.apache.org/confluence/display/DL/Contributing+to+Distrib
> > > utedLog
> > >
> > > I am getting many failures running step 4
> > >
> > > mvn clean apache-rat:check package findbugs:check
> > >
> > > from my Windows desktop.
> > >
> > > I know the error received in DL-28 was related to running the build on
> > > Windows instead of Unix.  Many of the errors that I see in the tests
> > > point to a Windows only problem.  Most of the errors reports are "Path
> > > must start with / character".
> > >
> > > I know when I was first reading about DistributedLog that it required
> > > Unix.  Is the plan to only run from Unix systems?  If so, I will look
> > > at creating a Unix environment for building, testing, and running.
> > > This e-mail and any attachments, contain Genuine Parts Company
> > > confidential information that is proprietary, privileged, and
> > > protected by applicable laws. If you have received this message in
> > > error and are not the intended recipient, you should not retain,
> > > distribute, disclose or use any of this information and you should
> > > destroy this e-mail, any attachments or copies therein forthwith.
> > > Please notify the sender immediately by e-mail if you have received
> this
> > e-mail in error.
> > >
> > > "This e-mail and any attachments, contain Genuine Parts Company
> > > confidential information that is proprietary, privileged, and
> > > protected by applicable laws. If you have received this message in
> > > error and are not the intended recipient, you should not retain,
> > > distribute, disclose or use any of this information and you should
> > > destroy this e-mail, any attachments or copies therein forthwith.
> > > Please notify the sender immediately by e-mail if you have received
> this
> > e-mail in error."
> > >
> > --
> > -franck
> > This e-mail and any attachments, contain Genuine Parts Company
> > confidential information that is proprietary, privileged, and protected
> by
> > applicable laws. If you have received this message in error and are not
> the
> > intended recipient, you should not retain, distribute, disclose or use
> any
> > of this information and you should destroy this e-mail, any attachments
> or
> > copies therein forthwith. Please notify the sender immediately by e-mail
> if
> > you have received this e-mail in error.
> >
> > "This e-mail and any attachments, contain Genuine Parts Company
> > confidential information that is proprietary, privileged, and protected
> by
> > applicable laws. If you have received this message in error and are not
> the
> > intended recipient, you should not retain, distribute, disclose or use
> any
> > of this information and you should destroy this e-mail, any attachments
> or
> > copies 

Re: [DISCUSSION] First Release

[Sijie Guo]

FYI. I merged the repackage script and repackage the namespace under
org.apache.distributedlog. All the changes for 0.4.0 are merged (except one
test case change - waiting for Liang's response). Ready to cut the first
release candidate.

- Sijie

On Thu, Dec 29, 2016 at 8:40 PM, Sijie Guo <si...@apache.org> wrote:

> I've merged all the pull requests that need to be included in 0.4.0 (and
> both Jenkins and CI builds are green now). Also I moved inactive jiras to
> 0.5.0.
>
> There are a few issues remaining - https://issues.apache.org/
> jira/issues/?jql=project%20%3D%20DL%20AND%20resolution%20%
> 3D%20Unresolved%20AND%20fixVersion%20%3D%200.4.0%
> 20ORDER%20BY%20priority%20DESC
>
> Most of them already have pull requests (but need to be rebased to latest
> master). So I can merge them.
>
> Hopefully I will be able to cut 0.4.0 release in following few days.
>
> - Sijie
>
> On Thu, Dec 8, 2016 at 9:16 PM, Sijie Guo <si...@apache.org> wrote:
>
>> I will start check the jiras that need to be included in 0.4.0 release at
>> the weekend. If there is any jiras that need to be included in 0.4.0,
>> please comment in the jira.
>>
>> - Sijie
>>
>> On Fri, Dec 2, 2016 at 8:28 PM, Sijie Guo <si...@apache.org> wrote:
>>
>>> FYI.
>>>
>>> https://issues.apache.org/jira/browse/DL-81 is created for tracking
>>> building the process.
>>>
>>> https://issues.apache.org/jira/browse/INFRA-13024 and
>>> https://issues.apache.org/jira/browse/INFRA-13023 for setting the dists
>>> for DL.
>>>
>>> - Sijie
>>>
>>> On Fri, Dec 2, 2016 at 8:05 PM, Sijie Guo <si...@apache.org> wrote:
>>>
>>>> Thank you for all the feedbacks. I will drive the release for this
>>>> version. So that we can have all the procedures documented in the wiki.
>>>>
>>>> I created the wiki page here for documenting the procedure:
>>>> https://cwiki.apache.org/confluence/display/DL/Pr
>>>> eparing+DistributedLog+Releases
>>>>
>>>> - Sijie
>>>>
>>>>
>>>> On Mon, Nov 21, 2016 at 7:10 PM, Jia Zhai <zhaiji...@gmail.com> wrote:
>>>>
>>>>> +1
>>>>> Great to know the commitment of merge twitter's branch. Looking
>>>>> forward to
>>>>> see bookkeeper 4.5.
>>>>>
>>>>> On Mon, Nov 21, 2016 at 6:36 PM, Flavio Junqueira <f...@apache.org>
>>>>> wrote:
>>>>>
>>>>> > It does make sense, Sijie, thanks for the update.
>>>>> >
>>>>> > -Flavio
>>>>> >
>>>>> > > On 17 Nov 2016, at 05:12, Sijie Guo <si...@apache.org> wrote:
>>>>> > >
>>>>> > > Flavio,
>>>>> > >
>>>>> > > I totally agreed that not using an official Apache  version is not
>>>>> great
>>>>> > > for the community. We had a bookkeeper meetup last night. We've
>>>>> discussed
>>>>> > > the current situation with the community. We came to a commitment
>>>>> to
>>>>> > merge
>>>>> > > Twitter's branch back into bookkeeper 4.5. After that we won't
>>>>> maintain
>>>>> > our
>>>>> > > own branch and switch to 4.5.
>>>>> > >
>>>>> > > Hope this make sense.
>>>>> > >
>>>>> > > Sijie
>>>>> > >
>>>>> > > On Nov 16, 2016 8:04 PM, "Flavio Junqueira" <f...@apache.org>
>>>>> wrote:
>>>>> > >
>>>>> > > It isn't great that DistributedLog is not using the Apache
>>>>> BookKeeper
>>>>> > > release. Essentially anyone using DistributedLog today needs to
>>>>> use the
>>>>> > > Twitter branch of BookKeeper, which has diverged from Apache
>>>>> BookKeeper.
>>>>> > > I'm sure the changes in the Twitter branch are all great, but I'd
>>>>> be more
>>>>> > > comfortable being able to rely on the Apache BookKeeper releases,
>>>>> which
>>>>> > are
>>>>> > > community driven.
>>>>> > >
>>>>> > > I'm not going to block the release on this alone because it is
>>>>> important
>>>&

Re: vote process for proposals?

[Sijie Guo]

Ping?

Xi, Jon, any updates about this? Do any of you want to drive this?

- Sijie



On Thu, Dec 15, 2016 at 11:18 AM, Sijie Guo <sij...@twitter.com.invalid>
wrote:

> Xi, Jon, are any of you interested in making a draft about about the
> proposal workflow?
>
> On Wed, Dec 14, 2016 at 6:14 PM, Jon Derrick <jonathan.derri...@gmail.com>
> wrote:
>
> > I think it really worth having a voting proposal, as sometime I might
> lose
> > track of if a proposal is accepted or not and whether it is under
> > development.
> >
> > Beam's process looks promising. You can try to start with that.
> >
> > Another suggestion is it would be awesome if the DL jira queue can have
> new
> > type, called 'Proposal'. Then we can enforce the proposal workflow in the
> > jira.
> >
>
> I think it is possible to ask INFRA team to create a new jira type/workflow
> for us, if we can come up with more details. Can you tell us more about
> your thoughts?
>
> - Sijie
>
>
> >
> > On Tue, Dec 13, 2016 at 1:10 AM, Xi Liu <xi.liu@gmail.com> wrote:
> >
> > > Thank you Sijie. I feel it is good to have a voting process, so that it
> > > would be good to track if a proposal is accepted for developing or
> > > discarded due to any reasons. I will start with my proposal and see how
> > it
> > > is going with the community.
> > >
> > > - Xi
> > >
> > > On Thu, Dec 8, 2016 at 9:11 PM, Sijie Guo <si...@apache.org> wrote:
> > >
> > > > Xi, thank you for raising this up. I don't think we have a formal
> > process
> > > > for track proposals. I think we can learn the proposals from other
> > apache
> > > > projects. For example, beam has very nice documentation on
> contribution
> > > > guide (http://beam.incubator.apache.org/contribute/contribution-
> guide/
> > ).
> > > > We
> > > > probably can adopt it.
> > > >
> > > > I don't feel strong about the voting process. If it is easier for
> > making
> > > > conclusion on the proposal discussion, let's vote for any discussed
> > > > proposal.
> > > >
> > > > - Sijie
> > > >
> > > >
> > > >
> > > > On Thu, Dec 8, 2016 at 9:10 AM, Xi Liu <xi.liu@gmail.com> wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > It is great that we have a process to track/discuss proposals. but
> > the
> > > > > process is still a bit unclear to me. do we need a vote phase to
> > adopt
> > > > the
> > > > > proposals? and shall we document the process in wiki page?
> > > > >
> > > > > my basic understand about the process is:
> > > > >
> > > > > - create a proposal wiki page to describe the proposal
> > > > > - start the '[discussion]' email thread for the proposal
> > > > > - conversation will happen in the '[discussion]' email thread and
> the
> > > > wiki
> > > > > page will be refined
> > > > >
> > > > > I feel there will be a phase to decide whether this proposal will
> be
> > > > > accepted or discarded and update the state of the proposals. shall
> I
> > > vote
> > > > > DP-2?
> > > > >
> > > > > - Xi
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > - jderrick
> >
>

[Review] The first release of Apache DistributedLog

[Sijie Guo]

I drafted a blog post for announcing the first apache release. Here is the
draft. Please help review it :D

https://docs.google.com/document/d/1IXVmP2cHkf4ydeUHUJN9p5ZWTpA1auwBhfqMnYBu4A0/edit

- Sijie

Re: Git Workflow on Windows

[Sijie Guo]

We definitely want to support running distributedlog in other environments.
And in theory, it is a Java system, it should be able to run on different
platforms. But as what Franck mentioned, the major problem is most of us
don't have a windows environment :/ I tried to have a Jenkins job or Travis
CI job to build distributedlog on windows. But unfortunately, it is
inconvenient for me to debug what it failed.

Based on the conversation in the jiras, it seems that the major problems
are a compilation problem and a symlink problem. So fixing these two should
be able to compile and run distributedlog on windows. However, in order to
validate the performance on windows, we might seek for helps from the
people who have more experiences on windows.

- Sijie

On Tue, Jan 3, 2017 at 4:56 PM, Franck Cuny  wrote:

> Hello Tracy,
>
> could you paste the complete output of the command you run somewhere ?
>
> As far as I know, we haven't tried to build DLog on a windows system, and I
> don't think we've made any effort to support this so far.
>
> On Tue, Jan 3, 2017 at 11:35 AM Tracy Martin 
> wrote:
>
> > I am fixing DL-28 after the merge, and I am following the "Git Workflow"
> > described here:
> >
> > https://cwiki.apache.org/confluence/display/DL/
> Contributing+to+DistributedLog
> >
> > I am getting many failures running step 4
> >
> > mvn clean apache-rat:check package findbugs:check
> >
> > from my Windows desktop.
> >
> > I know the error received in DL-28 was related to running the build on
> > Windows instead of Unix.  Many of the errors that I see in the tests
> point
> > to a Windows only problem.  Most of the errors reports are "Path must
> start
> > with / character".
> >
> > I know when I was first reading about DistributedLog that it required
> > Unix.  Is the plan to only run from Unix systems?  If so, I will look at
> > creating a Unix environment for building, testing, and running.
> > This e-mail and any attachments, contain Genuine Parts Company
> > confidential information that is proprietary, privileged, and protected
> by
> > applicable laws. If you have received this message in error and are not
> the
> > intended recipient, you should not retain, distribute, disclose or use
> any
> > of this information and you should destroy this e-mail, any attachments
> or
> > copies therein forthwith. Please notify the sender immediately by e-mail
> if
> > you have received this e-mail in error.
> >
> > "This e-mail and any attachments, contain Genuine Parts Company
> > confidential information that is proprietary, privileged, and protected
> by
> > applicable laws. If you have received this message in error and are not
> the
> > intended recipient, you should not retain, distribute, disclose or use
> any
> > of this information and you should destroy this e-mail, any attachments
> or
> > copies therein forthwith. Please notify the sender immediately by e-mail
> if
> > you have received this e-mail in error."
> >
> --
> -franck
>

Announce DistributedLog Slack Channel

[Sijie Guo]

Hello all,

Happy New Year!

I'd happy to announce that we have a Slack channel for distributedlog
community now.

Slack Channel : https://apachedistributedlog.slack.com

You can get an invitation to join the slack channel via this url -
https://getdl-slack.herokuapp.com/

Let me know if you have questions. Look forward to see you guys hangout
there!

Thanks,
Sijie

Re: Request wiki edit permissions

[Sijie Guo]

Done.

- Sijie

On Thu, Dec 22, 2016 at 12:59 AM, Jay Juma <jayk.j...@gmail.com> wrote:

> Sijie,
>
> My wiki handle is jayk.juma.
>
> https://cwiki.apache.org/confluence/display/~jayk.juma
>
> Thanks in advance.
>
> - Jay
>
> On Thu, Dec 15, 2016 at 11:35 AM, Sijie Guo <sij...@twitter.com.invalid>
> wrote:
>
> > Jay,
> >
> > what is your wiki handle?
> >
> > - Sijie
> >
> > On Wed, Dec 14, 2016 at 6:26 PM, Jay Juma <jayk.j...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I'd like to create a distributedlog proposal. But I can't edit the wiki
> > > page. Can any committers grant edit permissions to me? Thanks in
> advance.
> > >
> > > - Jay
> > >
> >
>

[jira] [Updated] (DL-18) Shard id is not optional

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated DL-18:

Labels: help-wanted  (was: )

> Shard id is not optional
> 
>
> Key: DL-18
> URL: https://issues.apache.org/jira/browse/DL-18
> Project: DistributedLog
>  Issue Type: Task
>  Components: documentation
>    Reporter: Sijie Guo
>  Labels: help-wanted
> Fix For: 0.4.0
>
>
> http://distributedlog.io/configuration/proxy.html in the documentation, 
> {quote}
> server_shard: The shard id used by the server to identify itself. It is 
> optional but recommended to set. For example, if the write proxy is running 
> in Apache Aurora, you could use the instance id as the shard id. The default 
> value is -1 (unset).
> {quote}
> However, the shard id is not optional. because the ledger allocator pool uses 
> it to distinguish ledger allocators (see DL-17).
> We need to update the documentation to reflect the current state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-24) broken quickstart tutorial

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-24.
-
Resolution: Fixed

> broken quickstart tutorial 
> ---
>
> Key: DL-24
> URL: https://issues.apache.org/jira/browse/DL-24
> Project: DistributedLog
>  Issue Type: Task
>  Components: documentation
>    Reporter: Sijie Guo
> Fix For: 0.4.0
>
>
> reported at https://github.com/twitter/distributedlog/issues/40



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DL-17) Ledger allocator pool should be able to use hostname to distinguish write proxies

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated DL-17:

Labels: help-wanted  (was: )

> Ledger allocator pool should be able to use hostname to distinguish write 
> proxies
> -
>
> Key: DL-17
> URL: https://issues.apache.org/jira/browse/DL-17
> Project: DistributedLog
>  Issue Type: Task
>  Components: distributedlog-service
>    Reporter: Sijie Guo
>  Labels: help-wanted
> Fix For: 0.4.0
>
>
> Currently write proxy uses shard id to distinguish ledger allocators in the 
> pool. Using shard id is very convenient if deploying using a scheduler like 
> aurora, as scheduler usually be able to assign a unique shard id.
> However, for deployments not using aurora, it might make sense to use just 
> hostname to identify the allocator used by a specific write proxy. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DL-9) Reverse iterator over a log stream #24

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated DL-9:
---
Labels: help-wanted  (was: )

> Reverse iterator over a log stream #24
> --
>
> Key: DL-9
> URL: https://issues.apache.org/jira/browse/DL-9
> Project: DistributedLog
>  Issue Type: New Feature
>  Components: distributedlog-core
>    Reporter: Sijie Guo
>  Labels: help-wanted
>
> The AsyncLogReader only provides forward iterator over a log stream. 
> Sometimes, a reverse iterator is helpful.
> Cloned from https://github.com/twitter/distributedlog/issues/24



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-62) BKSyncLogReader has deadlock

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-62.
-
   Resolution: Fixed
Fix Version/s: 0.4.0

This has been merged at ebaf145807813c2731f3afbcd30fb526a1d677da

> BKSyncLogReader has deadlock
> 
>
> Key: DL-62
> URL: https://issues.apache.org/jira/browse/DL-62
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-core
>Reporter: Khurrum Nasim
>Assignee: Khurrum Nasim
> Fix For: 0.4.0
>
>
> There is a deadlock introduced in DL-32 when [~jderrick] fixed the findbug 
> errors. It is also the root cause of CI failures (DL-59)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DL-61) Open reader starting from a given sequence id

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated DL-61:

Labels: help-wanted  (was: )

> Open reader starting from a given sequence id
> -
>
> Key: DL-61
> URL: https://issues.apache.org/jira/browse/DL-61
> Project: DistributedLog
>  Issue Type: New Feature
>  Components: distributedlog-core
>Reporter: Khurrum Nasim
>Assignee: Khurrum Nasim
>  Labels: help-wanted
>
> Current implementation only supports opening reader by DLSN or TransactionID. 
> DL should support opening reader by SequenceID too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-35) Document on how to setup a global DL cluster

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-35.
-
Resolution: Fixed

This has been merged at 
https://github.com/apache/incubator-distributedlog/pull/36

> Document on how to setup a global DL cluster
> 
>
> Key: DL-35
> URL: https://issues.apache.org/jira/browse/DL-35
> Project: DistributedLog
>  Issue Type: Task
>  Components: documentation
>    Reporter: Sijie Guo
>Assignee: Leigh Stewart
> Fix For: 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DL-121) DL should inherit AutoCloseable

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated DL-121:
-
Labels: help-wanted  (was: )

> DL should inherit AutoCloseable
> ---
>
> Key: DL-121
> URL: https://issues.apache.org/jira/browse/DL-121
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-core
>Reporter: Gerrit Sundaram
>  Labels: help-wanted
>
> It would be great that DL resources (e.g. namespace, manager, writer and 
> reader) can be auto closable. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-97) Remove unused methods in BKLogHandler

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-97.
-
Resolution: Fixed

> Remove unused methods in BKLogHandler
> -
>
> Key: DL-97
> URL: https://issues.apache.org/jira/browse/DL-97
> Project: DistributedLog
>  Issue Type: Sub-task
>  Components: distributedlog-core
>    Reporter: Sijie Guo
>    Assignee: Sijie Guo
> Fix For: 0.4.0
>
>
> Remove unused methods in BKLogHandler



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (DL-28) generate java code failed using scrooge

[Sijie Guo (JIRA)]

[ 
https://issues.apache.org/jira/browse/DL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15768308#comment-15768308
 ] 

Sijie Guo commented on DL-28:
-

[~fonan] okay. let me know if you need any help.

> generate java code failed using scrooge
> ---
>
> Key: DL-28
> URL: https://issues.apache.org/jira/browse/DL-28
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-protocol
>Affects Versions: 0.4.0
> Environment: Apache Maven 3.2.5
> Maven home: C:\apache-maven-3.2.5
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: C:\Java\jdk1.8.0_60\jre
> Default locale: zh_CN, platform encoding: UTF-8
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
>Reporter: weiwei
>Assignee: Liang Xie
>Priority: Blocker
>  Labels: build
> Fix For: 0.4.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] distributedlog . SUCCESS [  0.002 
> s]
> [INFO] DistributedLog Protocol  FAILURE [  1.081 
> s]
> [INFO] DistributedLog Core Library  SKIPPED
> [INFO] DistributedLog Client .. SKIPPED
> [INFO] DistributedLog Service . SKIPPED
> [INFO] DistributedLog Benchmark ... SKIPPED
> [INFO] DistributedLog Example . SKIPPED
> [INFO] DistributedLog Basics .. SKIPPED
> [INFO] DistributedLog Messaging Tutorial .. SKIPPED
> [INFO] DistributedLog Kafka Tutorial .. SKIPPED
> [INFO] DistributedLog MapReduce ... SKIPPED
> [INFO] DistributedLog Tutorials ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.321 s
> [INFO] Finished at: 2016-08-02T13:26:31+08:00
> [INFO] Final Memory: 12M/150M
> [INFO] 
> 
> [ERROR] Exception parsing: 
> E:\incubator-distributedlog\distributedlog-protocol\src\main\thrift\service.thrift:
>  [3.1] failure: string matching regex `\z' expected but `/' found
> [ERROR] 
> [ERROR] // Response stats codes
> [ERROR] 
> [ERROR] ^
> [ERROR] -> [Help 1]
> com.twitter.scrooge.frontend.FileParseException: Exception parsing: 
> E:\isoftstone\workspacedeis\incubator-distributedlog\distributedlog-protocol\src\main\thrift\service.thrift
>   at 
> com.twitter.scrooge.frontend.ThriftParser$$anonfun$parse$1.apply(ThriftParser.scala:427)
>   at 
> com.twitter.scrooge.frontend.ThriftParser$$anonfun$parse$1.apply(ThriftParser.scala:427)
>   at scala.Option.map(Option.scala:145)
>   at 
> com.twitter.scrooge.frontend.ThriftParser.parse(ThriftParser.scala:420)
>   at 
> com.twitter.scrooge.frontend.ThriftParser.parseFile(ThriftParser.scala:448)
>   at com.twitter.scrooge.Compiler$$anonfun$run$2.apply(Compiler.scala:66)
>   at com.twitter.scrooge.Compiler$$anonfun$run$2.apply(Compiler.scala:64)
>   at scala.collection.immutable.List.foreach(List.scala:318)
>   at 
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:32)
>   at scala.collection.mutable.ListBuffer.foreach(ListBuffer.scala:45)
>   at com.twitter.scrooge.Compiler.run(Compiler.scala:64)
>   at com.twitter.ScroogeRunner.compile(ScroogeRunner.scala:45)
>   at 
> com.twitter.AbstractMavenScroogeMojo.execute(AbstractMavenScroogeMojo.java:239)
>   at 
> com.twitter.MavenScroogeCompileMojo.execute(MavenScroogeCompileMojo.java:22)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.

[jira] [Created] (DL-151) TestBKLogReadHandler#testGetFirstDLSNWithOpenLedger is flaky

[Sijie Guo (JIRA)]

Sijie Guo created DL-151:


 Summary: TestBKLogReadHandler#testGetFirstDLSNWithOpenLedger is 
flaky
 Key: DL-151
 URL: https://issues.apache.org/jira/browse/DL-151
 Project: DistributedLog
  Issue Type: Task
  Components: distributedlog-core, tests
Reporter: Sijie Guo
Assignee: Sijie Guo


{code}
Failed tests:   
testGetFirstDLSNWithOpenLedger(com.twitter.distributedlog.TestBKLogReadHandler):
 expected:<DLSN{logSegmentSequenceNo=1, entryId=99, slotId=0}> but 
was:<DLSN{logSegmentSequenceNo=1, entryId=86, slotId=0}>
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (DL-149) Docker support

[Sijie Guo (JIRA)]

[ 
https://issues.apache.org/jira/browse/DL-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15768060#comment-15768060
 ] 

Sijie Guo commented on DL-149:
--

/cc [~franckcuny]

[~franckcuny] was making distributedlog run on k8s. you guys can coordinate on 
that.

> Docker support
> --
>
> Key: DL-149
> URL: https://issues.apache.org/jira/browse/DL-149
> Project: DistributedLog
>  Issue Type: Improvement
>Reporter: Asko Kauppi
>
> I would like to run DistributedLog in two ways:
> - on my local machine, within a development folder, for a project that uses DL
> - on Kubernetes cluster for production
> Better, modularized Docker support would allow both of these to happen. I 
> could use docker-compose to launch a development setup by a one-liner. In 
> Kubernetes, having separate Zookeeper, BookKeeper, Write Proxy and Read Proxy 
> images would allow free adjustment on how many of these are run, and where.
> I found multiple Docker image projects in the Internet, including one 
> Dockerfile in the distributedlog project itself. However, none of them cover 
> the above needs. So I started this: 
> https://github.com/akauppi/distributedlog-blanket
> The Docker images there don't work. I would ask for help to make it better.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DL-150) TestZKLogMetadataForWriter.testCreateLogMetadata is flaky

[Sijie Guo (JIRA)]

Sijie Guo created DL-150:


 Summary: TestZKLogMetadataForWriter.testCreateLogMetadata is flaky
 Key: DL-150
 URL: https://issues.apache.org/jira/browse/DL-150
 Project: DistributedLog
  Issue Type: Task
  Components: tests
Reporter: Sijie Guo
Assignee: Sijie Guo
 Fix For: 0.4.0


{code}
Error Message

Failed to create log /messaging/distributedlog/testCreateLogMetadata/ 
: NONODE

Stacktrace

com.twitter.distributedlog.exceptions.ZKException: Failed to create log 
/messaging/distributedlog/testCreateLogMetadata/ : NONODE
at 
com.twitter.distributedlog.impl.metadata.ZKLogMetadataForWriter$3.processResult(ZKLogMetadataForWriter.java:277)
at 
org.apache.bookkeeper.zookeeper.ZooKeeperClient$3$1.processResult(ZooKeeperClient.java:566)
at 
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:687)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:528)

{code}

The problem is the namespace uri is not created before tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-146) Fix Stream typo : initiaize

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-146.
--
   Resolution: Fixed
Fix Version/s: 0.4.0

Merge the fix. Thanks [~xieliang007]

> Fix Stream typo : initiaize
> ---
>
> Key: DL-146
> URL: https://issues.apache.org/jira/browse/DL-146
> Project: DistributedLog
>  Issue Type: Improvement
>  Components: distributedlog-service
>Reporter: Liang Xie
>Assignee: Liang Xie
>Priority: Minor
> Fix For: 0.4.0
>
>
> "moved to initiaize()" -> "moved to initialize()"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-93) LogSegmentMetadataStore should only notify when the list of log segments is updated

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-93.
-
Resolution: Fixed

> LogSegmentMetadataStore should only notify when the list of log segments is 
> updated
> ---
>
> Key: DL-93
> URL: https://issues.apache.org/jira/browse/DL-93
> Project: DistributedLog
>  Issue Type: Improvement
>  Components: distributedlog-core
>    Reporter: Sijie Guo
>Assignee: Sijie Guo
> Fix For: 0.4.0
>
>
> Currently it notifies the listeners not only when there is a change but also 
> when session expires. it would break the reada
> head loop and cause readers have to wait until it is able to connect to 
> zookeeper again.
> With this change, it would only notify when the list of log segments is 
> updated. If it disconnects to zookeeper, the listen
> er won't be notified and it would keep reading from the log segments it knows.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-94) Make the zookeeper client used by bookkeeper client retry on session expires

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-94.
-
Resolution: Fixed

> Make the zookeeper client used by bookkeeper client retry on session expires
> 
>
> Key: DL-94
> URL: https://issues.apache.org/jira/browse/DL-94
> Project: DistributedLog
>  Issue Type: Improvement
>  Components: distributedlog-core
>    Reporter: Sijie Guo
>    Assignee: Sijie Guo
> Fix For: 0.4.0
>
>
>  * the zookeeper client used by bookkeeper client is purely for metadata 
> accesses, so we should retry on session expires.
> * remove the unnessary zookeeper session handling in bk log handler. as 
> we don't necessary to fail bookkeeper client or log
>  handler when session expires as it would be handled and retried by the 
> zookeeper client.
> * Make the retry infinitely if the retry settings for bkc zookeeper 
> client is set to 0 or negative.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-92) Simplify the state transition on stream

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-92.
-
   Resolution: Fixed
Fix Version/s: 0.4.0

> Simplify the state transition on stream
> ---
>
> Key: DL-92
> URL: https://issues.apache.org/jira/browse/DL-92
> Project: DistributedLog
>  Issue Type: Improvement
>  Components: distributedlog-service
>Affects Versions: 0.4.0
>    Reporter: Sijie Guo
>Assignee: Leigh Stewart
> Fix For: 0.4.0
>
>
> Simplify the state transition on stream
> * the stream is created on INITIALIZING
> * when the stream is started, it would start transition from INITIALIZING 
> to INITIALIZED
> * it would serve stream operations when the stream is INITIALIZED
> * it would be turned to ERROR when encountered exceptions.
> * the stream would be closed when service operation timeout or 
> encountered any exceptions. it would first be removed from  acquired mapping
> * the stream would be removed from cached mapping depends on probation 
> time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (DL-107) Added unregistering gauges for distributedlog-core and distributedlog-benchmark

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated DL-107:
-
Assignee: Philip Su

> Added unregistering gauges for distributedlog-core and 
> distributedlog-benchmark
> ---
>
> Key: DL-107
> URL: https://issues.apache.org/jira/browse/DL-107
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-core
>    Reporter: Sijie Guo
>Assignee: Philip Su
> Fix For: 0.4.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-86) Improve handling of lock conflicts in zk session lock

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-86.
-
Resolution: Fixed

> Improve handling of lock conflicts in zk session lock
> -
>
> Key: DL-86
> URL: https://issues.apache.org/jira/browse/DL-86
> Project: DistributedLog
>  Issue Type: Improvement
>  Components: distributedlog-core
>    Reporter: Sijie Guo
>    Assignee: Sijie Guo
> Fix For: 0.4.0
>
>
> - lock reacquire could happen in foreground and background thread. so use a 
> semaphore to make sure there is only on e  outstanding  acquire 
> operation. and  check if already hold lock before reacquire.
> - fix handling zk sibling znode logic. as the znode is sequential znode, 
> the name would be different each time. so onlycomparing the client id and 
> session id of the znodes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-123) Every tests should have timeout

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-123.
--
   Resolution: Fixed
Fix Version/s: 0.4.0

Thank you [~boyork]

> Every tests should have timeout
> ---
>
> Key: DL-123
> URL: https://issues.apache.org/jira/browse/DL-123
> Project: DistributedLog
>  Issue Type: Bug
>Reporter: Gerrit Sundaram
>Assignee: Brennon York
>  Labels: help-wanted
> Fix For: 0.4.0
>
>
> Currently not every test has timeout value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-89) add flag to enable thrift mux on DL monitor service

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-89.
-
Resolution: Fixed

> add flag to enable thrift mux on DL monitor service
> ---
>
> Key: DL-89
> URL: https://issues.apache.org/jira/browse/DL-89
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-service
>    Reporter: Sijie Guo
>Assignee: David Rusek
> Fix For: 0.4.0
>
>
> provide the ability to enable thriftmux on monitor service



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-87) Introduce periodic keepalive control record in writer

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-87.
-
Resolution: Fixed

> Introduce periodic keepalive control record in writer
> -
>
> Key: DL-87
> URL: https://issues.apache.org/jira/browse/DL-87
> Project: DistributedLog
>  Issue Type: New Feature
>        Reporter: Sijie Guo
>Assignee: Leigh Stewart
> Fix For: 0.4.0
>
>
> the writer will periodically write 'keepalive' control record to make sure 
> the stream is alive. so if the write proxy is disconnected from bookies, the 
> control record will fail to write hence write proxy gets a chance to drop the 
> ownership.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-88) remove watches when unregister children watches

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-88.
-
Resolution: Fixed

> remove watches when unregister children watches
> ---
>
> Key: DL-88
> URL: https://issues.apache.org/jira/browse/DL-88
> Project: DistributedLog
>  Issue Type: New Feature
>  Components: distributedlog-core
>    Reporter: Sijie Guo
>    Assignee: Sijie Guo
> Fix For: 0.4.0
>
>
> use the new zk removeWatches api to remove watchers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DL-122) Use assertions from Junit rather than assert() for tests

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-122.
--
   Resolution: Fixed
Fix Version/s: 0.4.0

[~boyork] thank you for your contribution.

> Use assertions from Junit rather than assert() for tests
> 
>
> Key: DL-122
> URL: https://issues.apache.org/jira/browse/DL-122
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-core
>Reporter: Gerrit Sundaram
>Assignee: Brennon York
> Fix For: 0.4.0
>
>
> there are too many places in test using 'assert()' rather than using 
> assertions from junit. it would be good that we can change that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (DL-28) generate java code failed using scrooge

[Sijie Guo (JIRA)]

[ 
https://issues.apache.org/jira/browse/DL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15765842#comment-15765842
 ] 

Sijie Guo commented on DL-28:
-

[~JoshuaAndrew] [~fonan] can you check if it addresses your issue?

> generate java code failed using scrooge
> ---
>
> Key: DL-28
> URL: https://issues.apache.org/jira/browse/DL-28
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-protocol
>Affects Versions: 0.4.0
> Environment: Apache Maven 3.2.5
> Maven home: C:\apache-maven-3.2.5
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: C:\Java\jdk1.8.0_60\jre
> Default locale: zh_CN, platform encoding: UTF-8
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
>Reporter: weiwei
>Assignee: Liang Xie
>Priority: Blocker
>  Labels: build
> Fix For: 0.4.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] distributedlog . SUCCESS [  0.002 
> s]
> [INFO] DistributedLog Protocol  FAILURE [  1.081 
> s]
> [INFO] DistributedLog Core Library  SKIPPED
> [INFO] DistributedLog Client .. SKIPPED
> [INFO] DistributedLog Service . SKIPPED
> [INFO] DistributedLog Benchmark ... SKIPPED
> [INFO] DistributedLog Example . SKIPPED
> [INFO] DistributedLog Basics .. SKIPPED
> [INFO] DistributedLog Messaging Tutorial .. SKIPPED
> [INFO] DistributedLog Kafka Tutorial .. SKIPPED
> [INFO] DistributedLog MapReduce ... SKIPPED
> [INFO] DistributedLog Tutorials ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.321 s
> [INFO] Finished at: 2016-08-02T13:26:31+08:00
> [INFO] Final Memory: 12M/150M
> [INFO] 
> 
> [ERROR] Exception parsing: 
> E:\incubator-distributedlog\distributedlog-protocol\src\main\thrift\service.thrift:
>  [3.1] failure: string matching regex `\z' expected but `/' found
> [ERROR] 
> [ERROR] // Response stats codes
> [ERROR] 
> [ERROR] ^
> [ERROR] -> [Help 1]
> com.twitter.scrooge.frontend.FileParseException: Exception parsing: 
> E:\isoftstone\workspacedeis\incubator-distributedlog\distributedlog-protocol\src\main\thrift\service.thrift
>   at 
> com.twitter.scrooge.frontend.ThriftParser$$anonfun$parse$1.apply(ThriftParser.scala:427)
>   at 
> com.twitter.scrooge.frontend.ThriftParser$$anonfun$parse$1.apply(ThriftParser.scala:427)
>   at scala.Option.map(Option.scala:145)
>   at 
> com.twitter.scrooge.frontend.ThriftParser.parse(ThriftParser.scala:420)
>   at 
> com.twitter.scrooge.frontend.ThriftParser.parseFile(ThriftParser.scala:448)
>   at com.twitter.scrooge.Compiler$$anonfun$run$2.apply(Compiler.scala:66)
>   at com.twitter.scrooge.Compiler$$anonfun$run$2.apply(Compiler.scala:64)
>   at scala.collection.immutable.List.foreach(List.scala:318)
>   at 
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:32)
>   at scala.collection.mutable.ListBuffer.foreach(ListBuffer.scala:45)
>   at com.twitter.scrooge.Compiler.run(Compiler.scala:64)
>   at com.twitter.ScroogeRunner.compile(ScroogeRunner.scala:45)
>   at 
> com.twitter.AbstractMavenScroogeMojo.execute(AbstractMavenScroogeMojo.java:239)
>   at 
> com.twitter.MavenScroogeCompileMojo.execute(MavenScroogeCompileMojo.java:22)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.mav

[jira] [Resolved] (DL-28) generate java code failed using scrooge

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved DL-28.
-
Resolution: Fixed

Thanks [~xieliang007] for the fix.

> generate java code failed using scrooge
> ---
>
> Key: DL-28
> URL: https://issues.apache.org/jira/browse/DL-28
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-protocol
>Affects Versions: 0.4.0
> Environment: Apache Maven 3.2.5
> Maven home: C:\apache-maven-3.2.5
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: C:\Java\jdk1.8.0_60\jre
> Default locale: zh_CN, platform encoding: UTF-8
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
>Reporter: weiwei
>Assignee: Liang Xie
>Priority: Blocker
>  Labels: build
> Fix For: 0.4.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] distributedlog . SUCCESS [  0.002 
> s]
> [INFO] DistributedLog Protocol  FAILURE [  1.081 
> s]
> [INFO] DistributedLog Core Library  SKIPPED
> [INFO] DistributedLog Client .. SKIPPED
> [INFO] DistributedLog Service . SKIPPED
> [INFO] DistributedLog Benchmark ... SKIPPED
> [INFO] DistributedLog Example . SKIPPED
> [INFO] DistributedLog Basics .. SKIPPED
> [INFO] DistributedLog Messaging Tutorial .. SKIPPED
> [INFO] DistributedLog Kafka Tutorial .. SKIPPED
> [INFO] DistributedLog MapReduce ... SKIPPED
> [INFO] DistributedLog Tutorials ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.321 s
> [INFO] Finished at: 2016-08-02T13:26:31+08:00
> [INFO] Final Memory: 12M/150M
> [INFO] 
> 
> [ERROR] Exception parsing: 
> E:\incubator-distributedlog\distributedlog-protocol\src\main\thrift\service.thrift:
>  [3.1] failure: string matching regex `\z' expected but `/' found
> [ERROR] 
> [ERROR] // Response stats codes
> [ERROR] 
> [ERROR] ^
> [ERROR] -> [Help 1]
> com.twitter.scrooge.frontend.FileParseException: Exception parsing: 
> E:\isoftstone\workspacedeis\incubator-distributedlog\distributedlog-protocol\src\main\thrift\service.thrift
>   at 
> com.twitter.scrooge.frontend.ThriftParser$$anonfun$parse$1.apply(ThriftParser.scala:427)
>   at 
> com.twitter.scrooge.frontend.ThriftParser$$anonfun$parse$1.apply(ThriftParser.scala:427)
>   at scala.Option.map(Option.scala:145)
>   at 
> com.twitter.scrooge.frontend.ThriftParser.parse(ThriftParser.scala:420)
>   at 
> com.twitter.scrooge.frontend.ThriftParser.parseFile(ThriftParser.scala:448)
>   at com.twitter.scrooge.Compiler$$anonfun$run$2.apply(Compiler.scala:66)
>   at com.twitter.scrooge.Compiler$$anonfun$run$2.apply(Compiler.scala:64)
>   at scala.collection.immutable.List.foreach(List.scala:318)
>   at 
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:32)
>   at scala.collection.mutable.ListBuffer.foreach(ListBuffer.scala:45)
>   at com.twitter.scrooge.Compiler.run(Compiler.scala:64)
>   at com.twitter.ScroogeRunner.compile(ScroogeRunner.scala:45)
>   at 
> com.twitter.AbstractMavenScroogeMojo.execute(AbstractMavenScroogeMojo.java:239)
>   at 
> com.twitter.MavenScroogeCompileMojo.execute(MavenScroogeCompileMojo.java:22)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.

[jira] [Updated] (DL-28) generate java code failed using scrooge

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated DL-28:

Assignee: Liang Xie  (was: Sijie Guo)

> generate java code failed using scrooge
> ---
>
> Key: DL-28
> URL: https://issues.apache.org/jira/browse/DL-28
> Project: DistributedLog
>  Issue Type: Bug
>  Components: distributedlog-protocol
>Affects Versions: 0.4.0
> Environment: Apache Maven 3.2.5
> Maven home: C:\apache-maven-3.2.5
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: C:\Java\jdk1.8.0_60\jre
> Default locale: zh_CN, platform encoding: UTF-8
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
>Reporter: weiwei
>Assignee: Liang Xie
>Priority: Blocker
>  Labels: build
> Fix For: 0.4.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] distributedlog . SUCCESS [  0.002 
> s]
> [INFO] DistributedLog Protocol  FAILURE [  1.081 
> s]
> [INFO] DistributedLog Core Library  SKIPPED
> [INFO] DistributedLog Client .. SKIPPED
> [INFO] DistributedLog Service . SKIPPED
> [INFO] DistributedLog Benchmark ... SKIPPED
> [INFO] DistributedLog Example . SKIPPED
> [INFO] DistributedLog Basics .. SKIPPED
> [INFO] DistributedLog Messaging Tutorial .. SKIPPED
> [INFO] DistributedLog Kafka Tutorial .. SKIPPED
> [INFO] DistributedLog MapReduce ... SKIPPED
> [INFO] DistributedLog Tutorials ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 1.321 s
> [INFO] Finished at: 2016-08-02T13:26:31+08:00
> [INFO] Final Memory: 12M/150M
> [INFO] 
> 
> [ERROR] Exception parsing: 
> E:\incubator-distributedlog\distributedlog-protocol\src\main\thrift\service.thrift:
>  [3.1] failure: string matching regex `\z' expected but `/' found
> [ERROR] 
> [ERROR] // Response stats codes
> [ERROR] 
> [ERROR] ^
> [ERROR] -> [Help 1]
> com.twitter.scrooge.frontend.FileParseException: Exception parsing: 
> E:\isoftstone\workspacedeis\incubator-distributedlog\distributedlog-protocol\src\main\thrift\service.thrift
>   at 
> com.twitter.scrooge.frontend.ThriftParser$$anonfun$parse$1.apply(ThriftParser.scala:427)
>   at 
> com.twitter.scrooge.frontend.ThriftParser$$anonfun$parse$1.apply(ThriftParser.scala:427)
>   at scala.Option.map(Option.scala:145)
>   at 
> com.twitter.scrooge.frontend.ThriftParser.parse(ThriftParser.scala:420)
>   at 
> com.twitter.scrooge.frontend.ThriftParser.parseFile(ThriftParser.scala:448)
>   at com.twitter.scrooge.Compiler$$anonfun$run$2.apply(Compiler.scala:66)
>   at com.twitter.scrooge.Compiler$$anonfun$run$2.apply(Compiler.scala:64)
>   at scala.collection.immutable.List.foreach(List.scala:318)
>   at 
> scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:32)
>   at scala.collection.mutable.ListBuffer.foreach(ListBuffer.scala:45)
>   at com.twitter.scrooge.Compiler.run(Compiler.scala:64)
>   at com.twitter.ScroogeRunner.compile(ScroogeRunner.scala:45)
>   at 
> com.twitter.AbstractMavenScroogeMojo.execute(AbstractMavenScroogeMojo.java:239)
>   at 
> com.twitter.MavenScroogeCompileMojo.execute(MavenScroogeCompileMojo.java:22)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build

[jira] [Closed] (DL-126) Fix the url of distributedlog blog post

[Sijie Guo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/DL-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo closed DL-126.

Resolution: Fixed

> Fix the url of distributedlog blog post
> ---
>
> Key: DL-126
> URL: https://issues.apache.org/jira/browse/DL-126
> Project: DistributedLog
>  Issue Type: Bug
>  Components: website
>    Reporter: Sijie Guo
>    Assignee: Sijie Guo
> Fix For: 0.4.0
>
>
> The URL states 2015. It should be 2016.
> http://distributedlog.incubator.apache.org/technical-review/2015/09/19/kafka-vs-distributedlog



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)