Re: [ANNOUNCE] Please welcome Boris Shkolnik to the Samza PMC
Congrats Boris! On Fri, Jun 7, 2019 at 3:20 PM Bharath Kumara Subramanian < codin.mart...@gmail.com> wrote: > Congratulations Boris! > > On Fri, Jun 7, 2019 at 3:19 PM Jagadish Venkatraman < > jagadish1...@gmail.com> > wrote: > > > Congratulations Boris! > > > > On Fri, Jun 7, 2019 at 3:15 PM Xinyu Liu wrote: > > > > > Congrats, Boris! > > > > > > Xinyu > > > > > > On Fri, Jun 7, 2019 at 3:13 PM Jakob Homan wrote: > > > > > > > Howdy all- > > > >I'm very pleased to announce that the Samza PMC has voted Boris > > > > Shkolnik to be a Project Management Committee (PMC) Member. The PMC > > > > is responsible for the overall health of a project andl for voting in > > > > new committers and PMC members, as well as VOTEing on releases. Over > > > > the past two years, Boris has been a valuable committer on the > > > > project. > > > > > > > > Congrats Boris! > > > > > > > > Thanks, > > > > > > > > Jakob > > > > on behalf of the Samza PMC > > > > > > > > > > > > > -- > > Jagadish V, > > Graduate Student, > > Department of Computer Science, > > Stanford University > > > -- Nacho - Ignacio Solis - iso...@igso.net
Re: Samza 13.1 and Kafka 1.0
XiaoChuan, if you want to do some testing with Kafka 1.0 and report your findings you are highly encouraged :-). On Tue, Nov 7, 2017 at 9:56 AM, Yi Pan <nickpa...@gmail.com> wrote: > Hi, XiaoChuan, > > Sorry to reply late. Samza 13.1 is built w/ Kafka 0.10.1.1. We have not > test against Kafka broker 1.0 yet. We usually release Samza with the Kafka > version that is running as a stable one in LinkedIn. If you have specific > feature requirements that is only in Kafka 1.0, please let us know. > > Thanks! > > -Yi > > On Sat, Nov 4, 2017 at 2:21 PM, XiaoChuan Yu <xiaochuan...@kik.com> wrote: > >> Hi, >> >> Does anyone know if Samza 13.1 is compatible with Kafka 1.0? >> >> Thanks, >> Xiaochuan Yu >> -- Nacho - Ignacio Solis - iso...@igso.net
Re: [Discuss] Samza 0.13.1 release
+1 On Fri, Aug 11, 2017 at 3:52 PM, Jacob Maes <jacob.m...@gmail.com> wrote: > Looks good! > > +1 > > On Thu, Aug 10, 2017 at 6:53 PM, Jagadish Venkatraman < > jagadish1...@gmail.com> wrote: > >> +1 for the release. thanks for the summary and for driving this Fred! >> >> On Thu, Aug 10, 2017 at 5:15 PM Fred Haifeng Ji <haifeng...@gmail.com> >> wrote: >> >> > The format was messed up when sent from my yahoo mail to >> > dev@samza.apache.org. I am resending it from my gmail account. Sorry for >> > inconvenience! >> > >> > Hi all, >> > >> > There have been some new features and critical bug fixes added to master >> > since 0.13.0 release, which makes Samza Standalone features more stable. >> It >> > is now good enough to warrant *a new minor release*. We will continue to >> > test for stability and performance in the next few weeks. >> > >> > Here are the main JIRA tickets that will be included in this release (but >> > not limited to): >> > SAMZA-1165: Cleanup data created by ZkStandalone in ZK; >> > SAMZA-1324: Add a metricsreporter lifecycle for JobCoordinator component >> of >> > StreamProcessor; >> > SAMZA-1336: Standalone session expiration propagation; >> > SAMZA-1337: LocalApplicationRunner needs to support StreamTask; >> > SAMZA-1339: Add standalone integration tests; >> > … >> > >> > There are also quite a few bug fixes in 0.13.1, *please check the >> complete >> > list of changes in 0.13.1 here >> > < >> > https://issues.apache.org/jira/browse/SAMZA-1165?jql= >> project%20%3D%2012314526%20AND%20fixVersion%20%3D%2012340845%20ORDER%20BY% >> 20priority%20DESC%2C%20key%20ASC >> > >* >> > . >> > >> > Most JIRAs in the list have been completed and merged, with the following >> > one remaining, but we should try to get it completed before 0.13.1 is >> > released. >> > SAMZA-1385: Coordination utils in LocalApplicationRunner uses same Zk >> node >> > as ZkJobCoordinatorFactory for leader election >> > >> > Here's what I propose: >> > 1. Cut an 0.13.1 release branch. >> > 2. Work on getting the remaining open JIRA done. >> > 3. Target a release vote by Aug 18. >> > >> > Thoughts? >> > >> > Fred >> > >> -- >> Sent from my iphone. >> -- Nacho - Ignacio Solis - iso...@igso.net
Re: [VOTE] Apache Samza 0.13.0 RC0
Thanks! On Mon, May 15, 2017 at 8:00 AM, Navina Ramesh <nram...@linkedin.com.invalid> wrote: > I will try to get the patch out today. Work doesn't look trivial. I am on > it. > > Navina > > On May 14, 2017 23:10, "Ignacio Solis" <iso...@igso.net> wrote: > >> We should hold off until it is solved. How long will it take to fix this? >> >> On Sun, May 14, 2017 at 10:13 PM, Navina Ramesh (Apache) >> <nav...@apache.org> wrote: >> > I just changed the status of this JIRA to "BLOCKER" - >> > https://issues.apache.org/jira/browse/SAMZA-1128 >> > >> > This causes a bug in standalone deployment where any failure in the >> barrier >> > protocol stops the scheduled executorservice. Unfortunately, >> > CoordinationUtils creates its own scheduled executorservice, which is >> > incorrect. Scheduled ExecutorService is meant to be the working queue for >> > the ZkJobCoordinator. This needs to be fixed. Bharath already ran into >> this >> > bug during testing on Friday. >> > >> > veto for this release candidate. >> > >> > @Prateek/Jagadish: >> > I recommend sending a "non-vote, testing release candidate" for this >> > release until we complete all pending tasks (includes docs, tests etc). >> It >> > will also be useful to share the pending tasks and their progress. In >> case >> > you have already shared it, I might have missed it since some emails are >> > bouncing off my inbox. >> > >> > Thanks! >> > Navina >> > >> > On Sun, May 14, 2017 at 1:30 PM, Boris S <bor...@gmail.com> wrote: >> > >> >> I think we need to add SAMZA-1286 and >> >> SAMZA-1279 to the release . >> >> >> >> On Wed, May 10, 2017 at 7:51 PM, Jagadish Venkatraman < >> jagad...@apache.org >> >> > >> >> 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/~jagadish/samza-0.13.0-rc0/ >> >> > >> >> > The release candidate is signed with pgp key AF81FFBF, which can be >> found >> >> > on keyservers: >> >> > http://pgp.mit.edu/pks/lookup?op=get=0xAF81FFBF >> >> > >> >> > The git tag is release-0.13.0-rc0 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-rc0 >> >> > >> >> > Test binaries have been published to Maven's staging repository, and >> are >> >> > available here: >> >> > https://repository.apache.org/content/repositories/ >> orgapachesamza-1020 >> >> > >> >> > 127 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 8:00PM Saturday, >> >> 05/13/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) >> >> > >> >> > >> >> > +1 from my side for the release. >> >> > >> >> > Cheers! >> >> > >> >> >> >> >> >> -- >> Nacho - Ignacio Solis - iso...@igso.net >> -- Nacho - Ignacio Solis - iso...@igso.net
Re: [VOTE] Apache Samza 0.13.0 RC0
We should hold off until it is solved. How long will it take to fix this? On Sun, May 14, 2017 at 10:13 PM, Navina Ramesh (Apache) <nav...@apache.org> wrote: > I just changed the status of this JIRA to "BLOCKER" - > https://issues.apache.org/jira/browse/SAMZA-1128 > > This causes a bug in standalone deployment where any failure in the barrier > protocol stops the scheduled executorservice. Unfortunately, > CoordinationUtils creates its own scheduled executorservice, which is > incorrect. Scheduled ExecutorService is meant to be the working queue for > the ZkJobCoordinator. This needs to be fixed. Bharath already ran into this > bug during testing on Friday. > > veto for this release candidate. > > @Prateek/Jagadish: > I recommend sending a "non-vote, testing release candidate" for this > release until we complete all pending tasks (includes docs, tests etc). It > will also be useful to share the pending tasks and their progress. In case > you have already shared it, I might have missed it since some emails are > bouncing off my inbox. > > Thanks! > Navina > > On Sun, May 14, 2017 at 1:30 PM, Boris S <bor...@gmail.com> wrote: > >> I think we need to add SAMZA-1286 and >> SAMZA-1279 to the release . >> >> On Wed, May 10, 2017 at 7:51 PM, Jagadish Venkatraman <jagad...@apache.org >> > >> 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/~jagadish/samza-0.13.0-rc0/ >> > >> > The release candidate is signed with pgp key AF81FFBF, which can be found >> > on keyservers: >> > http://pgp.mit.edu/pks/lookup?op=get=0xAF81FFBF >> > >> > The git tag is release-0.13.0-rc0 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-rc0 >> > >> > Test binaries have been published to Maven's staging repository, and are >> > available here: >> > https://repository.apache.org/content/repositories/orgapachesamza-1020 >> > >> > 127 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 8:00PM Saturday, >> 05/13/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) >> > >> > >> > +1 from my side for the release. >> > >> > Cheers! >> > >> -- Nacho - Ignacio Solis - iso...@igso.net
Re: [VOTE] Samza Logo
Hi folks. >From the comments and the votes it seems we are leaning towards the circles logo. I will proceed with this and get in touch with the designer for any details we may want to change. Cheers, Nacho On Tue, Apr 18, 2017 at 12:00 PM, Jagadish Venkatraman <jagadish1...@gmail.com> wrote: > Oh, I already voted last week. I liked the orbital loop one the best:-) > > The dots appear to signify processor nodes, and the streams connect them. > Also, it has a nice "S" like pattern aligning with Samza. Also, I did not > like the "color blind" dots as much as the orbital loop :D > > On Tue, Apr 18, 2017 at 11:38 AM, Navina Ramesh < > nram...@linkedin.com.invalid> wrote: > >> @Renato: >> Thanks for your feedback. Always appreciate help from our contributors :) >> >> @Jagadish: >> Thanks for stating your points. It is clear that you are against the >> butterfly ones. But are you in support of any of the others? Please vote :) >> >> Thanks! >> Navina >> >> On Tue, Apr 18, 2017 at 10:38 AM, Jagadish Venkatraman < >> jagadish1...@gmail.com> wrote: >> >> > FWIW, I have a contrarian perspective on this one. Here's my 2 cents: >> > >> > I'm -1 for having for our logo to do anything with a butterfly. >> > >> > - Samza and Kafka are separate top-level projects. I do not think the >> > connection to Franz Kafka's novel on "metamorphosis", and the fact that a >> > salesman named "Samsa" in the novel was transformed to an "insect" should >> > dictate our logo. Agreed, the butterfly is a cute insect remotely >> > relatable(?) to stream processing via a convoluted story. >> > >> > - For a choice of a mascot, I'd much rather have something that signifies >> > scale, sturdiness or swiftness instead of a cute butterfly :-) >> > >> > - The 2 other non-butterfly logos at-least have a "node", "stream", >> > "edges", "graph" like feel which I like. >> > >> > Thanks, >> > Jagadish >> > >> > On Sat, Apr 15, 2017 at 12:24 PM, Jacob Maes <jacob.m...@gmail.com> >> wrote: >> > >> > > I think I voted the exact opposite to everyone else in this thread. >> > > >> > > I don't want anything to do with a butterfly. The metaphor is even >> > further >> > > removed from the Samsa story than a cockroach, so I think we should >> give >> > up >> > > on that. I don't want a mascot; we're not building a university >> football >> > > team. And as animals go, the only slower one I can think of is a sloth, >> > so >> > > I don't feel a butterfly says "scalable stream processing". This, >> > combined >> > > with my preference to eschew the color red for logos, puts the red >> > > butterfly last. >> > > >> > > The blue butterfly is a little more abstract and formal looking, but >> > still >> > > a butterfly, so that is second to last. >> > > >> > > The other 2 are very close, in my opinion. >> > > >> > > The one with the circles is reminiscent of orbital loops, which gives >> me >> > > the feeling of scale. It also has the dots at varying places along the >> > > lines, which to me conveys the different proportions of input/output >> > stream >> > > sizes/TTLs. And the cyclical shape could also be used for animations >> > > portraying the concept of "reprocessing" >> > > >> > > The one with the "S" dots reminds me of the Kafka logo without the >> lines. >> > > If the lines are the streams and the dots are processing nodes, then I >> > > think it's clever for the Samza logo to be a "negative" of the Kafka >> one. >> > > That's not to say samza is any more related to Kafka than it is; but if >> > the >> > > Kafka logo says "streams" then to me this Samza logo says "processors" >> > > >> > > My 2 cents. >> > > >> > > On Fri, Apr 14, 2017 at 11:05 PM, Ignacio Solis <iso...@igso.net> >> wrote: >> > > >> > > > You're making me feel bad for linking that one! :-) >> > > > >> > > > I don't see it as a maze. To me, that one is like circles that turn, >> > > > representing the processing. Like cogs on an engine. The little >> > > > circles
Re: [VOTE] Samza Logo
Hi folks. This is a reminder that you should vote on the designs. Please REPLY TO THIS EMAIL so we know what people think. We want to choose a final logo out of these 4 designs. Nacho On Sat, Apr 15, 2017 at 12:24 PM, Jacob Maes <jacob.m...@gmail.com> wrote: > I think I voted the exact opposite to everyone else in this thread. > > I don't want anything to do with a butterfly. The metaphor is even further > removed from the Samsa story than a cockroach, so I think we should give up > on that. I don't want a mascot; we're not building a university football > team. And as animals go, the only slower one I can think of is a sloth, so > I don't feel a butterfly says "scalable stream processing". This, combined > with my preference to eschew the color red for logos, puts the red > butterfly last. > > The blue butterfly is a little more abstract and formal looking, but still > a butterfly, so that is second to last. > > The other 2 are very close, in my opinion. > > The one with the circles is reminiscent of orbital loops, which gives me > the feeling of scale. It also has the dots at varying places along the > lines, which to me conveys the different proportions of input/output stream > sizes/TTLs. And the cyclical shape could also be used for animations > portraying the concept of "reprocessing" > > The one with the "S" dots reminds me of the Kafka logo without the lines. > If the lines are the streams and the dots are processing nodes, then I > think it's clever for the Samza logo to be a "negative" of the Kafka one. > That's not to say samza is any more related to Kafka than it is; but if the > Kafka logo says "streams" then to me this Samza logo says "processors" > > My 2 cents. > > On Fri, Apr 14, 2017 at 11:05 PM, Ignacio Solis <iso...@igso.net> wrote: > >> You're making me feel bad for linking that one! :-) >> >> I don't see it as a maze. To me, that one is like circles that turn, >> representing the processing. Like cogs on an engine. The little >> circles are like the messages. The concentric circles are like the >> streams. >> >> The red butterfly is my second favorite. >> >> Vote note: >> >> Once we close voting we'll look at the actual results. The way the >> ranking gets calculated it you don't vote for a design at all, that >> vote does not get factored in. It assumes you have no opinion. So if >> somebody votes 5 stars on A and 1 start on B. And second person only >> votes 5 stars on B, then the ranking would be A-5 stars, B-3 stars. >> (or something along those lines). So if you only vote on the 5 star >> ones, you're missing your vote on the ones you don't like. >> >> So, once we close, we'll see how people voted. >> >> Nacho >> >> >> On Fri, Apr 14, 2017 at 9:21 PM, Yi Pan <nickpa...@gmail.com> wrote: >> > 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 >> <nram...@linkedin.com.invalid >> >> 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 >> >&
Re: [VOTE] Samza Logo
You're making me feel bad for linking that one! :-) I don't see it as a maze. To me, that one is like circles that turn, representing the processing. Like cogs on an engine. The little circles are like the messages. The concentric circles are like the streams. The red butterfly is my second favorite. Vote note: Once we close voting we'll look at the actual results. The way the ranking gets calculated it you don't vote for a design at all, that vote does not get factored in. It assumes you have no opinion. So if somebody votes 5 stars on A and 1 start on B. And second person only votes 5 stars on B, then the ranking would be A-5 stars, B-3 stars. (or something along those lines). So if you only vote on the 5 star ones, you're missing your vote on the ones you don't like. So, once we close, we'll see how people voted. Nacho On Fri, Apr 14, 2017 at 9:21 PM, Yi Pan <nickpa...@gmail.com> wrote: > 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 <nram...@linkedin.com.invalid >> 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 <iso...@igso.net> 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 >> > <nram...@linkedin.com.invalid> 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 <iso...@igso.net> >> 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. >> -- Nacho - Ignacio Solis - iso...@igso.net
Re: [VOTE] Samza Logo
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 <nram...@linkedin.com.invalid> 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 <iso...@igso.net> 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
[VOTE] Samza Logo
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
Re: Samza Logo designs
I'll leave this open one more day for feedback. Then wait a couple of days for redesigns, then do a final round. On Fri, Apr 7, 2017 at 1:11 PM, Ignacio Solis <iso...@igso.net> wrote: > Hi folks. > > I started a Designcrowd campaign for a logo. I got some initial > designs. I would like some feedback - voting. > > This is NOT a final design, just a way to get some more feedback for > the designers. We do want to get a design selected before the next > release. > > Please provide feedback to individual designs if you want (along with > voting), and provide general feedback here on this mailing list. > > Things that would be helpful include design ideas, concepts, themes, etc. > > http://www.designcrowd.com/vote/samza-logo-poll-phase1 > > For completeness, the relevant JIRA is this: > https://issues.apache.org/jira/browse/SAMZA- > > Cheers, > > Nacho > > -- > Nacho - Ignacio Solis - iso...@igso.net -- Nacho - Ignacio Solis - iso...@igso.net
Samza Logo designs
Hi folks. I started a Designcrowd campaign for a logo. I got some initial designs. I would like some feedback - voting. This is NOT a final design, just a way to get some more feedback for the designers. We do want to get a design selected before the next release. Please provide feedback to individual designs if you want (along with voting), and provide general feedback here on this mailing list. Things that would be helpful include design ideas, concepts, themes, etc. http://www.designcrowd.com/vote/samza-logo-poll-phase1 For completeness, the relevant JIRA is this: https://issues.apache.org/jira/browse/SAMZA- Cheers, Nacho -- Nacho - Ignacio Solis - iso...@igso.net
Re: [VOTE] SEP-1: Semantics of ProcessorId in Samza
; > Because JobCoordinator provides coordination service across many >> > > > > processors, an interface getProcessorId() in JobCoordinator is >> > > confusing >> > > > > regarding to which processorId we are getting. >> > > > > >> > > > > Otherwise, the proposal looks good. >> > > > > >> > > > > -Yi >> > > > > >> > > > > On Wed, Mar 29, 2017 at 7:57 PM, Navina Ramesh >> > > > > <nram...@linkedin.com.invalid >> > > > > > wrote: >> > > > > >> > > > > > Good to hear from you, Yan. Thanks! :) >> > > > > > >> > > > > > On Wed, Mar 29, 2017 at 7:48 PM, Yan Fang <yanfang...@gmail.com> >> > > > wrote: >> > > > > > >> > > > > > > +1 . Thanks for the proposal, Navina. :) >> > > > > > > >> > > > > > > Fang, Yan >> > > > > > > yanfang...@gmail.com >> > > > > > > >> > > > > > > On Thu, Mar 30, 2017 at 4:24 AM, Prateek Maheshwari < >> > > > > > > pmaheshw...@linkedin.com.invalid> wrote: >> > > > > > > >> > > > > > > > +1 (non binding) from me. >> > > > > > > > >> > > > > > > > - Prateek >> > > > > > > > >> > > > > > > > On Tue, Mar 28, 2017 at 2:17 PM, Boris S <bor...@gmail.com> >> > > wrote: >> > > > > > > > >> > > > > > > > > +1 Looks good to me. >> > > > > > > > > >> > > > > > > > > On Tue, Mar 28, 2017 at 2:00 PM, xinyu liu < >> > > > xinyuliu...@gmail.com> >> > > > > > > > wrote: >> > > > > > > > > >> > > > > > > > > > +1 on my side. Very happy to see this proposal. This is a >> > > > blocker >> > > > > > for >> > > > > > > > > > integrating fluent API with StreamProcessor, and >> hopefully >> > we >> > > > can >> > > > > > get >> > > > > > > > it >> > > > > > > > > > resolved soon :). >> > > > > > > > > > >> > > > > > > > > > Thanks, >> > > > > > > > > > Xinyu >> > > > > > > > > > >> > > > > > > > > > On Tue, Mar 28, 2017 at 11:28 AM, Navina Ramesh (Apache) >> < >> > > > > > > > > > nav...@apache.org> >> > > > > > > > > > wrote: >> > > > > > > > > > >> > > > > > > > > > > Hi everyone, >> > > > > > > > > > > >> > > > > > > > > > > This is a voting thread for SEP-1: Semantics of >> > ProcessorId >> > > > in >> > > > > > > Samza. >> > > > > > > > > > > For reference, here is the wiki link: >> > > > > > > > > > > https://cwiki.apache.org/confluence/display/SAMZA/SEP- >> > > > > > > > > > > 1%3A+Semantics+of+ProcessorId+in+Samza >> > > > > > > > > > > >> > > > > > > > > > > Link to discussion mail thread: >> > > > > > > > > > > http://mail-archives.apache. >> > org/mod_mbox/samza-dev/201703. >> > > > > > > > > > > mbox/%3CCANazzuuHiO%3DvZQyFbTiYU-0Sfh3riK%3Dz4j_ >> > > > > > > > > > AdCicQ8rBO%3DXuYQ%40mail. >> > > > > > > > > > > gmail.com%3E >> > > > > > > > > > > >> > > > > > > > > > > Please vote on this SEP asap. :) >> > > > > > > > > > > >> > > > > > > > > > > Thanks! >> > > > > > > > > > > Navina >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > -- >> > > > > > Navina R. >> > > > > > >> > > > > >> > > > >> > > > >> > > > >> > > > -- >> > > > Navina R. >> > > > >> > > >> > >> > >> > >> > -- >> > Navina R. >> > >> > > > > -- > We are hiring in Streams Infra (Kafka/Samza/Datastream) !! -- Nacho - Ignacio Solis - iso...@igso.net
