Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

2016-08-01 Thread Julian Hyde 

> On Aug 1, 2016, at 5:24 PM, Navina Ramesh  
> wrote:
> 
> Are you referring to the Gemfile.lock in docs/ ? I do see that in the
> source release.

I was mistaken. Apparently it is OK to check in Gemfile.lock; see 
http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/
 
.

Julian

Re: Review Request 50682: SAMZA-993 Fix logging bug for some scala versions

2016-08-01 Thread Fred Ji 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/#review144420
---


Ship it!




Ship It!

- Fred Ji


On Aug. 2, 2016, 12:13 a.m., Jake Maes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50682/
> ---
> 
> (Updated Aug. 2, 2016, 12:13 a.m.)
> 
> 
> Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes, 
> Navina Ramesh, Jagadish Venkatraman, Xinyu Liu, and Yi Pan (Data 
> Infrastructure).
> 
> 
> Bugs: SAMZA-993
> https://issues.apache.org/jira/browse/SAMZA-993
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> SAMZA-993 Fix logging bug for some scala versions
> 
> 
> Diffs
> -
> 
>   samza-core/src/main/scala/org/apache/samza/util/Logging.scala 
> 9a4ed897d58e90d61fdde14dd51ac5ba2d9edd36 
> 
> Diff: https://reviews.apache.org/r/50682/diff/
> 
> 
> Testing
> ---
> 
> Running checkall now...
> 
> 
> Thanks,
> 
> Jake Maes
> 
>

Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

2016-08-01 Thread Navina Ramesh 
Ok. I added my keys to the KEYS file.

@Julian: Thanks for the suggestion. I don't know the reason for choosing
home.apache.org as opposed to dist.apache.org. The latter does make more
sense. We will update the release procedure for 0.11.0.

Are you referring to the Gemfile.lock in docs/ ? I do see that in the
source release.

Navina

On Mon, Aug 1, 2016 at 3:55 PM, Yi Pan  wrote:

> Hi, Navina,
>
> Yes. You should put your key in the KEYS file.
>
> And +1 (binding) as I built and ran the zopkio integration test
> successfully as well.
>
> On Mon, Aug 1, 2016 at 1:05 PM, Navina Ramesh  >
> wrote:
>
> > @Garry: Yeah. I wasn't very clear about it either.
> >
> > @Yi: Do you know if it is a part of the release process to add my keys to
> > the KEYS file in git repo?
> >
> >
> > Navina
> >
> > On Mon, Aug 1, 2016 at 12:47 PM, Garry Turkington <
> > g.turking...@improvedigital.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Built the source ran all tests and tried a sample test job. All looks
> > good.
> > >
> > > One question - the key used to sign isn't in the KEYS file in the git
> > repo
> > > -- is this a convenieence mechanism or  does the release process mean
> it
> > > should be there?
> > >
> > > Garry
> > >
> > > -Original Message-
> > > From: Jacob Maes [mailto:jacob.m...@gmail.com]
> > > Sent: Monday, August 01, 2016 7:45 PM
> > > To: dev@samza.apache.org
> > > Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
> > >
> > > +1 non-binding
> > > Lots of good fixes in this release.
> > >
> > > On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman <
> > > jagadish1...@gmail.com> wrote:
> > >
> > > > Thanks for driving this release.+1 approve (non-binding)
> > > >
> > > > Thanks,
> > > > Jagadish
> > > >
> > > > On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
> > > >  > > > > wrote:
> > > >
> > > > > Hey all,
> > > > >
> > > > > This is a call for a vote on a release of Apache Samza 0.10.0.
> > > > > Thanks to everyone who has contributed to this release. We are very
> > > > > glad to see some new contributors in this release.
> > > > >
> > > > > **NOTE**: This release is primarily a bug-fix release with no major
> > > > changes
> > > > > to the public api. Since we are behind schedule in terms of
> > > > > releases, we are combining the DISCUSS and VOTE email into a single
> > > > > VOTE email. If anyone has objections, please do raise them. We plan
> > > > > to shortly follow-up with a DISCUSS email for 0.11.0 release, that
> > > > > brings in new features in multi-threading, REST api etc.
> > > > >
> > > > >
> > > > > The release candidate can be downloaded from here:
> > > > > http://home.apache.org/~navina/samza-0.10.1-rc0/
> > > > >
> > > > >
> > > > > The release candidate is signed with pgp key 331C8F69, which can be
> > > > > found on keyservers:
> > > > > http://pgp.mit.edu/pks/lookup?op=get=0x331C8F69
> > > > >
> > > > >
> > > > > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > > > > *
> > > > >
> > > >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> > > > eb2dc1dbffc661f910b1272b233640
> > > > > <
> > > > >
> > > >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> > > > eb2dc1dbffc661f910b1272b233640
> > > > > >*
> > > > >
> > > > >
> > > > > Test binaries have been published to Maven's staging repository,
> and
> > > > > are available
> > > > > here:
> > > > >
> https://repository.apache.org/content/repositories/orgapachesamza-10
> > > > > 12/
> > > > >
> > > > >
> > > > > Note that the binaries were built with JDK7 without incident.
> > > > >
> > > > > 69 issues were resolved for this release:
> > > > >
> > > > >
> > > >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND
> > > >
> %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Clo
> > > > sed)
> > > > >
> > > > >
> > > > > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> > > > > 08/05/2016
> > > > ).
> > > > >
> > > > >
> > > > > Please download the release candidate, check the hashes/signature,
> > > > > build it and test it, and then please vote:
> > > > >
> > > > >
> > > > > [ ] +1 approve
> > > > >
> > > > > [ ] +0 no opinion
> > > > >
> > > > > [ ] -1 disapprove (and reason why)
> > > > >
> > > > >
> > > > > +1 from my side for the release.
> > > > >
> > > > > Cheers!
> > > > > --
> > > > > Navina R.
> > > > > nav...@apache.org
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Jagadish V,
> > > > Graduate Student,
> > > > Department of Computer Science,
> > > > Stanford University
> > > >
> > >
> > > -
> > > No virus found in this message.
> > > Checked by AVG - www.avg.com
> > > Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date:
> > 07/27/16
> > >
> >
> >
> >
> > --
> > Navina R.
> >
>



