Re: [VOTE] SEP-28: Samza State Backend Interface and Checkpointing Improvement

> +1 (binding). Looking forward to seeing this running in production. > > -- > Bharath > > On Tue, Jun 22, 2021 at 1:41 PM Sanil Jain wrote: > > > +1 (non-binding) Thanks for the contribution > > > > On Tue, 22 Jun 2021 at 13:09, Prateek Maheshwa

Re: [VOTE] SEP-29: Blob Store Based State Backup And Restore

wrote: > > > > > +1 (non-binding) Thanks for this contribution! > > > > > > -Sanil > > > > > > On Tue, 22 Jun 2021 at 13:13, Daniel Chen wrote: > > > > > > > +1 (non-binding), thanks! > > > > > > > > O

Re: [VOTE] SEP-29: Blob Store Based State Backup And Restore

+1 (binding) from me. Thanks for the contribution! - Prateek On Tue, Jun 22, 2021 at 11:45 AM Prateek Maheshwari wrote: > Hi all, > > This is a call for a vote on SEP-29: Blob Store Based State Backup And > Restore. > > Discussion thread: > https://mail-archives.apache.o

Re: [VOTE] SEP-28: Samza State Backend Interface and Checkpointing Improvement

+1 (binding). Thanks for the contribution! - Prateek On Tue, Jun 22, 2021 at 11:13 AM Yi Pan wrote: > +1 (binding) this is going to improve our state recovery story > significantly! > > -Yi > > On Mon, Jun 21, 2021 at 1:03 PM Daniel Chen wrote: > > > Hi all, > > > > This is a call for a vote

[VOTE] SEP-29: Blob Store Based State Backup And Restore

Hi all, This is a call for a vote on SEP-29: Blob Store Based State Backup And Restore. Discussion thread: https://mail-archives.apache.org/mod_mbox/samza-dev/202106.mbox/%3cCAMja7KdMNU_Zk-vDnwcm4GSJs==126-mu6djgtsoukzkxzf...@mail.gmail.com%3e SEP-29:

[DISCUSS] SEP-29: Blob Store Based State Backup And Restore

[Sending on behalf of Shekhar due to email delivery issues] Hi folks, We've been working on adding support for a blob store based state backend for backing up and restoring local state. In our experiments this has led to significantly faster state restore times compared to Kafka changelogs,

Re: Draft board report for Samza

Looks good to me, thanks. May be worth calling out the recent improvements in standalone stability under Project Activity as well. - Prateek On Fri, Apr 16, 2021 at 12:28 PM Bharath Kumara Subramanian < codin.mart...@gmail.com> wrote: > Hi all, > > Here is a draft report for Samza. Please let

Re: [DISCUSS] Samza 1.5.1 release

+1, this is a critical bug and we should release the fix ASAP. Thanks, Prateek On Tue, Aug 18, 2020 at 9:02 PM Bharath Kumara Subramanian < codin.mart...@gmail.com> wrote: > Hi all, > > In 1.5 release, we enabled transactional state by default for all samza > jobs. We identified a critical bug

Re: [VOTE] SEP-22: Container Placements in Samza

+1 from me too. Thanks for adding this feature! - Prateek On Fri, May 29, 2020 at 11:56 AM Boris S wrote: > Hi, > LGTM. > +1. > > On Wed, May 27, 2020 at 11:28 AM Sanil Jain > wrote: > > > Hi all, > > > > This is a call for a vote on SEP-22: Container Placements in Samza > > > > Thanks to

[Draft] Samza Quarterly ASF Board Report

Hi folks, Below is the draft for the quarterly ASF Board Report for Apache Samza. If you're aware of recent community activity (new users, talks, meetups, projects etc.) related to Samza not covered below, we'd love to hear about it. Thanks, Prateek == Draft Report ==

Re: [VOTE] SEP-24: Cluster-based Job Coordinator Dependency Isolation

+1 (binding) from me. Thanks for contributing this feature. Looking forward to having dependency isolation and to the ability to upgrade the framework independently from an application. Thanks, Prateek On Fri, Feb 28, 2020 at 10:48 AM Cameron Lee wrote: > Hi all, > > This is a call for a vote

Re: [VOTE] Apache Samza 1.3.1 RC0

