Re: [VOTE] Samza Logo

[Yi Pan]

Really? The one with the maze on the left currently is top one? I can't
relate to that either. My favorite was the logo w/ Taiji symbol. Since that
did not make the top 4, I am voting for the red bufferfly one, same as
Navina.

-Yi

On Fri, Apr 14, 2017 at 3:33 PM, Navina Ramesh  wrote:

> I prefer to have open discussions in the official mailing list or JIRA
> since it is an open-community. It also helps track the discussions.
>
> Fwiw, I am in favor of the red themed butterfly design because:
> 1. Knowing the origin of the name "Samza" (from Gregor Samsa character in
> "Metamorphosis"), it isn't very far-fetched in terms of relating stream
> processing to some kind of transformation. Butterfly is probably the
> prettiest insect to associate with "metamorphosis", without giving the
> impression of a bug :)
> 2. Red theme ties it with the current logo, although we can improvise on
> the gradients.
> 3. We can have a "mascot" , instead of an abstract symbol.
>
> One comment on the butterfly one - it seems to have only 1 antenna.
>
> -1 for the dots only logo. It feels like a color-blindness test :D
> -1 for the blue-based logo - it is just not relatable and it's an extreme
> change from the current one.
>
> I couldn't relate to the circular one. What are are trying to portray/imply
> here. That we are a bunch of disconnected links?
>
> Thanks!
> Navina
>
> On Fri, Apr 14, 2017 at 3:16 PM, Ignacio Solis  wrote:
>
> > Vote directly at design crowd.  But feel free to leave comments here,
> > maybe you can try to persuade people or argue for your favorite. :-)
> >
> > Nacho
> >
> > On Fri, Apr 14, 2017 at 2:31 PM, Navina Ramesh
> >  wrote:
> > > Hi Nacho,
> > > Do you want us to vote on this mail thread or directly at design crowd?
> > >
> > > Thanks!
> > > Navina
> > >
> > > On Fri, Apr 14, 2017 at 2:19 PM, Ignacio Solis 
> wrote:
> > >
> > >> Hi folks.
> > >>
> > >> After some feedback and culling, we are down to 4 candidates.  Please
> > >> vote on your favorite designs. We will be able to make minor
> > >> modifications to the selected logo as we talk to the designer.  We can
> > >> always have changes in colors or fonts.
> > >>
> > >> http://www.designcrowd.com/vote/apachesamzalogo
> > >>
> > >> This poll will stay open for about a week to collect all votes and
> > >> comments.
> > >>
> > >> For completeness, the relevant JIRA is this:
> > >> https://issues.apache.org/jira/browse/SAMZA-
> > >>
> > >> Cheers,
> > >>
> > >> Nacho
> > >>
> > >> --
> > >> Nacho - Ignacio Solis - iso...@igso.net
> > >>
> > >
> > >
> > >
> > > --
> > > Navina R.
> >
> >
> >
> > --
> > Nacho - Ignacio Solis - iso...@igso.net
> >
>
>
>
> --
> Navina R.
>

Re: [VOTE] Samza Logo

[Navina Ramesh]

I prefer to have open discussions in the official mailing list or JIRA
since it is an open-community. It also helps track the discussions.

Fwiw, I am in favor of the red themed butterfly design because:
1. Knowing the origin of the name "Samza" (from Gregor Samsa character in
"Metamorphosis"), it isn't very far-fetched in terms of relating stream
processing to some kind of transformation. Butterfly is probably the
prettiest insect to associate with "metamorphosis", without giving the
impression of a bug :)
2. Red theme ties it with the current logo, although we can improvise on
the gradients.
3. We can have a "mascot" , instead of an abstract symbol.

One comment on the butterfly one - it seems to have only 1 antenna.

-1 for the dots only logo. It feels like a color-blindness test :D
-1 for the blue-based logo - it is just not relatable and it's an extreme
change from the current one.

I couldn't relate to the circular one. What are are trying to portray/imply
here. That we are a bunch of disconnected links?

Thanks!
Navina

On Fri, Apr 14, 2017 at 3:16 PM, Ignacio Solis  wrote:

> Vote directly at design crowd.  But feel free to leave comments here,
> maybe you can try to persuade people or argue for your favorite. :-)
>
> Nacho
>
> On Fri, Apr 14, 2017 at 2:31 PM, Navina Ramesh
>  wrote:
> > Hi Nacho,
> > Do you want us to vote on this mail thread or directly at design crowd?
> >
> > Thanks!
> > Navina
> >
> > On Fri, Apr 14, 2017 at 2:19 PM, Ignacio Solis  wrote:
> >
> >> Hi folks.
> >>
> >> After some feedback and culling, we are down to 4 candidates.  Please
> >> vote on your favorite designs. We will be able to make minor
> >> modifications to the selected logo as we talk to the designer.  We can
> >> always have changes in colors or fonts.
> >>
> >> http://www.designcrowd.com/vote/apachesamzalogo
> >>
> >> This poll will stay open for about a week to collect all votes and
> >> comments.
> >>
> >> For completeness, the relevant JIRA is this:
> >> https://issues.apache.org/jira/browse/SAMZA-
> >>
> >> Cheers,
> >>
> >> Nacho
> >>
> >> --
> >> Nacho - Ignacio Solis - iso...@igso.net
> >>
> >
> >
> >
> > --
> > Navina R.
>
>
>
> --
> Nacho - Ignacio Solis - iso...@igso.net
>



-- 
Navina R.

Re: [VOTE] Samza Logo

[Ignacio Solis]

Vote directly at design crowd.  But feel free to leave comments here,
maybe you can try to persuade people or argue for your favorite. :-)

Nacho

On Fri, Apr 14, 2017 at 2:31 PM, Navina Ramesh
 wrote:
> Hi Nacho,
> Do you want us to vote on this mail thread or directly at design crowd?
>
> Thanks!
> Navina
>
> On Fri, Apr 14, 2017 at 2:19 PM, Ignacio Solis  wrote:
>
>> Hi folks.
>>
>> After some feedback and culling, we are down to 4 candidates.  Please
>> vote on your favorite designs. We will be able to make minor
>> modifications to the selected logo as we talk to the designer.  We can
>> always have changes in colors or fonts.
>>
>> http://www.designcrowd.com/vote/apachesamzalogo
>>
>> This poll will stay open for about a week to collect all votes and
>> comments.
>>
>> For completeness, the relevant JIRA is this:
>> https://issues.apache.org/jira/browse/SAMZA-
>>
>> Cheers,
>>
>> Nacho
>>
>> --
>> Nacho - Ignacio Solis - iso...@igso.net
>>
>
>
>
> --
> Navina R.



-- 
Nacho - Ignacio Solis - iso...@igso.net

Re: [VOTE] Samza Logo

[Navina Ramesh]

Hi Nacho,
Do you want us to vote on this mail thread or directly at design crowd?

Thanks!
Navina

On Fri, Apr 14, 2017 at 2:19 PM, Ignacio Solis  wrote:

> Hi folks.
>
> After some feedback and culling, we are down to 4 candidates.  Please
> vote on your favorite designs. We will be able to make minor
> modifications to the selected logo as we talk to the designer.  We can
> always have changes in colors or fonts.
>
> http://www.designcrowd.com/vote/apachesamzalogo
>
> This poll will stay open for about a week to collect all votes and
> comments.
>
> For completeness, the relevant JIRA is this:
> https://issues.apache.org/jira/browse/SAMZA-
>
> Cheers,
>
> Nacho
>
> --
> Nacho - Ignacio Solis - iso...@igso.net
>



-- 
Navina R.

[VOTE] Samza Logo

[Ignacio Solis]

Hi folks.

After some feedback and culling, we are down to 4 candidates.  Please
vote on your favorite designs. We will be able to make minor
modifications to the selected logo as we talk to the designer.  We can
always have changes in colors or fonts.

http://www.designcrowd.com/vote/apachesamzalogo

This poll will stay open for about a week to collect all votes and comments.

For completeness, the relevant JIRA is this:
https://issues.apache.org/jira/browse/SAMZA-

Cheers,

Nacho