-- 
Navina R.

Re: Review Request 50682: SAMZA-993 Fix logging bug for some scala versions

2016-08-01 Thread Xinyu Liu 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/#review144417
---


Ship it!




+1. thanks for the quick fix!

- Xinyu Liu


On Aug. 2, 2016, 12:13 a.m., Jake Maes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50682/
> ---
> 
> (Updated Aug. 2, 2016, 12:13 a.m.)
> 
> 
> Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes, 
> Navina Ramesh, Jagadish Venkatraman, Xinyu Liu, and Yi Pan (Data 
> Infrastructure).
> 
> 
> Bugs: SAMZA-993
> https://issues.apache.org/jira/browse/SAMZA-993
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> SAMZA-993 Fix logging bug for some scala versions
> 
> 
> Diffs
> -
> 
>   samza-core/src/main/scala/org/apache/samza/util/Logging.scala 
> 9a4ed897d58e90d61fdde14dd51ac5ba2d9edd36 
> 
> Diff: https://reviews.apache.org/r/50682/diff/
> 
> 
> Testing
> ---
> 
> Running checkall now...
> 
> 
> Thanks,
> 
> Jake Maes
> 
>

Re: Review Request 50682: SAMZA-993 Fix logging bug for some scala versions

2016-08-01 Thread Navina Ramesh 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/#review144414
---


Ship it!




Ship It!

- Navina Ramesh


On Aug. 2, 2016, 12:13 a.m., Jake Maes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50682/
> ---
> 
> (Updated Aug. 2, 2016, 12:13 a.m.)
> 
> 
> Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes, 
> Navina Ramesh, Jagadish Venkatraman, Xinyu Liu, and Yi Pan (Data 
> Infrastructure).
> 
> 
> Bugs: SAMZA-993
> https://issues.apache.org/jira/browse/SAMZA-993
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> SAMZA-993 Fix logging bug for some scala versions
> 
> 
> Diffs
> -
> 
>   samza-core/src/main/scala/org/apache/samza/util/Logging.scala 
> 9a4ed897d58e90d61fdde14dd51ac5ba2d9edd36 
> 
> Diff: https://reviews.apache.org/r/50682/diff/
> 
> 
> Testing
> ---
> 
> Running checkall now...
> 
> 
> Thanks,
> 
> Jake Maes
> 
>

Review Request 50682: SAMZA-993 Fix logging bug for some scala versions

2016-08-01 Thread Jake Maes 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50682/
---

Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes, 
Navina Ramesh, Jagadish Venkatraman, Xinyu Liu, and Yi Pan (Data 
Infrastructure).


Bugs: SAMZA-993
https://issues.apache.org/jira/browse/SAMZA-993


Repository: samza


Description
---

SAMZA-993 Fix logging bug for some scala versions


Diffs
-

  samza-core/src/main/scala/org/apache/samza/util/Logging.scala 
9a4ed897d58e90d61fdde14dd51ac5ba2d9edd36 

Diff: https://reviews.apache.org/r/50682/diff/


Testing
---

Running checkall now...


Thanks,

Jake Maes

Re: Review Request 50670: SAMZA-991: Continue to report SamzaAppMasterMetrics

2016-08-01 Thread Jagadish Venkatraman 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/
---

(Updated Aug. 1, 2016, 11:29 p.m.)


Review request for samza, Yi Pan (Data Infrastructure), Navina Ramesh, and 
Xinyu Liu.


Repository: samza


Description
---

As a part of the AM-JC refactoring, we took out some metrics from 
SamzaAppMasterMetrics and moved them to samza-core. However, for existing jobs 
that rely on metrics for their monitoring/alerting, changing metric-names may 
break the jobs.

This change ensures that we still report basic metrics like failed containers, 
running containers, job health from Samza yarn for backwards-compat reasons.


Diffs
-

  
samza-yarn/src/main/java/org/apache/samza/job/yarn/YarnClusterResourceManager.java
 1fac7f4e656be2d83f7448a1ae498ffe32f6f6db 
  
samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterMetrics.scala 
PRE-CREATION 

Diff: https://reviews.apache.org/r/50670/diff/


Testing (updated)
---

