Re: [DISCUSS] SEP-5: Enable partition expansion of input streams

[Dong Lin]

Hey Jacob, Navina, Yi,

I am wondering if my answer has addressed your concern. Can you let me know
if there is any concern with SEP?

Thanks,
Dong

On Tue, Jun 6, 2017 at 11:06 PM, Dong Lin  wrote:

> Hey Jacob,
>
> Thanks for taking time to review the SEP.
>
> I agree with you and Navina that the current SEP doesn't provide support
> to arbitrary input systems and it doesn't support partition shrink. I think
> the scope of this SEP is to support partition expansion for Kafka (the most
> widely used input system of Samza) and keep the door open for partition
> support of various input systems. The current design can support any system
> that meets the two operational requirement specified in the doc.
>
> While it is possible to support more types of input systems, it will
> likely add more complexity to the design. For example, the first
> alternative solution from you requires broker-side support to negotiate
> hash algorithm. The second alternative solution requires changelog
> partition reshuffle which carries its own design complexity and performance
> overhead. There is tradeoff between the generality and the complexity among
> these choices. I like the current design because it is simple and addresses
> a big usage scenario for us. We can add more complexity to generalize the
> design if it enables important use-case. Does this sound reasonable?
>
> Note that the "Rejected Alternative" section also mentions the possibility
> of supporting a wider range of input systems by allowing user to specify
> the new-partition to old-partition mapping. We are not doing it because 1)
> we may have better understanding of the design after we have a specific
> second input system to support 2) the current design can be extended to
> support general input systems. I think similar argument can be applied
> explain why we don't have to support general input systems using the
> potentially-good alternatives you mentioned.
>
> I hope SEP-5 can be an important first-step towards supporting partition
> expansion of any input system.
>
> To answer your questions about the current proposal:
>
> >1. "An alternative solution is to allow task number to increase after
> >partition expansion and uses a proper task-to-container assignment to
> make
> >sure the Samza output is correct." What does the container have to do
> with
> >stateful processing or output in general?
>
> The task-to-container assignment matters because if the correlated tasks
> (i.e. tasks that consume messages with the same key) needs to be in the
> same container so that they can share the same key/value local store on the
> same physical machine.
>
> >2. When you use "Join" as an example, you basically mean multiple
> >co-partitioned streams, right? This is opposed to multiple,
> >independently-partitioned streams or a single stream. Would be nice to
> >formulate the proposal in these more general terms.
>
> I thought "join" is a commonly used to refer to the join opeartion with
> co-partitioned stream but I may be wrong. I have updated the wiki to
> explicitly mention "co-partitioned stream". Does this look better now?
>
> >3. When switching SSP groupers, how will the users avoid the
> >org.apache.samza.checkpoint.kafka.DifferingSystemStreamPartition
> GrouperFactoryValues
> >exception?
>
> I think we can hardcode new logic in KafkaCheckpointLogKey.scala such that
> exception will not be thrown if new grouper is
> GroupByPartitionWithFixedTaskNum and old grouper is GroupByPartition.
> Does this look reasonable?
>
> >4. Partition to task assignment is meaningless without key to partition
> >mapping. The real semantics are captured in the external requirement for
> >partitioning via hash+modulo. But in that case, iiuc, only the partition
> >count matters. So why not just store the original partition count rather
> >than the whole mapping?
>
> I think storing the previous task-to-partition mapping is more general
> than storing the partition count of all topics for the following reasons:
>
> - Samza already stores the task-to-container mapping and container-to-host
> mapping in the coordinator stream. It seems consistent to also store the
> partition-to-task mapping. And this information may be useful for other
> use-case such as debugging.
>
> - By having the new interface take the previous task-to-partition
> assignment instead of a topic-to-partition-count mapping as new parameter,
> we can potentially have grouper implementation to support other types of
> input systems.
>
> - It is sightly simpler to store the task-to-partition assignment because
> we don't need to know whether this is the first time a job is started or
> not. On the other hand, you can write topic-to-partition-count mapping to
> the coordinator stream only if this is the first time the job is run
>
> Thanks,
> Dong
>
> On Mon, Jun 5, 2017 at 11:17 AM, Jacob Maes  wrote:
>
>> Hey Dong,
>>
>> Thanks for the SEP. Supporting partition changes is critically important
>> for stateful Samza

[GitHub] samza pull request #220: SAMZA-1330: Stand alone feature preview, known limi...

[sborya]

GitHub user sborya opened a pull request:

https://github.com/apache/samza/pull/220

SAMZA-1330: Stand alone feature preview, known limitation.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/navina/samza StandAloneFeaturePreview

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/samza/pull/220.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #220