Integration tests and check-all passed successfully. +1 (binding) from me. Thanks, Prateek On Tue, Feb 18, 2020 at 12:47 PM Bharath Kumara Subramanian < codin.mart...@gmail.com> wrote: > Ran check-all and integration tests passed with one exception. > The following test was flaky and passed on

Re: [ANNOUNCE] Please welcome Bharath Kumarasubramanian to the Samza PMC

Congrats Bharath! On Fri, Feb 14, 2020 at 9:15 AM Sanil Jain wrote: > Congrats Bharath! > > > > On Fri, 14 Feb 2020 at 08:30, Daniel Nishimura > wrote: > > > Congrats Bharath! > > > > > > > On Feb 13, 2020, at 10:46 PM, Yi Pan wrote: > > > > > > Congrats! Bharath, well deserved! > > > > > >

Re: Samza consumer without Zookeeper

Robert, from the stacktrace this looks like something in the application logic is looking for that key (i.e. in the HelixApp constructor). Thanks, Prateek On Mon, Feb 10, 2020 at 1:14 PM Robert Wigginton wrote: > Yi, > > I think I am getting ahead of myself. We are not getting past the job >

Re: Nullpointer After Upgrade from samza 1.0.0 to 1.3.0

Brett, can you take a look at this? - Prateek On Wed, Jan 15, 2020 at 9:41 AM Jeremiah Adams wrote: > I am updating our jobs to use samza 1.3.0. I'm getting a null pointer when > manually committing via taskCoordinator.commit(). > > > Below is the stack trace - can anyone point me in the right

Stream Processing Meetup at LinkedIn (Sunnyvale) on Feb 5th

Hi folks, The next Bay Area Stream Processing meetup will be held on Wednesday, February 5, 2020. This meetup will focus on Apache Kafka, Apache Samza and related streaming technologies. Where: Unify Conference room, 950 W Maude Ave, Sunnyvale When: 5:00 - 8:00 PM RSVP: link

Re: [DISCUSS] SEP-24: Cluster-based Job Coordinator Dependency Isolation

Thanks for addressing the feedback. I'm +1 for the proposal. Looking forward to the ability to upgrade the framework independently from the application. - Prateek On Mon, Jan 6, 2020 at 10:39 AM Cameron Lee wrote: > Hi all, > I am just refreshing this thread to check if there is any further

Re: [Draft] Samza quarterly report

Samza Portable Runner for Beam > > KubeCon North America - Running Apache Samza on Kubernetes > > - We have organized meetups with the following Samza Talks: > > Sunnyvale - Stream Processing in Python with Samza and Beam > > Sunnyvale - Apache Samza 1.0: Recent Ad

Re: [Draft] Samza quarterly report

Thanks for preparing this Yi. We had the following Samza talks and meetups in 2019. Let's highlight them under Community Health: Conferences: Strange Loop - Riding the Stream Processing Wave Apache Beam Summit (Berlin) - Streaming Pipelines at Scale with Apache Beam and Samza ApacheCon North

Re: [VOTE] SEP-26: Add SystemProducer for Azure Blob Storage

+1 (binding). Thanks for the contribution. - Prateek On Tue, Jan 7, 2020 at 7:59 PM Jagadish Venkatraman wrote: > +1 (binding), looking forward to Samza's integration with Azure blobs > > On Wednesday, January 8, 2020, Lakshmi Manasa > wrote: > > > Hi, > > > > This is a call for a vote on

[RESULT][VOTE] SEP-25: PR Title And Description Guidelines

The vote on SEP-25 has been open for > 72 hours and has 4 binding and 4 non-binding +1s. SEP-25 is accepted. Thanks, Prateek

Re: [VOTE] SEP 25: PR Title and Description Guidelines

t;>> +1 non-binding > > > >>> > > > >>>> On Dec 18, 2019, at 7:09 PM, Yi Pan wrote: > > > >>>> > > > >>>> +1 (binding) > > > >>>> > > > >>>> On Wed, Dec 18, 2019 at 10:49 AM B

Re: [DISCUSS] SEP-26: Add SystemProducer for Azure Blob Storage

Thanks for the proposal Manasa, it looks good to me. If there are no major questions or objections by EOD let's move to the VOTE. Thanks, Prateek On Wed, Dec 18, 2019 at 4:27 PM Lakshmi Manasa wrote: > Hi all, > > We created SEP-26: Add SystemProducer for Azure Blob Storage. > > Please find