1. Build succeeds and unit tests pass.
2. Verified with a sample test job that metrics were actually flowing using 
JvisualVM.


Thanks,

Jagadish Venkatraman

Re: Review Request 50670: SAMZA-991: Continue to report SamzaAppMasterMetrics

2016-08-01 Thread Xinyu Liu 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/#review144393
---


Ship it!




+1

- Xinyu Liu


On Aug. 1, 2016, 10:21 p.m., Jagadish Venkatraman wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50670/
> ---
> 
> (Updated Aug. 1, 2016, 10:21 p.m.)
> 
> 
> Review request for samza, Yi Pan (Data Infrastructure), Navina Ramesh, and 
> Xinyu Liu.
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> As a part of the AM-JC refactoring, we took out some metrics from 
> SamzaAppMasterMetrics and moved them to samza-core. However, for existing 
> jobs that rely on metrics for their monitoring/alerting, changing 
> metric-names may break the jobs.
> 
> This change ensures that we still report basic metrics like failed 
> containers, running containers, job health from Samza yarn for 
> backwards-compat reasons.
> 
> 
> Diffs
> -
> 
>   
> samza-yarn/src/main/java/org/apache/samza/job/yarn/YarnClusterResourceManager.java
>  1fac7f4e656be2d83f7448a1ae498ffe32f6f6db 
>   
> samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterMetrics.scala
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/50670/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Jagadish Venkatraman
> 
>

Re: Review Request 50670: SAMZA-991: Continue to report SamzaAppMasterMetrics

2016-08-01 Thread Jagadish Venkatraman 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/#review144391
---




samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterMetrics.scala 
(line 78)


Good point, fixed this one! (The SamzaContainer however, does not run on 
the same process as the SamzaAppMaster.)


- Jagadish Venkatraman


On Aug. 1, 2016, 9:07 p.m., Jagadish Venkatraman wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50670/
> ---
> 
> (Updated Aug. 1, 2016, 9:07 p.m.)
> 
> 
> Review request for samza, Yi Pan (Data Infrastructure), Navina Ramesh, and 
> Xinyu Liu.
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> As a part of the AM-JC refactoring, we took out some metrics from 
> SamzaAppMasterMetrics and moved them to samza-core. However, for existing 
> jobs that rely on metrics for their monitoring/alerting, changing 
> metric-names may break the jobs.
> 
> This change ensures that we still report basic metrics like failed 
> containers, running containers, job health from Samza yarn for 
> backwards-compat reasons.
> 
> 
> Diffs
> -
> 
>   
> samza-yarn/src/main/java/org/apache/samza/job/yarn/YarnClusterResourceManager.java
>  1fac7f4e656be2d83f7448a1ae498ffe32f6f6db 
>   
> samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterMetrics.scala
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/50670/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Jagadish Venkatraman
> 
>

Re: Review Request 50670: SAMZA-991: Continue to report SamzaAppMasterMetrics

2016-08-01 Thread Jagadish Venkatraman 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/
---

(Updated Aug. 1, 2016, 10:21 p.m.)


Review request for samza, Yi Pan (Data Infrastructure), Navina Ramesh, and 
Xinyu Liu.


Changes
---

address Xinyu's review feedback.


Repository: samza


Description
---

As a part of the AM-JC refactoring, we took out some metrics from 
SamzaAppMasterMetrics and moved them to samza-core. However, for existing jobs 
that rely on metrics for their monitoring/alerting, changing metric-names may 
break the jobs.

This change ensures that we still report basic metrics like failed containers, 
running containers, job health from Samza yarn for backwards-compat reasons.


Diffs (updated)
-

  
samza-yarn/src/main/java/org/apache/samza/job/yarn/YarnClusterResourceManager.java
 1fac7f4e656be2d83f7448a1ae498ffe32f6f6db 
  
samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterMetrics.scala 
PRE-CREATION 

Diff: https://reviews.apache.org/r/50670/diff/


Testing
---


Thanks,

Jagadish Venkatraman

Re: Review Request 50670: SAMZA-991: Continue to report SamzaAppMasterMetrics

2016-08-01 Thread Xinyu Liu 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/#review144387
---




samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterMetrics.scala 
(line 78)


Seems jvm is started here again (see it in some other  refactored code)

btw, seems Jvm metrics is also started in SamzaContainer. Do we run 
mulitple jvm stats? It might have some performance implications. Could you 
please take a look? Thanks.


- Xinyu Liu


On Aug. 1, 2016, 9:07 p.m., Jagadish Venkatraman wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50670/
> ---
> 
> (Updated Aug. 1, 2016, 9:07 p.m.)
> 
> 
> Review request for samza, Yi Pan (Data Infrastructure), Navina Ramesh, and 
> Xinyu Liu.
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> As a part of the AM-JC refactoring, we took out some metrics from 
> SamzaAppMasterMetrics and moved them to samza-core. However, for existing 
> jobs that rely on metrics for their monitoring/alerting, changing 
> metric-names may break the jobs.
> 
> This change ensures that we still report basic metrics like failed 
> containers, running containers, job health from Samza yarn for 
> backwards-compat reasons.
> 
> 
> Diffs
> -
> 
>   
> samza-yarn/src/main/java/org/apache/samza/job/yarn/YarnClusterResourceManager.java
>  1fac7f4e656be2d83f7448a1ae498ffe32f6f6db 
>   
> samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterMetrics.scala
>  PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/50670/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Jagadish Venkatraman
> 
>

