Hi all,
SEP-15 has been updated now that SAMZA-1714 has been reviewed and implemented.
Please vote on whether there are further breaking changes needed in the API or
we can accept this proposal to be included in Samza 1.0.
https://cwiki.apache.org/confluence/display/SAMZA/SEP-15%3A+New+Runtime+C
Hi Jeremiah,
If you would like to continue to use the low-level API (i.e. StreamTask),
then you actually will want to use TaskApplication, not StreamApplication.
Sorry for the confusion regarding the naming of the classes. Take a look at
https://samza.apache.org/learn/documentation/latest/api/low-
Thanks Xinyu for starting this thread.
I support the guidelines that you mentioned, with a couple clarifications
regarding "PR Review": If a Samza PR is authored by a committer, then
another second committer should provide an approval before that code is
merged, correct? Once the second committer p
Hey Malcolm,
Sorry for not responding to this earlier. Unfortunately, we don't have an
example in which ProducerInterceptor is used in a Samza application. It's
odd that the whole task fails when you try to use your interceptor. The
only thing I could think of is that the Kafka producer fails to p
contained in this
> message is intended only for the personal and confidential use of the
> recipient(s) named above. If you have received this message in error,
> please notify the sender immediately and delete the original message.
>
>
> On Mon, Oct 7, 2019 at 2:32 PM Cameron Lee
>
Hi all,
We created SEP-24: Cluster-based Job Coordinator Dependency Isolation.
Please find the SEP wiki here (
https://cwiki.apache.org/confluence/display/SAMZA/SEP-24%3A+Cluster-based+Job+Coordinator+Dependency+Isolation
).
Please take a look and provide any feedback.
Thank you,
Cameron
Thanks for the proposal.
I just have one comment: It looks like part of the API for the new system
producer is that the OutgoingMessageEnvelope.message can be an Avro record
or a byte array, depending on how the user wants to manage schemas. Can you
please add some detail to the SEP about that part
Hi all,
I am just refreshing this thread to check if there is any further feedback
on this SEP.
Thank you,
Cameron
On Fri, Nov 22, 2019 at 11:24 AM Cameron Lee
wrote:
> Hi all,
> We created SEP-24: Cluster-based Job Coordinator Dependency Isolation.
> Please find the SEP wiki here
Hi all,
We have made some updates to Samza, and we would like to make a Samza 1.4
release.
We have been testing some of these changes internally at Linkedin, and we
would like to send this thread for discussion for releasing to open source.
Highlights of the release include improvements to local st
d, Feb 26, 2020 at 1:25 PM Xinyu Liu wrote:
>
> > This is great! Thanks for driving the new release.
> >
> > Thanks,
> > Xinyu
> >
> > On Tue, Feb 25, 2020 at 2:45 PM Cameron Lee
> > wrote:
> >
> > > Hi all,
> > > We have made some u
Hi all,
This is a call for a vote on SEP-24: Cluster-based Job Coordinator
Dependency Isolation. Thanks to everyone who reviewed the proposal and
provided feedback.
I have addressed comments on the SEP, and I am not aware of any further
major questions or objections, so I am starting this vote.
Hi all,
This is a call for a vote on a release of Apache Samza 1.4.0. Thanks to
everyone who has contributed to this release.
The release candidate can be downloaded from here:
http://home.apache.org/~cameronlee/samza-1.4.0-rc0/
The release candidate is signed with pgp key 0x54CB3CE3, which can
s that running 'gradle -b
> bootstrap.gradle'
> brings in gradle5.*, while the gradle files we have are for 4.*
> Cameron is looking into fixing this situation.
> -1
>
> On Fri, Feb 28, 2020 at 3:59 PM Cameron Lee
> wrote:
>
> > Hi all,
> >
> > This
Hi all,
This is a call for a vote on a release of Apache Samza 1.4.0. Thanks to
everyone who has contributed to this release.
The release candidate can be downloaded from here:
https://home.apache.org/~cameronlee/samza-1.4.0-rc1/
The release candidate is signed with pgp key 0x54CB3CE3, which can
gt; >
> > > Thanks Cameron. I look forward to this feature taking our "Stream
> > > Processing as a service" offering to the next level.
> > >
> > > Cheers
> > >
> > > On Tuesday, March 3, 2020, Prateek Maheshwari
> > wrote:
wrote:
> >
> > > Have downloaded the files, build with check-all.sh, and ran both YARN
> and
> > > standalone integration tests. All passed.
> > >
> > > +1 (binding).
> > >
> > > Thanks!
> > >
> > > -Yi
> &
Ideally,
> when we are deploying the same Samza application on YARN vs Mesos or
> managed K8s clusters, we should only need to change the configure values,
> not the configuration variable names and values. Does it make sense?
> Otherwise, we can schedule a conf call to clarify that
gt; If not, what's the mechanism that we will use to let the container JVM
> process to know where the YARN localizer has put API/infra classpaths?
>
> Thanks!
>
> -Yi
>
>
>
> On Wed, Mar 11, 2020 at 8:09 PM Cameron Lee
> wrote:
>
> > The configuration va
4:07 PM Yi Pan wrote:
> Hey, Cameron,
>
> Thanks for the detailed answers. It would be good to add this explanation
> to the SEP page as well.
>
> Otherwise, +1 from my side. Thanks!
>
> -Yi
>
> On Mon, Mar 16, 2020 at 10:06 AM Cameron Lee
> wrote:
>
> >
19 matches
Mail list logo