[VOTE] SEP 25: PR Title and Description Guidelines

Hi folks, This is a call for a vote on SEP 25: PR Title and Description Guidelines. Thanks to everyone who helped review the proposal and provided feedback. Feedback from the discussion is positive:

Re: [DISCUSS] SEP 25: PR Title and Description Guidelines

; > On Fri, Dec 13, 2019 at 11:24 PM Jagadish Venkatraman < > > > jagadish1...@gmail.com> wrote: > > > > > > > +1, thanks for the write-up Prateek. > > > > > > > > Let's also update the contributor's guidelines at: > > >

[DISCUSS] SEP 25: PR Title and Description Guidelines

Hi folks, In order to make Samza PR descriptions and commit messages more consistent, informative and discoverable, we propose the following requirements for new PRs submitted to the Samza project https://cwiki.apache.org/confluence/display/SAMZA/SEP-25%3A+PR+Title+And+Description+Guidelines

Re: [VOTE] SEP-23: Simplify Job Runner

+1 (binding). Thanks, Prateek On Wed, Dec 11, 2019 at 11:50 AM Xinyu Liu wrote: > +1 (binding). This proposal will help future split deployment as well as > make the deployment simple. Thanks for making the effort! > > Thanks, > Xinyu > > On Wed, Dec 11, 2019 at 10:30 AM Ke Wu wrote: > > >

Re: [DISCUSS] SEP-23: Simplify Job Runner

Looks good to me as well. +1 for the overall proposal, and thanks for putting it together. - Prateek On Tue, Dec 10, 2019 at 1:26 PM Xinyu Liu wrote: > Thanks for updating the SEP wiki. The revised design looks clear to me. > Some config name might be simplified, e.g. >

Re: [VOTE] Apache Samza 1.3.0 RC2

+ 1 (binding) Verified the signatures, built and ran check-all and the integration tests. All tests passed. Thanks for co-ordinating the release. - Prateek On Mon, Dec 2, 2019 at 10:18 AM Xinyu Liu wrote: > + 1 (binding) > > Verified the signatures, built and ran the integration tests. All

Re: Samza compaction policy

Hi Malcolm, Using cleanup.policy=compact on the Kafka checkpoint topic should be sufficient, and is the default when the topic is created by Samza. Under normal operations, a checkpoint topic should only have ~ num task messages. I can suggest the following ways to identify the issue: 1. Read

Re: [VOTE] SEP-18: Startpoints - Manipulating Starting Offsets for Input Streams

+1 (binding). Thanks! - Prateek On Fri, Sep 6, 2019 at 8:32 AM Bharath Kumara Subramanian < codin.mart...@gmail.com> wrote: > +1 (non-binding) > > Looks good to me. > > On Fri, Sep 6, 2019 at 8:11 AM Jagadish Venkatraman < > jagadish1...@gmail.com> > wrote: > > > +1 (binding) > > > > Excellent

Re: "send to" ordering is inconsistent