Review Request 50670: SAMZA-991: Continue to report SamzaAppMasterMetrics

2016-08-01 Thread Jagadish Venkatraman 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50670/
---

Review request for samza, Yi Pan (Data Infrastructure), Navina Ramesh, and 
Xinyu Liu.


Repository: samza


Description
---

As a part of the AM-JC refactoring, we took out some metrics from 
SamzaAppMasterMetrics and moved them to samza-core. However, for existing jobs 
that rely on metrics for their monitoring/alerting, changing metric-names may 
break the jobs.

This change ensures that we still report basic metrics like failed containers, 
running containers, job health from Samza yarn for backwards-compat reasons.


Diffs
-

  
samza-yarn/src/main/java/org/apache/samza/job/yarn/YarnClusterResourceManager.java
 1fac7f4e656be2d83f7448a1ae498ffe32f6f6db 
  
samza-yarn/src/main/scala/org/apache/samza/job/yarn/SamzaAppMasterMetrics.scala 
PRE-CREATION 

Diff: https://reviews.apache.org/r/50670/diff/


Testing
---


Thanks,

Jagadish Venkatraman

Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

2016-08-01 Thread Julian Hyde 
+1 (non-binding)

Downloaded, built, ran tests, checked L Instructions on installing gradle 
were nice and clear.

I ran rat (I presume that ‘./gradlew rat’ is the correct command) and it passed.

I believe that best practice is to put the release bits under 
https://dist.apache.org/repos/dist/dev/${project}/${release} 
 rather 
than under home.apache.org . I suggest that Samza 
follows this for future releases.

The best place to put KEYS is 
https://dist.apache.org/repos/dist/dev/${project}/KEYS 
, not in git 
(because git can be subverted).

Should Gemfile.lock be in the release? Isn’t it a generated file?

Julian


> On Aug 1, 2016, at 1:05 PM, Navina Ramesh  
> wrote:
> 
> @Garry: Yeah. I wasn't very clear about it either.
> 
> @Yi: Do you know if it is a part of the release process to add my keys to
> the KEYS file in git repo?
> 
> 
> Navina
> 
> On Mon, Aug 1, 2016 at 12:47 PM, Garry Turkington <
> g.turking...@improvedigital.com> wrote:
> 
>> +1 (binding)
>> 
>> Built the source ran all tests and tried a sample test job. All looks good.
>> 
>> One question - the key used to sign isn't in the KEYS file in the git repo
>> -- is this a convenieence mechanism or  does the release process mean it
>> should be there?
>> 
>> Garry
>> 
>> -Original Message-
>> From: Jacob Maes [mailto:jacob.m...@gmail.com]
>> Sent: Monday, August 01, 2016 7:45 PM
>> To: dev@samza.apache.org
>> Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
>> 
>> +1 non-binding
>> Lots of good fixes in this release.
>> 
>> On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman <
>> jagadish1...@gmail.com> wrote:
>> 
>>> Thanks for driving this release.+1 approve (non-binding)
>>> 
>>> Thanks,
>>> Jagadish
>>> 
>>> On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
>>> >> 
 Hey all,
 
 This is a call for a vote on a release of Apache Samza 0.10.0.
 Thanks to everyone who has contributed to this release. We are very
 glad to see some new contributors in this release.
 
 **NOTE**: This release is primarily a bug-fix release with no major
>>> changes
 to the public api. Since we are behind schedule in terms of
 releases, we are combining the DISCUSS and VOTE email into a single
 VOTE email. If anyone has objections, please do raise them. We plan
 to shortly follow-up with a DISCUSS email for 0.11.0 release, that
 brings in new features in multi-threading, REST api etc.
 
 
 The release candidate can be downloaded from here:
 http://home.apache.org/~navina/samza-0.10.1-rc0/
 
 
 The release candidate is signed with pgp key 331C8F69, which can be
 found on keyservers:
 http://pgp.mit.edu/pks/lookup?op=get=0x331C8F69
 
 
 The git tag is release-0.10.1-rc0 and signed with the same pgp key:
 *
 
>>> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
>>> eb2dc1dbffc661f910b1272b233640
 <
 
>>> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
>>> eb2dc1dbffc661f910b1272b233640
> *
 
 
 Test binaries have been published to Maven's staging repository, and
 are available
 here:
 https://repository.apache.org/content/repositories/orgapachesamza-10
 12/
 
 
 Note that the binaries were built with JDK7 without incident.
 
 69 issues were resolved for this release:
 
 
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND
>>> %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Clo
>>> sed)
 
 
 The vote will be open for 72 hours ( end in 12:00pm Thursday,
 08/05/2016
>>> ).
 
 
 Please download the release candidate, check the hashes/signature,
 build it and test it, and then please vote:
 
 
 [ ] +1 approve
 
 [ ] +0 no opinion
 
 [ ] -1 disapprove (and reason why)
 
 
 +1 from my side for the release.
 
 Cheers!
 --
 Navina R.
 nav...@apache.org
 