commit fafc5dbcabbadec230587685df076ffa429f4a4e
Author: Boris Shkolnik 
Date:   2017-06-07T21:26:37Z

single app for single zk

commit 42bd506684c067c077f91f11f96c5f5d5669b613
Author: Boris Shkolnik 
Date:   2017-06-08T01:05:57Z

Merge branch 'master' into StandAloneFeaturePreview

commit ea33a922599057225a477ec97b6836aaf673fb49
Author: Boris Shkolnik 
Date:   2017-06-08T01:08:17Z

added a "known problem" for StandAlone




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] samza pull request #219: SAMZA-1329: Switch SamzaTaskProxy to use LocalityMa...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/samza/pull/219


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] samza pull request #216: SAMZA-1326: Revert to use getGlobalAppId for zk pat...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/samza/pull/216


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Wiki Spam

[Navina Ramesh]

> Given that admin privs are handed out to PMCs along with explicit
instructions not to change the permissions for the anonymous user, I'd
like to understand what went wrong in this case (with a view to ensuring
it doesn't happen again) before re-enabling admin permissions.

Agreed. Afaik, there are only 2 "active" PMCs in our project and I don't
believe either of us gave permissions for anonymous user.

> There were also a bunch of people who are neither PMC members nor
committers who had admin privs on your space. I'd very much prefer to
see admin privs limited to active PMC members and committers moving
forwards.

Yes. This was a mistake on our part as we should have been cautious on the
permissions we provide for contributors. Going forward, we want to correct
these permissions grants. We just want to make sure there is an avenue for
us to request permissions.

Thanks!

On Wed, Jun 7, 2017 at 12:47 PM, Mark Thomas  wrote:

> On 07/06/17 18:04, Jagadish Venkatraman wrote:
> > Hi Mark,
> >
> > Thanks for bringing this to our notice.
> >
> >>> This is because someone, going against ASF infrastructure policy,
> > altered the permissions for the anonymous user allowing them write
> > permissions
> >
> > Do we know when this occurred? I presume this was a lapse.
>
> It looks as if it was around the beginning of last month based on the
> dates of the pages I removed.
>
> >
> >>>  A samza-dev user has been created and configured to watch the
> > Samza wiki space for changes
> >
> > Sounds great! Does that mean that notifications for changes in the Samza
> > wiki space will now be sent to this mailing list?
>
> This wasn't working. It looks like those notifications will need to go
> to the commits list. I'll get that changed shortly and see if that fixes
> the problem.
>
> >>>  All users currently assigned permissions on the Samza wiki have had
> all
> > their permissions revoked except for viewing.
> >
> > We will re-assess all permissions, and set them up again.  I'm assuming
> > PMCs will still be able to do this?
>
> Not at the moment. PMC members currently have read access only.
>
> Given that admin privs are handed out to PMCs along with explicit
> instructions not to change the permissions for the anonymous user, I'd
> like to understand what went wrong in this case (with a view to ensuring
> it doesn't happen again) before re-enabling admin permissions.
>
> There were also a bunch of people who are neither PMC members nor
> committers who had admin privs on your space. I'd very much prefer to
> see admin privs limited to active PMC members and committers moving
> forwards.
>
> Mark
>
>
> >
> > Best,
> > Jagadish
> >
> > On Wed, Jun 7, 2017 at 6:13 AM, Mark Thomas  > > wrote:
> >
> > Dear Samza developer community,
> >
> > It has been brought to the infrastructure team's attention that your
> > wiki [1] is covered in spam. This is because someone, going against
> ASF
> > infrastructure policy, altered the permissions for the anonymous user
> > allowing them write permissions.
> >
> > During the investigation it was noticed that change notifications for
> > your wiki were not being sent to a public mailing list so that the
> > community could monitor all changes to the wiki.
> >
> > Therefore, the following actions have been taken:
> >
> > - All users currently assigned permissions on the Samza wiki have had
> > all their permissions revoked except for viewing.
> >
> > - A samza-dev user has been created and configured to watch the Samza
> > wiki space for changes
> >
> > Additionally, the spam pages will shortly be removed.
> >
> > Mark
> > on behalf of the ASF infrastructure team
> >
> > [1] https://cwiki.apache.org/confluence/display/SAMZA/Apache+Samza
> > 
> >
> >
>
>


-- 
Navina R.

Re: Wiki Spam

[Mark Thomas]

On 07/06/17 18:04, Jagadish Venkatraman wrote:
> Hi Mark,
> 
> Thanks for bringing this to our notice.
> 
>>> This is because someone, going against ASF infrastructure policy,
> altered the permissions for the anonymous user allowing them write
> permissions
> 
> Do we know when this occurred? I presume this was a lapse.

It looks as if it was around the beginning of last month based on the
dates of the pages I removed.

> 
>>>  A samza-dev user has been created and configured to watch the
> Samza wiki space for changes
> 
> Sounds great! Does that mean that notifications for changes in the Samza
> wiki space will now be sent to this mailing list?

This wasn't working. It looks like those notifications will need to go
to the commits list. I'll get that changed shortly and see if that fixes
the problem.

>>>  All users currently assigned permissions on the Samza wiki have had all
> their permissions revoked except for viewing.
> 
> We will re-assess all permissions, and set them up again.  I'm assuming
> PMCs will still be able to do this?

Not at the moment. PMC members currently have read access only.

Given that admin privs are handed out to PMCs along with explicit
instructions not to change the permissions for the anonymous user, I'd
like to understand what went wrong in this case (with a view to ensuring
it doesn't happen again) before re-enabling admin permissions.

There were also a bunch of people who are neither PMC members nor
committers who had admin privs on your space. I'd very much prefer to
see admin privs limited to active PMC members and committers moving
forwards.

Mark


> 
> Best,
> Jagadish
> 
> On Wed, Jun 7, 2017 at 6:13 AM, Mark Thomas  > wrote:
> 
> Dear Samza developer community,
> 
> It has been brought to the infrastructure team's attention that your
> wiki [1] is covered in spam. This is because someone, going against ASF
> infrastructure policy, altered the permissions for the anonymous user
> allowing them write permissions.
> 
> During the investigation it was noticed that change notifications for
> your wiki were not being sent to a public mailing list so that the
> community could monitor all changes to the wiki.
> 
> Therefore, the following actions have been taken:
> 
> - All users currently assigned permissions on the Samza wiki have had
> all their permissions revoked except for viewing.
> 
> - A samza-dev user has been created and configured to watch the Samza
> wiki space for changes
> 
> Additionally, the spam pages will shortly be removed.
> 
> Mark
> on behalf of the ASF infrastructure team
> 
> [1] https://cwiki.apache.org/confluence/display/SAMZA/Apache+Samza
> 
> 
> 

[GitHub] samza pull request #194: SAMZA-1221, SAMZA-1101: Internal cleanup for High-L...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/samza/pull/194


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] samza pull request #219: Switch SamzaTaskProxy to use LocalityManager.

[shanthoosh]

GitHub user shanthoosh opened a pull request:

https://github.com/apache/samza/pull/219

Switch SamzaTaskProxy to use LocalityManager.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shanthoosh/samza fix-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/samza/pull/219.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #219


commit f4d87d7c48541cfe210a92d8926432928ded5c9f
Author: Shanthoosh Venkataraman 
Date:   2017-06-07T03:27:44Z

Initial version of SamzaTaskProxy switch.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] samza pull request #215: Website updates for 0.13.0 release

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/samza/pull/215


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] samza pull request #218: SAMZA-1327: fail if namespace specified in the conn...