t (operations don't take long enough yet to > warrant the extra state) so we just removed it for the time being. > > Prateek Maheshwari writes: > > > Hi Tom, > > > > It looks like we won't be able to include SAMZA-2116 in the upcoming 1.1 > > release due to ti

Re: Anyone interested in Elasticsearch 5.x ?

Hi Thunder, Thanks for the offer to update the ES version! What's the scope of these changes? Is this a client version upgrade with minor changes, or a reimplementation of / significant changes to the ElasticsearchSystemProducer/Consumer? Will the changes be backwards compatible for existing

Re: REMINDER. [VOTE] Apache Samza 1.2.0 RC4

+1 (binding) Verified build + check-all + integration tests + signatures. Thanks for help with the release, Boris and Pawas. - Prateek On Wed, Jun 5, 2019 at 3:03 AM Bharath Kumara Subramanian wrote: > > +1 (non-binding) > > Verified build and test on Linux. I too noticed some intermittent

Re: Limiting the job coordinator port range

Hi Malcolm, The JC server is currently started on a random port. This is because multiple JCs can exist on the same host, so using a framework-wide pre-defined port causes bind conflicts. There's currently no way to narrow down the range or fix the port on a per-job basis. If you want to add a

Re: 0.14 to 1.x Low-Level application migration questions

Hi Thunder, I'm assuming you're talking about the low level (StreamTask) API here, since the High Level API has stronger requirements for I/O systems/streams. > How much IS picked up from config. All of the system, stream and store properties can still be specified in configuration. Properties

Re: [DISCUSS] Change Apache Samza git comments/merge email recipient to commits@samza

Thanks Xinyu. Separating discussions and commit messages sounds good to me. I'm +1, but happy to keep it as-is if others find the commit emails useful. - Prateek On Thu, Apr 4, 2019 at 3:14 PM Xinyu Liu wrote: > Hi, All, > > Our dev mailing list has been flooded with github comments/merges so

Re: Running w/ multiple CPUs/container on YARN

And just to double check, you also changed the yarn.resourcemanager.scheduler.class to CapacityScheduler? On Tue, Apr 2, 2019 at 9:49 AM Prateek Maheshwari wrote: > Is it still the same message from the AM? The one that says: "Got AM > register response. The YARN RM supports contain

Re: Running w/ multiple CPUs/container on YARN

.opts=-Daws.accessKeyId= -Daws.secretKey=, but > >> since this seemed very workaround-ish, I just assumed that I would > >> eventually hit other problems using a version of Hadoop not pinned in > >> the Samza repo. If you're running 2.7.x at LinkedIn, however, I'll >

Re: Running w/ multiple CPUs/container on YARN

about it. > > Cheers, > Malcolm > > On Mon, Apr 1, 2019 at 1:51 PM Prateek Maheshwari > wrote: > > > Hi Malcolm, > > > > Yes, the AM is just reporting what the RM specified as the maximum > allowed > > request size. > > &

Re: Running w/ multiple CPUs/container on YARN

ion-mb > > 256 > > > > > > yarn.scheduler.maximum-allocation-mb > > 14336 > > > > > > yarn.scheduler.minimum-allocation-vcores > > 1 > > > > > > yarn.scheduler.maximum-allocation-vcores

Re: Running w/ multiple CPUs/container on YARN

Hi Malcolm, Just setting that configuration should be sufficient. We haven't seen this issue before. What Samza/YARN versions are you using? Can you also include the logs from where you get the error and your yarn configuration? - Prateek On Mon, Apr 1, 2019 at 2:33 AM Malcolm McFarland wrote:

Re: SSL with Samza 0.14.1?

pache.samza > samza-core_2.12 > ${samza.version} > > > > org.apache.samza > samza-kafka_2.12 > ${samza.version} > runtime > > > > org.apache.samza > samza-kv_2.12 > ${samza.version} > runtime > > > >

Re: SSL with Samza 0.14.1?

for the job. 3. Stacktrace where you see the SSL connect errors. Thanks, Prateek On Mon, Mar 25, 2019 at 9:47 AM Prateek Maheshwari wrote: > Forwarding again. Original email did not show up on the OSS mailing list. > > -- Forwarded message - > From: Deshpande, Omkar

Fwd: SSL with Samza 0.14.1?

Forwarding again. Original email did not show up on the OSS mailing list. -- Forwarded message - From: Deshpande, Omkar Date: Fri, Mar 22, 2019 at 5:08 PM Subject: Fwd: SSL with Samza 0.14.1? To: prateek...@gmail.com ++Prateek gmail -- *From:*

Re: Error handling

and verifying if the issue is already fixed. Thanks, Prateek On Fri, Mar 22, 2019 at 7:23 AM Tom Davis wrote: > > Prateek Maheshwari writes: > > > Hi Tom, > > > > This would depend on what your k8s container orchestration logic looks > > like. For example, in YA

Re: [VOTE] Apache Samza 1.1.0 RC2

1. Verified checksum and signatures for the binaries. 2. Ran ./check-all.sh 3. Ran YARN and Standalone integration tests with the config patch successfully. +1(binding) from my side as well. Thanks, Prateek On Mon, Mar 18, 2019 at 2:06 PM Jagadish Venkatraman wrote: > 1. Verified check-sum

Re: Error handling

Hi Tom, This would depend on what your k8s container orchestration logic looks like. For example, in YARN, 'status' returns 'not running' after 'start' until all the containers requested from the AM are 'running'. We also leverage YARN to restart containers/job automatically on failures (within

Re: Backing Kafka/Yarn/Zookeeper version for Samza 1.0.0?

://www.helixeducation.com/blog/> | Twitter > <https://twitter.com/HelixEducation> | Facebook > <https://www.facebook.com/HelixEducation> | LinkedIn > <http://www.linkedin.com/company/3609946> > > > > > > *From: *Prateek Maheshwari

Re: Backing Kafka/Yarn/Zookeeper version for Samza 1.0.0?

Hi Jeremiah, We're in the process of upgrading Samza to use Kafka clients version 2.0, and YARN client version 2.9. This should be available in the next release (version 1.2). In the mean time, Kafka 0.11 and YARN 2.6 / 2.7 are the recommended versions. Can you clarify what you mean about hard

Re: "send to" ordering is inconsistent

nks, Prateek! Yes, the workaround will be fine for the time being. > Thank you again! > > Prateek Maheshwari writes: > > > Hi Tom, > > > > Thanks for reporting this. I created a ticket (SAMZA-2116 > > <https://issues.apache.org/jira/browse/SAMZA-2116>

Re: [POSSIBLE PHISHING] Task Partition Commit Failed After Upgrade

Jeremiah, were you able to resolve this issue? - Prateek On Wed, Mar 6, 2019 at 10:08 AM Prateek Maheshwari wrote: > Hi Jeremiah, > > The configuration you want to look for is: > 'job.systemstreampartition.grouper.factory'. It sh

Re: [DISCUSS] Samza 1.1.0 release

Daniel, let's try to include the following change in the release as well. SAMZA-2116: Make sendTo and sink operators non-terminal Other than that, +1 (binding). - Prateek On Thu, Mar 7, 2019 at 9:22 AM Xinyu Liu wrote: > +1 (binding) > > Thanks, > Xinyu > > On Thu, Mar 7, 2019 at 12:43 AM

Re: [POSSIBLE PHISHING] Task Partition Commit Failed After Upgrade

Hi Jeremiah, The configuration you want to look for is: 'job.systemstreampartition.grouper.factory'. It should default to: 'org.apache.samza.container.grouper.stream.GroupByPartitionFactory'. Can you check if you see this value in the configuration logged by SamzaContainer during container start?

Re: "send to" ordering is inconsistent

ep all of this functionality in a sink function. Does this work for you? Thanks, Prateek On Wed, Feb 27, 2019 at 2:54 PM Tom Davis wrote: > > Prateek Maheshwari writes: > > > Hi Tom, > > > > I'm assuming that the two sub-DAGs you're talking about are the two M

Re: "send to" ordering is inconsistent

Hi Tom, I'm assuming that the two sub-DAGs you're talking about are the two Map -> Send To chains acting on the "audit-report-requests" input and sending their results to the "audit-report-status" output. Although processing within each Task is in-order, the framework does not guarantee the

Re: [VOTE] Migration of Samza git repo to gitbox.apache.org

+1 (binding) again - Prateek On Wed, Jan 23, 2019 at 11:50 AM Pawas Chhokra wrote: > > Hi all, > > This is a call for a vote on migrating Samza git repo to gitbox.apache.org, on > 11 AM, Jan 29, 2019. As mandated by the Apache Infrastructure Team, all git > repositories must be migrated from

Re: [DISCUSS] Mandatory migration of Samza git repo to gitbox.apache.org

Thanks for starting the discussion Pawas. I'm +1 (binding) for the migration. - Prateek On Tue, Jan 15, 2019 at 11:44 AM Pawas Chhokra wrote: > > Hi all, > > As mandated by the Apache Infrastructure Team, all git repositories must be > migrated from git-wip-us.apache.org URL to

Re: Draft report to board - Jan 2019

- Beam Samza runner upgrade to use Samza 1.0 > > - Go and Python support via Beam Samza runner > > > > ## Health report: > > - Project is in healthy status with 1.0 released in Nov 2018 > > > > ## PMC changes: > > > > - Currently 15 PMC members.

Re: Beam Samza Runner - java.lang.UnsupportedOperationException: Cannot create a producer for an input system

+ Xinyu > On Jan 4, 2019, at 9:58 PM, Deshpande, Omkar > wrote: > > Hello, > > I am getting following exception while running Beam Samza Runner – > > java.lang.UnsupportedOperationException: Cannot create a producer for an > input system > > at >

Re: app.class or task.class for beam samza runner

Hi Omkar, I think it's only possible to get that exception with Samza 1.0. Can you verify that the deployment is indeed using samza 0.14.1? Thanks, Prateek On Wed, Jan 2, 2019 at 11:40 PM Deshpande, Omkar wrote: > > Hello, > > I have been able to execute my Samza-Beam application in Local

Re: https://issues.apache.org/jira/browse/SAMZA-2039

For notifying others, you can leave a comment on the ticket that you're working on it. Additionally, you can assign the ticket to yourself if you have the permissions to do so. Thanks for your interest, and please let us know if you need any help. - Prateek > On Dec 17, 2018, at 8:27 PM,

Re: Welcome Hai Lu and Aditya Toomla as committers to Apache Samza!

Congrats Hai and Aditya, and thanks for your contributions! - Prateek > On Nov 6, 2018, at 10:40 AM, Wei Song wrote: > > Congrats Hai and Aditya! > > > > On 11/6/18, 10:20 AM, "Yi Pan" wrote: > >Hi, all, > >All official steps are completed and please join me to welcome Hai and >

Re: [VOTE] Apache Samza 1.0.0 RC4

Verified signatures and successfully ran check-all and integration tests. +1 (binding) from me. Thanks, Prateek On Fri, Nov 2, 2018 at 2:39 PM Boris S wrote: > > ran check-all and integration tests. All passed. > verified signatures. > +1 > > On Wed, Oct 31, 2018 at 7:15 PM Jagadish

[CANCEL] [VOTE] Apache Samza 1.0.0 RC2

Hi all, This is the CANCEL notification for the 1.0.0 RC3. We found an issue with Samza SQL integration with the new ApplicationRunners API that we will fix in the new RC. Thanks, Prateek

Re: [VOTE] Apache Samza 1.0.0 RC3

We found an issue with Samza SQL integration with the new ApplicationRunners APIs. We'll cancel this vote and create a new RC. Thanks, Prateek On Tue, Oct 30, 2018 at 10:14 AM Jake Maes wrote: > > +1 binding > > Ran check-all on OSX with Gradle 2.8 > > On Mon, Oct 29, 2018 a

[VOTE] Apache Samza 1.0.0 RC3

Hi all, This is a call for a vote on a release of Apache Samza 1.0.0. Thanks to everyone who has contributed to this release. The release candidate can be downloaded from here: http://home.apache.org/~pmaheshwari/samza-1.0.0-rc3/ The release candidate is signed with pgp key 6585B3D7, which can

[CANCEL] [VOTE] Apache Samza 1.0.0 RC2

Hi all, This is the CANCEL notification for the 1.0.0 RC2. We found a test framework message serialization issue that we will fix in the new RC. Thanks, Prateek

Re: [VOTE] Apache Samza 1.0.0 RC2

ll and deployed locally with the test jobs. All tests passed. > > > > +1 (binding) from my end. > > > > Thanks for push the release! > > > > -Yi > > > > On Wed, Oct 24, 2018 at 8:53 AM Prateek Maheshwari > > wrote: > > > > > Hi

Re: [VOTE] Apache Samza 1.0.0 RC2

> > On Tue, Oct 23, 2018 at 2:50 PM Boris S wrote: > > > Ran build, test and integration test on Linux. > > Verified the signatures. > > > > +1 > > > > On Tue, Oct 23, 2018 at 11:55 AM Prateek Maheshwari > > wrote: > > > > > Hi all, &g

[VOTE] Apache Samza 1.0.0 RC2

Hi all, This is a call for a vote on a release of Apache Samza 1.0.0. Thanks to everyone who has contributed to this release. The release candidate can be downloaded from here: http://home.apache.org/~pmaheshwari/samza-1.0.0-rc2/ The release candidate is signed with pgp key 6585B3D7, which can

[CANCEL] [VOTE] Apache Samza 1.0.0 RC1

Hi all, This is the CANCEL notification for the 1.0.0 RC1. We found a checkstyle issue that we will fix in the new RC. Thanks, Prateek

Re: [VOTE] Apache Samza 1.0.0 RC1

/samza-test/src/main/java/org/apache/samza/test/integration/TestStandaloneIntegrationApplication.java:44: > 'method def' child have incorrect indentation level 5, expected level > should be 4. > > Thanks. > > On Mon, Oct 22, 2018 at 9:09 PM Prateek Maheshwari > wrote: > &g

[VOTE] Apache Samza 1.0.0 RC1

Hi all, This is a call for a vote on a release of Apache Samza 1.0.0. Thanks to everyone who has contributed to this release. The release candidate can be downloaded from here: http://home.apache.org/~pmaheshwari/samza-1.0.0-rc1/ The release candidate is signed with pgp key 6585B3D7, which can

[CANCEL][VOTE] Apache Samza 1.0.0 RC0

Hi all, This is the CANCEL notification for the 1.0.0 RC0. We found an integration test setup issue that we will fix. We will also include the following PR in the new RC: SAMZA-1901: Implementation of Samza SQL Shell, Thanks, Prateek

Re: [VOTE] Apache Samza 1.0.0 RC0

gt; > -- Jagadish > > > > On Fri, Oct 19, 2018 at 6:59 PM Prateek Maheshwari > wrote: > > > Hi all, > > > > This is a call for a vote on a release of Apache Samza 1.0.0. Thanks to > > everyone who has contributed to this release. > > &g

[VOTE] Apache Samza 1.0.0 RC0

Hi all, This is a call for a vote on a release of Apache Samza 1.0.0. Thanks to everyone who has contributed to this release. The release candidate can be downloaded from here: http://home.apache.org/~pmaheshwari/samza-1.0.0-rc0/ The release candidate is signed with pgp key 6585B3D7, which can

Re: [VOTE] SEP-15: New Runtime Context API

gt; > jagadish1...@gmail.com> wrote: > > > > > +1 (binding) from my side. > > > > > > LGTM > > > > > > On Mon, Oct 15, 2018 at 10:44 AM Prateek Maheshwari > > > > > wrote: > > > > > > > +1 (non-bindi

Re: [VOTE] SEP-14: System and Stream Descriptors

On Fri, Oct 12, 2018 at 12:30 PM Prateek Maheshwari > wrote: > > > Hi folks, > > > > Now that SAMZA-1804 has been implemented and reviewed, we've updated > > SEP-14 with the latest APIs and design decisions. > > > > Please vote for accepting SEP-14 in i

Re: [VOTE] SEP-15: New Runtime Context API

+1 (non-binding) for these changes. (Resending from a non-LI email due to email delivery issues) - Prateek On Fri, Oct 12, 2018 at 3:28 PM Cameron Lee wrote: > > Hi all, > > SEP-15 has been updated now that SAMZA-1714 has been reviewed and implemented. > Please vote on whether there are further

Re: [VOTE] SEP-15: New Runtime Context API

+1 (non-binding) for these changes. - Prateek > On Oct 12, 2018, at 3:27 PM, Cameron Lee wrote: > > 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

Re: [VOTE] SEP-13: unified ApplicationDescriptor and ApplicationRunner APIs for high and low- level APIs in YARN and standalone deployment

+1 (non-binding) from me. Thanks for making the changes and updating the SEP! - Prateek On Fri, Oct 12, 2018 at 12:15 PM Yi Pan wrote: > > Hi, all, > > Given SAMZA-1789 has been reviewed and implemented, SEP-13 has been updated > to the latest API classes as well. Please vote on whether there

[VOTE] SEP-14: System and Stream Descriptors

Hi folks, Now that SAMZA-1804 has been implemented and reviewed, we've updated SEP-14 with the latest APIs and design decisions. Please vote for accepting SEP-14 in its current form for the upcoming Samza 1.0 release.

Re: Need Some Help w/ Gradle Build on OpenJDK 11

Hi Jeremiah, We fixed a Rat related issue yesterday in https://github.com/apache/samza/pull/703/. I don't know if this is the same issue you were running into, but might be worth trying again with the latest master. Thanks, Prateek On Wed, Oct 10, 2018 at 6:58 AM Jeremiah Adams wrote: > >

Re: [DISCUSS] SEP-14: System and Stream Descriptors

g 6, 2018, at 4:20 PM, Prateek Maheshwari wrote: > > Hi all, > > Here's the proposal for System and Stream Descriptors - a way of > specifying systems, input and output streams properties in application > code instead of configurations. > https://cwiki.apache.org/confluence

[DISCUSS] SEP-14: System and Stream Descriptors

Hi all, Here's the proposal for System and Stream Descriptors - a way of specifying systems, input and output streams properties in application code instead of configurations. https://cwiki.apache.org/confluence/display/SAMZA/SEP-14%3A+System+and+Stream+Descriptors Here's the PR with an

Re: Samza 0.14.1 : OffsetOutOfRangeException even with auto.offset.reset=smallest

Hi Thunder, Can you provide debug level logs from KafkaSystemConsumer with the stack trace for the exception? It'll help figure out why the auto.offset.reset property isn't taking effect. If this error is due to an older checkpoint for the stream, you can try resetting the checkpoint using the

Re: Urgent : Help with latency / backlog / topic lag

d.mode = true > > And actually I think we did catch up with that setting. I have since > completed also the merge of 0.14.1 and we are able to keep up with the input > now. > > Thanks again for the pointers and the fast response! > > -Original Message- > From: Prateek Maheshw

Re: Urgent : Help with latency / backlog / topic lag

chieve ~700/sec > > > -Original Message- > From: Prateek Maheshwari [mailto:prateek...@gmail.com] > Sent: Friday, June 8, 2018 13:54 > To: dev@samza.apache.org > Subject: Re: Urgent : Help with latency / backlog / topic lag > > Hi Thunder, > >> What we believe may be hap

Re: Urgent : Help with latency / backlog / topic lag

Hi Thunder, > What we believe may be happening is that most of the topics have no backlog, but one topic has all the backlog (this is because one of the topics accounts for ~60% of the total message rate). Could there be something inducing extra latency on processing the one topic with a backlog

Re: Old style "low level" Tasks with alternative deployment model(s)

at java.util.concurrent.locks.AbstractQueuedSynchronizer$ > ConditionObject.await(AbstractQueuedSynchronizer.java:2039) > at java.util.concurrent.ScheduledThreadPoolExecutor$ > DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081) > at java.util.concurrent.ScheduledThreadPoolExecut

Re: Old style "low level" Tasks with alternative deployment model(s)

Hi Thunder, Can you please take and attach a thread dump with this? Thanks, Prateek On Fri, Mar 16, 2018 at 4:47 PM, Thunder Stumpges wrote: > It appears it IS hung while serializing the JobModel... very strange! I > added some debug statements around the calls: > >

Re: Welcome Xinyu as new Samza PMC!

This is great news. Congrats Xinyu, and thanks for your contributions! > On Jan 17, 2018, at 10:39 AM, Srinivasulu Punuru wrote: > > Congrats Xinyu, Very well deserved! > > > From: Jagadish Venkatraman > Sent:

Re: Review Request 63267: Add instructions to README.md

branch this was tested on, and I'll copy and update for the other branch. - Prateek Maheshwari On Oct. 24, 2017, 3:54 p.m., Xinyu Liu wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.

Re: Review Request 63267: Add instructions to README.md

tested on the latest branch or on master? Let's commit to whichever it was, and I'll copy it over and update for the other branch. - Prateek Maheshwari On Oct. 24, 2017, 3:54 p.m., Xinyu Liu wrote: > > --- > This is an auto

Re: Kafka client.id collision

+1 for adding system name to the client id. - Prateek On Thu, Jul 20, 2017 at 10:43 AM, Navina Ramesh (Apache) wrote: > Hi David, > > I think this is expected to occur as a warning since we spin up all kafka > clients with the same client-id, which is $job.name + $job.id. >

Re: [DISCUSS] SEP-2: ApplicationRunner Design

gt; > > > > For this version of API, seems we don't need the > StreamApplication > >>>> > > > wrapper > >>>> > > > > as well as exposing the StreamGraph. Do you think we are on > the > >>>> right &g

Re: [DISCUSS] SEP-6: Support Watermark Across Intermediate Streams for Batch Processing

Hi Xinyu, Thanks for the proposal. Some requests for clarifications. Let's update the SEP directly instead of replying here. E.g., in "For any following intermediate stream whose input streams are all end-of-stream, it will be marked as pending EOS" - Should clarify that (IIUC) something is

Re: [VOTE] Apache Samza 0.13.0 RC0

Resent the CANCEL email, hopefully it makes it this time. - Prateek On Wed, May 17, 2017 at 2:08 PM, Navina Ramesh (Apache) wrote: > Prateek told me that he sent out a cancel email. It didn't reach the > mail-archive I think. Lately, we have this kind of issues where the

[DISCUSS] Samza 0.13.0 release

Hi all, There have been quite a lot of new features added to master since 0.12 release to warrant a new major release. At LinkedIn, we've done functional and performance testing against master in the past weeks, and deployed jobs with the latest build in production. We will continue to test for

  1   2   >