>>> 
>>> 
>>> 
>>> --
>>> Jagadish V,
>>> Graduate Student,
>>> Department of Computer Science,
>>> Stanford University
>>> 
>> 
>> -
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date: 07/27/16
>> 
> 
> 
> 
> -- 
> Navina R.

RE: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

2016-08-01 Thread Garry Turkington 
This link seems to say the KEYS file needs be in the  distribution directory on 
the Apache master site but not necessarily inside each released artifact. Which 
suggests the release process should ensure the signing key is in the publically 
accessible KEYS file. I guess its then a question of if we plan to version 
control that by keeping the master copy in the git root of master.

http://www.apache.org/dev/release-distribution.html#sigs-and-sums

Garry

-Original Message-
From: Navina Ramesh [mailto:nram...@linkedin.com.INVALID] 
Sent: Monday, August 01, 2016 9:05 PM
To: dev@samza.apache.org
Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

@Garry: Yeah. I wasn't very clear about it either.

@Yi: Do you know if it is a part of the release process to add my keys to the 
KEYS file in git repo?


Navina

On Mon, Aug 1, 2016 at 12:47 PM, Garry Turkington < 
g.turking...@improvedigital.com> wrote:

> +1 (binding)
>
> Built the source ran all tests and tried a sample test job. All looks good.
>
> One question - the key used to sign isn't in the KEYS file in the git 
> repo
> -- is this a convenieence mechanism or  does the release process mean 
> it should be there?
>
> Garry
>
> -Original Message-
> From: Jacob Maes [mailto:jacob.m...@gmail.com]
> Sent: Monday, August 01, 2016 7:45 PM
> To: dev@samza.apache.org
> Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0
>
> +1 non-binding
> Lots of good fixes in this release.
>
> On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman < 
> jagadish1...@gmail.com> wrote:
>
> > Thanks for driving this release.+1 approve (non-binding)
> >
> > Thanks,
> > Jagadish
> >
> > On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh 
> >  > > wrote:
> >
> > > Hey all,
> > >
> > > This is a call for a vote on a release of Apache Samza 0.10.0.
> > > Thanks to everyone who has contributed to this release. We are 
> > > very glad to see some new contributors in this release.
> > >
> > > **NOTE**: This release is primarily a bug-fix release with no 
> > > major
> > changes
> > > to the public api. Since we are behind schedule in terms of 
> > > releases, we are combining the DISCUSS and VOTE email into a 
> > > single VOTE email. If anyone has objections, please do raise them. 
> > > We plan to shortly follow-up with a DISCUSS email for 0.11.0 
> > > release, that brings in new features in multi-threading, REST api etc.
> > >
> > >
> > > The release candidate can be downloaded from here:
> > > http://home.apache.org/~navina/samza-0.10.1-rc0/
> > >
> > >
> > > The release candidate is signed with pgp key 331C8F69, which can 
> > > be found on keyservers:
> > > http://pgp.mit.edu/pks/lookup?op=get=0x331C8F69
> > >
> > >
> > > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > > *
> > >
> > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3
> > e1
> > eb2dc1dbffc661f910b1272b233640
> > > <
> > >
> > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3
> > e1
> > eb2dc1dbffc661f910b1272b233640
> > > >*
> > >
> > >
> > > Test binaries have been published to Maven's staging repository, 
> > > and are available
> > > here:
> > > https://repository.apache.org/content/repositories/orgapachesamza-
> > > 10
> > > 12/
> > >
> > >
> > > Note that the binaries were built with JDK7 without incident.
> > >
> > > 69 issues were resolved for this release:
> > >
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20A
> > ND 
> > %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20C
> > lo
> > sed)
> > >
> > >
> > > The vote will be open for 72 hours ( end in 12:00pm Thursday,
> > > 08/05/2016
> > ).
> > >
> > >
> > > Please download the release candidate, check the hashes/signature, 
> > > build it and test it, and then please vote:
> > >
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove (and reason why)
> > >
> > >
> > > +1 from my side for the release.
> > >
> > > Cheers!
> > > --
> > > Navina R.
> > > nav...@apache.org
> > >
> >
> >
> >
> > --
> > Jagadish V,
> > Graduate Student,
> > Department of Computer Science,
> > Stanford University
> >
>
> -
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date: 
> 07/27/16
>



--
Navina R.

-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date: 07/27/16

RE: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

2016-08-01 Thread Garry Turkington 
+1 (binding)

Built the source ran all tests and tried a sample test job. All looks good.

One question - the key used to sign isn't in the KEYS file in the git repo -- 
is this a convenieence mechanism or  does the release process mean it should be 
there?

Garry

-Original Message-
From: Jacob Maes [mailto:jacob.m...@gmail.com] 
Sent: Monday, August 01, 2016 7:45 PM
To: dev@samza.apache.org
Subject: Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

+1 non-binding
Lots of good fixes in this release.

On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman < jagadish1...@gmail.com> 
wrote:

> Thanks for driving this release.+1 approve (non-binding)
>
> Thanks,
> Jagadish
>
> On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh 
>  > wrote:
>
> > Hey all,
> >
> > This is a call for a vote on a release of Apache Samza 0.10.0. 
> > Thanks to everyone who has contributed to this release. We are very 
> > glad to see some new contributors in this release.
> >
> > **NOTE**: This release is primarily a bug-fix release with no major
> changes
> > to the public api. Since we are behind schedule in terms of 
> > releases, we are combining the DISCUSS and VOTE email into a single 
> > VOTE email. If anyone has objections, please do raise them. We plan 
> > to shortly follow-up with a DISCUSS email for 0.11.0 release, that 
> > brings in new features in multi-threading, REST api etc.
> >
> >
> > The release candidate can be downloaded from here:
> > http://home.apache.org/~navina/samza-0.10.1-rc0/
> >
> >
> > The release candidate is signed with pgp key 331C8F69, which can be 
> > found on keyservers:
> > http://pgp.mit.edu/pks/lookup?op=get=0x331C8F69
> >
> >
> > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > *
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> eb2dc1dbffc661f910b1272b233640
> > <
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1
> eb2dc1dbffc661f910b1272b233640
> > >*
> >
> >
> > Test binaries have been published to Maven's staging repository, and 
> > are available
> > here:
> > https://repository.apache.org/content/repositories/orgapachesamza-10
> > 12/
> >
> >
> > Note that the binaries were built with JDK7 without incident.
> >
> > 69 issues were resolved for this release:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND
> %20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Clo
> sed)
> >
> >
> > The vote will be open for 72 hours ( end in 12:00pm Thursday, 
> > 08/05/2016
> ).
> >
> >
> > Please download the release candidate, check the hashes/signature, 
> > build it and test it, and then please vote:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> > +1 from my side for the release.
> >
> > Cheers!
> > --
> > Navina R.
> > nav...@apache.org
> >
>
>
>
> --
> Jagadish V,
> Graduate Student,
> Department of Computer Science,
> Stanford University
>

-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7688 / Virus Database: 4627/12695 - Release Date: 07/27/16

Re: Review Request 50667: SAMZA-989 - Update hello-samza to use the startup logger

2016-08-01 Thread Yi Pan (Data Infrastructure) 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50667/#review144372
---


Ship it!




Ship It!

- Yi Pan (Data Infrastructure)


On Aug. 1, 2016, 6:53 p.m., Jake Maes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50667/
> ---
> 
> (Updated Aug. 1, 2016, 6:53 p.m.)
> 
> 
> Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes, 
> Navina Ramesh, Jagadish Venkatraman, Xinyu Liu, and Yi Pan (Data 
> Infrastructure).
> 
> 
> Bugs: SAMZA-989
> https://issues.apache.org/jira/browse/SAMZA-989
> 
> 
> Repository: samza-hello-samza
> 
> 
> Description
> ---
> 
> SAMZA-989 - Update hello-samza to use the startup logger
> 
> 
> Diffs
> -
> 
>   src/main/resources/log4j.xml 818135ddb15286c998378cebd32154bd29cf2cf8 
> 
> Diff: https://reviews.apache.org/r/50667/diff/
> 
> 
> Testing
> ---
> 
> Tested by manually deploying the job and inspecting the logs
> 
> 
> Thanks,
> 
> Jake Maes
> 
>

Review Request 50667: SAMZA-989 - Update hello-samza to use the startup logger

2016-08-01 Thread Jake Maes 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50667/
---

Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes, 
Navina Ramesh, Jagadish Venkatraman, Xinyu Liu, and Yi Pan (Data 
Infrastructure).


Bugs: SAMZA-989
https://issues.apache.org/jira/browse/SAMZA-989


Repository: samza-hello-samza


Description
---

SAMZA-989 - Update hello-samza to use the startup logger


Diffs
-

  src/main/resources/log4j.xml 818135ddb15286c998378cebd32154bd29cf2cf8 

Diff: https://reviews.apache.org/r/50667/diff/


Testing
---

Tested by manually deploying the job and inspecting the logs


Thanks,

Jake Maes

Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

2016-08-01 Thread Jacob Maes 
+1 non-binding
Lots of good fixes in this release.

On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman <
jagadish1...@gmail.com> wrote:

> Thanks for driving this release.+1 approve (non-binding)
>
> Thanks,
> Jagadish
>
> On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
>  > wrote:
>
> > Hey all,
> >
> > This is a call for a vote on a release of Apache Samza 0.10.0. Thanks
> > to everyone
> > who has contributed to this release. We are very glad to see some new
> > contributors in this release.
> >
> > **NOTE**: This release is primarily a bug-fix release with no major
> changes
> > to the public api. Since we are behind schedule in terms of releases, we
> > are combining the DISCUSS and VOTE email into a single VOTE email. If
> > anyone has objections, please do raise them. We plan to shortly follow-up
> > with a DISCUSS email for 0.11.0 release, that brings in new features in
> > multi-threading, REST api etc.
> >
> >
> > The release candidate can be downloaded from here:
> > http://home.apache.org/~navina/samza-0.10.1-rc0/
> >
> >
> > The release candidate is signed with pgp key 331C8F69, which can be found
> > on keyservers:
> > http://pgp.mit.edu/pks/lookup?op=get=0x331C8F69
> >
> >
> > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > *
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > <
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > >*
> >
> >
> > Test binaries have been published to Maven's staging repository, and
> > are available
> > here:
> > https://repository.apache.org/content/repositories/orgapachesamza-1012/
> >
> >
> > Note that the binaries were built with JDK7 without incident.
> >
> > 69 issues were resolved for this release:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Closed)
> >
> >
> > The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016
> ).
> >
> >
> > Please download the release candidate, check the hashes/signature, build
> > it and
> > test it, and then please vote:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> > +1 from my side for the release.
> >
> > Cheers!
> > --
> > Navina R.
> > nav...@apache.org
> >
>
>
>
> --
> Jagadish V,
> Graduate Student,
> Department of Computer Science,
> Stanford University
>

