Dear Apache Enthusiast,
(You’re receiving this because you are subscribed to one or more user
mailing lists for an Apache Software Foundation project.)
TL;DR:
* Apache Roadshow DC is in 3 weeks. Register now at
https://apachecon.com/usroadshowdc19/
* Registration for Apache Roadshow Chicago is
It appears that the issue is related to the KafkaCheckpointLogKey.java
constructor. grouperFactoryClassName here is null. THe documentation indicates
that task.name.grouper.factory config setting has a default value of
org.apache.samza.container.grouper.task.GroupByContainerCountFactory. I
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?
asfgit closed pull request #934: SAMZA-1935 : Refactor TaskContextImpl to not
include access to objects that are only used internally
URL: https://github.com/apache/samza/pull/934
This is an automated message from the Apache
sborya commented on a change in pull request #939: SAMZA-2122: Fix the task
caught-up logic which doesn't handle no incoming messages
URL: https://github.com/apache/samza/pull/939#discussion_r263078743
##
File path:
samza-core/src/main/scala/org/apache/samza/container/TaskInstance.
sborya commented on a change in pull request #939: SAMZA-2122: Fix the task
caught-up logic which doesn't handle no incoming messages
URL: https://github.com/apache/samza/pull/939#discussion_r263078808
##
File path:
samza-core/src/main/scala/org/apache/samza/container/TaskInstance.
xinyuiscool commented on a change in pull request #939: SAMZA-2122: Fix the
task caught-up logic which doesn't handle no incoming messages
URL: https://github.com/apache/samza/pull/939#discussion_r263086086
##
File path:
samza-core/src/main/scala/org/apache/samza/container/TaskInst
xinyuiscool commented on a change in pull request #939: SAMZA-2122: Fix the
task caught-up logic which doesn't handle no incoming messages
URL: https://github.com/apache/samza/pull/939#discussion_r263086035
##
File path:
samza-core/src/main/scala/org/apache/samza/container/TaskInst
cameronlee314 opened a new pull request #940: SAMZA-2121: Add checkpoint offset
field to IncomingMessageEnvelope
URL: https://github.com/apache/samza/pull/940
This is the first step for implementing
https://issues.apache.org/jira/browse/SAMZA-2120.
sborya merged pull request #939: SAMZA-2122: Fix the task caught-up logic which
doesn't handle no incoming messages
URL: https://github.com/apache/samza/pull/939
This is an automated message from the Apache Git Service.
To r
I am prototyping an application where I have two input topics and two
output topics. The application also uses a rocksdb state store that is
backed by kafka.
I followed WikipediaZkLocalApplication example, but the application always
exits without listening for messages from topic. I could see the
Sanil15 commented on a change in pull request #920: SAMZA-2106: Samza app and
job config refactor
URL: https://github.com/apache/samza/pull/920#discussion_r263162204
##
File path:
samza-core/src/main/java/org/apache/samza/execution/ExecutionPlanner.java
##
@@ -113,7 +115,
Sanil15 commented on a change in pull request #920: SAMZA-2106: Samza app and
job config refactor
URL: https://github.com/apache/samza/pull/920#discussion_r263162260
##
File path:
samza-core/src/main/java/org/apache/samza/runtime/RemoteApplicationRunner.java
##
@@ -84,7 +
Sanil15 commented on a change in pull request #920: SAMZA-2106: Samza app and
job config refactor
URL: https://github.com/apache/samza/pull/920#discussion_r263162324
##
File path: samza-core/src/main/java/org/apache/samza/util/JobConfigUtil.java
##
@@ -0,0 +1,72 @@
+/*
+ *
prateekm commented on issue #897: SEP-19 : Refactoring to remove
localityManager from JobModel
URL: https://github.com/apache/samza/pull/897#issuecomment-470334092
@rmatharu We also want to move the JobModel to samza-api (where
ContainerModel and TaskModel already are).
--
Can you please attach the container logs? I noticed only job configurations
were attached.
--
Bharath
From: Anoop Krishnakumar
Reply-To: "dev@samza.apache.org"
Date: Wednesday, March 6, 2019 at 1:54 PM
To: "dev@samza.apache.org"
Subject: Trouble running samza 0.14 in standalone mode
I am pro
cameronlee314 opened a new pull request #941: SAMZA-2120: Enable custom
handling of ConsumerRecords consumed by Kafka
URL: https://github.com/apache/samza/pull/941
This includes the code from https://github.com/apache/samza/pull/940.
For this PR, it would be practical to just look at co
xinyuiscool merged pull request #920: SAMZA-2106: Samza app and job config
refactor
URL: https://github.com/apache/samza/pull/920
This is an automated message from the Apache Git Service.
To respond to the message, please lo
rmatharu opened a new pull request #942: Bugfix: Recent CSM refactor was
causing some metrics to not be emitted. Fixed -restore-time metric.
URL: https://github.com/apache/samza/pull/942
This is an automated message from the
Hello everyone,
We have added couple of major features to master since 1.0.0 that warrants
a major release.
Within LinkedIn, some of these features have already been tested as part of
our test suites. We plan to continue our testing in coming weeks to
validate the stability prior to release.
Her
Hello everyone,
We have added couple of major features to master since 1.0.0 that warrants
a major release.
Within LinkedIn, some of these features have already been tested as part of
our test suites. We plan to continue our testing in coming weeks to
validate the stability prior to release.
Her
Hi, Anoop,
1. Please provide the full log file if possible. Just listing out a single
log line reporting the failure does not help.
2. Is there any reason that you still stay with Samza 0.14? I would highly
recommend to upgrade to 1.0 since there are tons of API and standalone
related improvements
+1 (binding)
On Wed, Mar 6, 2019 at 10:08 PM Daniel Chen wrote:
> Hello everyone,
>
> We have added couple of major features to master since 1.0.0 that warrants
> a major release.
>
> Within LinkedIn, some of these features have already been tested as part of
> our test suites. We plan to contin
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262815895
##
File path:
samza-core/src/main/java/org/apache/samza/coordinator/CoordinationUtils.java
###
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262817152
##
File path:
samza-core/src/main/java/org/apache/samza/coordinator/DistributedReadWriteLock.ja
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262818100
##
File path:
samza-core/src/main/java/org/apache/samza/coordinator/DistributedReadWriteLock.ja
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262813679
##
File path:
samza-core/src/main/java/org/apache/samza/runtime/LocalApplicationRunner.java
##
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262817813
##
File path:
samza-core/src/main/java/org/apache/samza/coordinator/DistributedReadWriteLock.ja
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262814871
##
File path:
samza-core/src/main/java/org/apache/samza/runtime/LocalApplicationRunner.java
##
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262816170
##
File path:
samza-core/src/main/java/org/apache/samza/coordinator/CoordinationUtils.java
###
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262815650
##
File path:
samza-core/src/main/java/org/apache/samza/coordinator/CoordinationUtils.java
###
mynameborat commented on a change in pull request #938: SAMZA-1531: Support
run.id in standalone for batch processing.
URL: https://github.com/apache/samza/pull/938#discussion_r262814180
##
File path:
samza-core/src/main/java/org/apache/samza/runtime/LocalApplicationRunner.java
##
32 matches
Mail list logo
