[RESULT][VOTE] Apache Samza 1.8.0 RC0

Hey All, The vote email for 1.8.0 release was sent on Dec 21st '22 and we got +1(binding) x3 from Yi, Xinyu and Boris. Samza 1.8.0 officially passed the VOTE phase! Thanks to everyone who helped with the validation! Thanks Ajo

[VOTE] Apache Samza 1.8.0 RC0

Hey All, This is a call for a vote on the release of *Apache Samza 1.8.0.* Thanks to everyone who contributed to this release. The release candidate can be downloaded from here: https://home.apache.org/~ajothomas/samza-1.8.0-rc0/ The release candidate is signed with pgp key *1A4639DA*, which is i

[DISCUSS] Apache Samza 1.8.0 RC0

Hi All, Since the last Samza 1.7.0 release earlier this year, we have added a few major features and improvements to the master which warrants a major 1.8.0 release. Within LinkedIn, some of these features have already been tested as part of our test suites and are in use in many of our productio

Re: SEP-31: Pipeline Drain: Support the ability to drain pipelines to allow incompatible intermediate schema changes

e streams) are received by tasks ==> b) infinite > watermark triggers from the source and flush all window/triggers in the > pipeline ==> c) once the infinite watermark is propagated through all > stages in the pipeline, stops the tasks. Could you confirm? > > Thanks a lot!

[VOTE] SEP-31: Pipeline Drain- Support the ability to drain pipelines to allow incompatible intermediate schema changes

Hi All, This is a call for a vote on *SEP-31: Pipeline Drain- Support the ability to drain pipelines to allow incompatible intermediate schema changes.* Thanks to everyone involved with the design and reviews to refine the proposal. Discuss Email Thread: https://lists.apache.org/thread/7m2hqcqq9l

SEP-31: Pipeline Drain: Support the ability to drain pipelines to allow incompatible intermediate schema changes

Hi All, Samza currently doesn't have a way to gracefully drain pipelines before making a backward-incompatible intermediate schema change. We have added a feature called Pipeline Drain to the samza engine to address this problem. Here is the SEP page for it: https://cwiki.apache.org/confluence/dis

[VOTE] SEP-30: Support Updates in Table API

...@mail.gmail.com%3e SEP-30: https://cwiki.apache.org/confluence/display/SAMZA/SEP-30%3A+Support+Updates+in+Table+API Jira ticket: https://issues.apache.org/jira/browse/SAMZA-2709 Please vote: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Ajo Thomas

[DISCUSS] SEP-30: Support Partial Updates in Table API

Hi All, Samza Table API is an abstraction for data sources that support random access by key and currently supports operations like Puts, Gets and Deletes on data sources. Partial updates to existing records using the Table API is a commonly requested feature and we have taken a stab to add suppor