Re: [DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

2016-08-01 Thread xinyu liu 
+1 (non-binding).

Thanks,
Xinyu

On Mon, Aug 1, 2016 at 11:41 AM, Jagadish Venkatraman <
jagadish1...@gmail.com> wrote:

> Thanks for driving this release.+1 approve (non-binding)
>
> Thanks,
> Jagadish
>
> On Mon, Aug 1, 2016 at 11:39 AM, Navina Ramesh
>  > wrote:
>
> > Hey all,
> >
> > This is a call for a vote on a release of Apache Samza 0.10.0. Thanks
> > to everyone
> > who has contributed to this release. We are very glad to see some new
> > contributors in this release.
> >
> > **NOTE**: This release is primarily a bug-fix release with no major
> changes
> > to the public api. Since we are behind schedule in terms of releases, we
> > are combining the DISCUSS and VOTE email into a single VOTE email. If
> > anyone has objections, please do raise them. We plan to shortly follow-up
> > with a DISCUSS email for 0.11.0 release, that brings in new features in
> > multi-threading, REST api etc.
> >
> >
> > The release candidate can be downloaded from here:
> > http://home.apache.org/~navina/samza-0.10.1-rc0/
> >
> >
> > The release candidate is signed with pgp key 331C8F69, which can be found
> > on keyservers:
> > http://pgp.mit.edu/pks/lookup?op=get=0x331C8F69
> >
> >
> > The git tag is release-0.10.1-rc0 and signed with the same pgp key:
> > *
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > <
> >
> https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
> > >*
> >
> >
> > Test binaries have been published to Maven's staging repository, and
> > are available
> > here:
> > https://repository.apache.org/content/repositories/orgapachesamza-1012/
> >
> >
> > Note that the binaries were built with JDK7 without incident.
> >
> > 69 issues were resolved for this release:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Closed)
> >
> >
> > The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016
> ).
> >
> >
> > Please download the release candidate, check the hashes/signature, build
> > it and
> > test it, and then please vote:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> > +1 from my side for the release.
> >
> > Cheers!
> > --
> > Navina R.
> > nav...@apache.org
> >
>
>
>
> --
> Jagadish V,
> Graduate Student,
> Department of Computer Science,
> Stanford University
>

[DISCUSS] [VOTE] Apache Samza 0.10.1 RC0

2016-08-01 Thread Navina Ramesh 
Hey all,

This is a call for a vote on a release of Apache Samza 0.10.0. Thanks
to everyone
who has contributed to this release. We are very glad to see some new
contributors in this release.

**NOTE**: This release is primarily a bug-fix release with no major changes
to the public api. Since we are behind schedule in terms of releases, we
are combining the DISCUSS and VOTE email into a single VOTE email. If
anyone has objections, please do raise them. We plan to shortly follow-up
with a DISCUSS email for 0.11.0 release, that brings in new features in
multi-threading, REST api etc.


The release candidate can be downloaded from here:
http://home.apache.org/~navina/samza-0.10.1-rc0/


The release candidate is signed with pgp key 331C8F69, which can be found
on keyservers:
http://pgp.mit.edu/pks/lookup?op=get=0x331C8F69


The git tag is release-0.10.1-rc0 and signed with the same pgp key:
*https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=33eff8a3e1eb2dc1dbffc661f910b1272b233640
*


Test binaries have been published to Maven's staging repository, and
are available
here:
https://repository.apache.org/content/repositories/orgapachesamza-1012/


Note that the binaries were built with JDK7 without incident.

69 issues were resolved for this release:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20in%20(0.10.1)%20AND%20status%20in%20(Resolved%2C%20Closed)


The vote will be open for 72 hours ( end in 12:00pm Thursday, 08/05/2016 ).


Please download the release candidate, check the hashes/signature, build it and
test it, and then please vote:


[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)


+1 from my side for the release.

Cheers!
-- 
Navina R.
nav...@apache.org

Re: Review Request 50583: SAMZA-954 Improve logging for Samza

2016-08-01 Thread Yi Pan (Data Infrastructure) 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50583/#review144369
---


Ship it!




Ship It!

- Yi Pan (Data Infrastructure)


