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
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
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 enabl
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 enabl
> 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 ar
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 pr
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 enabl
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 re
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 enabl
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 zkNa
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 yo
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
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 c
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 a
+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
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
allo
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 investigat
17 matches
Mail list logo