[sborya]

GitHub user sborya opened a pull request:

https://github.com/apache/samza/pull/218

SAMZA-1327: fail if namespace specified in the connection string does not 
exist



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/navina/samza zkNameSpaceFail

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/samza/pull/218.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #218


commit 20af96c17f91d5909cf2434302938b8ea46ceed1
Author: Boris Shkolnik 
Date:   2017-06-07T17:45:07Z

fail if namespace specified in the connection string does not exist




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] samza pull request #217: SAMZA-1327: create zk namespace if does not exist

[sborya]

GitHub user sborya opened a pull request:

https://github.com/apache/samza/pull/217

SAMZA-1327: create zk namespace if does not exist



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/navina/samza zkNamespaceCreate

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/samza/pull/217.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #217


commit a10da0f823c1f1b16703db29cb83dc6993ed0c76
Author: Boris Shkolnik 
Date:   2017-06-07T17:41:16Z

create zk namespace if does not exist




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Wiki Spam

[Navina Ramesh]

Hi Mark,
Thanks for letting us know.

We will re-asses our permissions and set them up. Should we reach out to
Gavin to set them up? It will be great to have one or more of the PMCs have
access to assign permission to reduce the turn-over time. Please let us
know the procedure.

Thanks!
Navina

On Wed, Jun 7, 2017 at 10:04 AM, Jagadish Venkatraman 
wrote:

> Hi Mark,
>
> Thanks for bringing this to our notice.
>
> >> This is because someone, going against ASF infrastructure policy,
> altered the permissions for the anonymous user allowing them write
> permissions
>
> Do we know when this occurred? I presume this was a lapse.
>
> >>  A samza-dev user has been created and configured to watch the Samza
> wiki
> space for changes
>
> Sounds great! Does that mean that notifications for changes in the Samza
> wiki space will now be sent to this mailing list?
>
> >>  All users currently assigned permissions on the Samza wiki have had all
> their permissions revoked except for viewing.
>
> We will re-assess all permissions, and set them up again.  I'm assuming
> PMCs will still be able to do this?
>
> Best,
> Jagadish
>
> On Wed, Jun 7, 2017 at 6:13 AM, Mark Thomas  wrote:
>
> > Dear Samza developer community,
> >
> > It has been brought to the infrastructure team's attention that your
> > wiki [1] is covered in spam. This is because someone, going against ASF
> > infrastructure policy, altered the permissions for the anonymous user
> > allowing them write permissions.
> >
> > During the investigation it was noticed that change notifications for
> > your wiki were not being sent to a public mailing list so that the
> > community could monitor all changes to the wiki.
> >
> > Therefore, the following actions have been taken:
> >
> > - All users currently assigned permissions on the Samza wiki have had
> > all their permissions revoked except for viewing.
> >
> > - A samza-dev user has been created and configured to watch the Samza
> > wiki space for changes
> >
> > Additionally, the spam pages will shortly be removed.
> >
> > Mark
> > on behalf of the ASF infrastructure team
> >
> > [1] https://cwiki.apache.org/confluence/display/SAMZA/Apache+Samza
> >
>



-- 
Navina R.

[GitHub] samza pull request #216: SAMZA-1326: Revert to use getGlobalAppId for zk pat...

[sborya]

GitHub user sborya opened a pull request:

https://github.com/apache/samza/pull/216

SAMZA-1326: Revert to use getGlobalAppId for zk path



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/navina/samza getGlobalId

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/samza/pull/216.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #216


commit 70eefbed0de7a8674aeaf8e9f122760ef49b9a93
Author: Boris Shkolnik 
Date:   2017-06-07T17:18:46Z

revert to use getGlobalAppId for zk path




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Wiki Spam

[Jagadish Venkatraman]

Hi Mark,

Thanks for bringing this to our notice.

>> This is because someone, going against ASF infrastructure policy,
altered the permissions for the anonymous user allowing them write
permissions

Do we know when this occurred? I presume this was a lapse.

>>  A samza-dev user has been created and configured to watch the Samza wiki
space for changes

Sounds great! Does that mean that notifications for changes in the Samza
wiki space will now be sent to this mailing list?

>>  All users currently assigned permissions on the Samza wiki have had all
their permissions revoked except for viewing.

We will re-assess all permissions, and set them up again.  I'm assuming
PMCs will still be able to do this?

Best,
Jagadish

On Wed, Jun 7, 2017 at 6:13 AM, Mark Thomas  wrote:

> Dear Samza developer community,
>
> It has been brought to the infrastructure team's attention that your
> wiki [1] is covered in spam. This is because someone, going against ASF
> infrastructure policy, altered the permissions for the anonymous user
> allowing them write permissions.
>
> During the investigation it was noticed that change notifications for
> your wiki were not being sent to a public mailing list so that the
> community could monitor all changes to the wiki.
>
> Therefore, the following actions have been taken:
>
> - All users currently assigned permissions on the Samza wiki have had
> all their permissions revoked except for viewing.
>
> - A samza-dev user has been created and configured to watch the Samza
> wiki space for changes
>
> Additionally, the spam pages will shortly be removed.
>
> Mark
> on behalf of the ASF infrastructure team
>
> [1] https://cwiki.apache.org/confluence/display/SAMZA/Apache+Samza
>

Re: [VOTE] Apache Samza 0.13.0 RC6

[Yi Pan]

+1 (binding)
build and ran all local integration tests on Linux.

On Tue, Jun 6, 2017 at 4:01 PM, Boris S  wrote:

> +1 (non-binding)
> build and tested on Linux (with python 2.7; 2.4 and 3.5 - didn't work)
>
> On Tue, Jun 6, 2017 at 2:49 PM, Jacob Maes  wrote:
>
> > +1 (non-binding)
> >
> > Built and tested on both OSX and RHEL with gradle 2.0 and 2.2
> respectively.
> >
> > Also verified the high level API + YARN host affinity on a test job with
> 32
> > containers.
> >
> >
> >
> > On Tue, Jun 6, 2017 at 9:14 AM, xinyu liu  wrote:
> >
> > > +1 (non-binding).
> > >
> > > Downloaded the source tar, built it and run check-all.sh on REHL6 with
> > > gradle 2.8. All passed.
> > >
> > > As a side note to Jagadish's comments, the build doesn't work on a
> higher
> > > gradle version either (gradle 3.5). Seems
> "-language:implicitConversions
> > > -language:reflectiveCalls" is not a valid build option anymore.
> > >
> > > Thanks,
> > > Xinyu
> > >
> > > On Mon, Jun 5, 2017 at 10:06 AM, Jagadish Venkatraman <
> > > jagadish1...@gmail.com> wrote:
> > >
> > > > Checked out, ran tests, and all of them pass.
> > > >
> > > > +1 (non-binding)
> > > >
> > > > I did get an error when running with gradle 2.4:
> > > > >>Could not resolve all dependencies for configuration
> > > > ':samza-kafka_2.11:compile'. > java.lang.
> UnsupportedOperationException
> > > (no
> > > > error message)
> > > >
> > > > However, when I used gradle 2.8, it was resolved.
> > > >
> > > > *gradle wrapper --gradle-version 2.8*
> > > >
> > > > Best,
> > > > Jagadish
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, Jun 5, 2017 at 8:37 AM, Jake Maes  wrote:
> > > >
> > > > > This is a call for a vote on a release of Apache Samza 0.13.0.
> Thanks
> > > to
> > > > > everyone who has contributed to this release. We are very glad to
> see
> > > > some
> > > > > new contributors and features in this release.
> > > > >
> > > > > The release candidate can be downloaded from here:
> > > > > http://home.apache.org/~jmakes/samza-0.13.0-rc6/
> > > > >
> > > > > The release candidate is signed with pgp key 940AFC5A, which can be
> > > found
> > > > > on keyservers:
> > > > > *http://pgp.mit.edu/pks/lookup?op=get&search=0x940AFC5A
> > > > > *
> > > > >
> > > > > The git tag is release-0.13.0-rc6 and signed with the same pgp key:
> > > > > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=
> > > > > refs/tags/release-0.13.0-rc6
> > > > >
> > > > > Test binaries have been published to Maven's staging repository,
> and
> > > are
> > > > > available here:
> > > > > https://repository.apache.org/content/repositories/
> > orgapachesamza-1026
> > > > >
> > > > > 144 issues were resolved for this release:
> > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%
> > > > > 20SAMZA%20AND%20fixVersion%20in%20(0.13%2C%200.13.0)%
> > > > > 20AND%20status%20in%20(
> > > > > Resolved%2C%20Closed)
> > > > >
> > > > > The vote will be open for 72 hours (ending at 9:00AM Thursday,
> > > > 06/08/2017).
> > > > >
> > > > > 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)
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Jagadish V,
> > > > Graduate Student,
> > > > Department of Computer Science,
> > > > Stanford University
> > > >
> > >
> >
>

Re: Wiki peRsonal z2tdalx

[Georgios Vlachogiannis]

Wyaa

On Jun 7, 2017 13:13, "Mark Thomas"  wrote:

Dear Samza developer community,

It has been brought to the infrastructure team's attention that your
wiki [1] is covered in spam. This is because someone, going against ASF
infrastructure policy, altered the permissions for the anonymous user
allowing them write permissions.

During the investigation it was noticed that change notifications for
your wiki were not being sent to a public mailing list so that the
community could monitor all changes to the wiki.

Therefore, the following actions have been taken:

- All users currently assigned permissions on the Samza wiki have had
all their permissions revoked except for viewing.

- A samza-dev user has been created and configured to watch the Samza
wiki space for changes

Additionally, the spam pages will shortly be removed.

Mark
on behalf of the ASF infrastructure team

[1] https://cwiki.apache.org/confluence/display/SAMZA/Apache+Samza

Wiki Spam

[Mark Thomas]

Dear Samza developer community,

It has been brought to the infrastructure team's attention that your
wiki [1] is covered in spam. This is because someone, going against ASF
infrastructure policy, altered the permissions for the anonymous user
allowing them write permissions.

During the investigation it was noticed that change notifications for
your wiki were not being sent to a public mailing list so that the
community could monitor all changes to the wiki.

Therefore, the following actions have been taken:

- All users currently assigned permissions on the Samza wiki have had
all their permissions revoked except for viewing.

- A samza-dev user has been created and configured to watch the Samza
wiki space for changes

Additionally, the spam pages will shortly be removed.

Mark
on behalf of the ASF infrastructure team

[1] https://cwiki.apache.org/confluence/display/SAMZA/Apache+Samza