On July 28, 2016, 8:41 p.m., Jake Maes wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50583/
> ---
> 
> (Updated July 28, 2016, 8:41 p.m.)
> 
> 
> Review request for samza, Boris Shkolnik, Chris Pettitt, Fred Ji, Jake Maes, 
> Navina Ramesh, Jagadish Venkatraman, Xinyu Liu, and Yi Pan (Data 
> Infrastructure).
> 
> 
> Bugs: SAMZA-954
> https://issues.apache.org/jira/browse/SAMZA-954
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> SAMZA-954 Improve logging for Samza
> 
> 
> Diffs
> -
> 
>   docs/learn/documentation/versioned/jobs/logging.md 
> 0726d37affa06f85e20fbd3bc2395c28f30159a8 
>   samza-core/src/main/scala/org/apache/samza/container/SamzaContainer.scala 
> a37f3536c45fdcb6d5410328f031b0263b71a82d 
>   samza-core/src/main/scala/org/apache/samza/metrics/JmxServer.scala 
> ad00ca00f918df4d71d1c920b77027401a55c80b 
>   samza-core/src/main/scala/org/apache/samza/util/Logging.scala 
> 250de1e2fa103be1a426d9da31187c12dbff8678 
>   samza-test/src/main/resources/log4j.xml 
> 29345f39ecef6f9ec769bf9d8eaab239f34e5d1e 
> 
> Diff: https://reviews.apache.org/r/50583/diff/
> 
> 
> Testing
> ---
> 
> Tested using hello-samza with the following log4j.xml
> 
> ```
> 
> http://jakarta.apache.org/log4j/;>
>   
> 
>class="org.apache.log4j.RollingFileAppender">
>   />
>  
>  
>  
>   
>  
>   
>class="org.apache.log4j.RollingFileAppender">
>   value="${samza.log.dir}/${samza.container.name}-startup.log" />
>  
>  
>  
>   
>  
>   
>   
> 
> 
> 
>   
>   
> 
> 
>   
> 
> 
> 
> ```
> 
> 
> Thanks,
> 
> Jake Maes
> 
>

Re: Review Request 50317: SAMZA-978: update md files to resolve inconsistent links, broken links and some confusing sentences

2016-08-01 Thread Yi Pan (Data Infrastructure) 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/50317/#review144365
---


Ship it!




Ship It!

- Yi Pan (Data Infrastructure)


On July 22, 2016, 11:23 p.m., Fred Ji wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/50317/
> ---
> 
> (Updated July 22, 2016, 11:23 p.m.)
> 
> 
> Review request for samza, Jon Bringhurst, Jagadish Venkatraman, and Yi Pan 
> (Data Infrastructure).
> 
> 
> Bugs: SAMZA-978
> https://issues.apache.org/jira/browse/SAMZA-978
> 
> 
> Repository: samza
> 
> 
> Description
> ---
> 
> 1. resolve the inconsistent next section link at the end of each section on 
> samza.apache.org/learn/documentation/0.10/; 
> 2. resolove some broken links such as Coda Hale's metrics library and Linux 
> CGroup; 
> 3. update some sentences or rephrase to make description clearer.
> 
> 
> Diffs
> -
> 
>   docs/learn/documentation/versioned/api/overview.md 
> 6712344e84e19883b857e00549db2acb101c7e0e 
>   docs/learn/documentation/versioned/comparisons/mupd8.md 
> 53417f91019c08d470d101685b6c40dad112bb18 
>   docs/learn/documentation/versioned/comparisons/storm.md 
> 58cb50895e7a419a7bede8911cd5b7f21fb487c4 
>   docs/learn/documentation/versioned/container/coordinator-stream.md 
> 98c1a845cda5ca2a53ee58b55508fc93492b982d 
>   docs/learn/documentation/versioned/container/event-loop.md 
> 116238312df7071747cbbc14bc9c46f558755195 
>   docs/learn/documentation/versioned/container/metrics.md 
> 0423155537b0095b9efcfb40757e8de17b640ffd 
>   docs/learn/documentation/versioned/container/samza-container.md 
> 55bec9813ca006757db046e6e85259b4d2e8c770 
>   docs/learn/documentation/versioned/container/state-management.md 
> 320392cd4412b459a093ab9657b7264cee42958b 
>   docs/learn/documentation/versioned/container/windowing.md 
> b10e5d4eba61cb5da026af828d89d558457a6b16 
>   docs/learn/documentation/versioned/hdfs/producer.md 
> 0865a351b48c0b00e32282d2d7e44dfeae09b4ec 
>   docs/learn/documentation/versioned/index.html 
> 1e79bd6f39ee67b5a2b74222d647342990bbbe23 
>   docs/learn/documentation/versioned/yarn/isolation.md 
> a76f6fd0f93482c085b15bb1b2c313a913508bcc 
>   docs/learn/documentation/versioned/yarn/yarn-host-affinity.md 
> af6367da4f5611e208c9fb8426554c4a9c4ad6c8 
> 
> Diff: https://reviews.apache.org/r/50317/diff/
> 
> 
> Testing
> ---
> 
> Basic unit tests and checkstyleTest passed.
> 1. Run unit tests:
>   ./gradlew clean build
> 2. Check if your code follows the coding conventions:
>   ./gradlew checkstyleMain checkstyleTest
>   
> Brought up Jekyll, built a local website out of markdown pages, and verified 
> the changes and links on localhost server.
> 
> 
> Thanks,
> 
> Fred Ji
> 
>