-- 
Nacho - Ignacio Solis - iso...@igso.net

[GitHub] samza pull request #86: SAMZA-1145: Provide Ability To Confgure The Default ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #119: SAMZA-1195 fix bug in Samza application master on K...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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.
---

[REPORT] Apache Samza - April 2017

[Yi Pan]

## Description:

Apache Samza is a distributed stream processing engine that are highly
configurable to process events from various data sources, including
real-time messaging system (e.g. Kafka)

and distributed file systems (e.g. HDFS).



## Issues:

 - there are no issues requiring board attention at this time



## Activity:

 - Major revision on API is proposed and in progress (SAMZA-914, SAMZA-915)

 - New feature Samza-as-a-lib (SAMZA-1063) in progress

 - Started the SEP (Samza Enhancement Proposal) process for major feature
design

 - Redfin had a Samza meet up and LinkedIn is planning the next one in May



## Health report:

 - Project is in healthy status with a lot of development activities

 - More adoptions are reported (including Redfin)



## PMC changes:



 - Currently 11 PMC members.

 - No new PMC members added in the last 3 months

 - Last PMC addition was Navina Ramesh on Thu Jan 07 2016



## Committer base changes:



 - Currently 16 committers.

 - No new committers added in the last 3 months

 - Last committer addition was Xinyu Liu at Mon Sep 26 2016



## Releases:



 - 0.12.0 was released on Tue Feb 21 2017



## Mailing list activity:



 - Subscribers remain relatively the same. More dev related mailing list
activities are seen since last quarter.



 - dev@samza.apache.org:

- 296 subscribers (down -3 in the last 3 months):

- 384 emails sent to list (328 in previous quarter)





## JIRA activity:



 - 134 JIRA tickets created in the last 3 months

 - 58 JIRA tickets closed/resolved in the last 3 months

[DISCUSS] SEP-2: ApplicationRunner Design

[Yi Pan]

Hi, everyone,

In light of new features such as fluent API and standalone that introduce
new deployment / application launch models in Samza, I created a new SEP-2
to address the new use cases. SEP-2 link:
https://cwiki.apache.org/confluence/display/SAMZA/SEP-2%3A+ApplicationRunner+Design

Please take a look and give feedbacks!

Thanks!

-Yi

[GitHub] samza pull request #124: SAMZA-1209: Improve error handling in LocalStoreMon...

[shanthoosh]

GitHub user shanthoosh opened a pull request:

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

SAMZA-1209: Improve error handling in LocalStoreMonitor

Changes:

1. Add opt-in configuration to continue garbage collection of local stores
   when there’s a failure in garbage collecting one local store.
2. Handle failures gracefully. In getJobModel, JobModel is expected as 
return response.
   Incase of failures, returned error-message Map is deserialized to 
JobModel
   resulting in ClassCastException. Handle 2xx, failures separately. Log 
error
   messages returned properly in httpGet call.
3. Fix getTasks url format.
4. Minor code cleanup(Switch to using ',' as seperator for 
job.status.servers configuration
   instead of '.' for ease of use).
5. Fix disabled tests in TestLocalStoreMonitor.

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

$ git pull https://github.com/shanthoosh/samza 
fix_config_format_in_localstore_monitor

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

https://github.com/apache/samza/pull/124.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 #124


commit c4a344ae7afc463346e3450548255d13b1bd7676
Author: Shanthoosh Venkataraman 
Date:   2017-04-12T16:53:19Z

SAMZA-1209: Improve error handling in LocalStoreMonitor

Changes:

1. Add opt-in configuration to continue garbage collection of local stores
   when there’s a failure in garbage collecting one local store.
2. Handle failures gracefully. In getJobModel, JobModel is expected as 
return response.
   Incase of failures, returned error-message Map is deserialized to 
JobModel
   resulting in ClassCastException. Handle 2xx, failures separately. Log 
error
   messages returned properly in httpGet call.
3. Fix getTasks url format.
4. Minor code cleanup(Switch to using ',' as seperator for 
job.status.servers configuration
   instead of '.' for ease of use).
5. Fix disabled tests in TestLocalStoreMonitor.




---
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.
---