GitHub user weisong44 opened a pull request:
https://github.com/apache/samza/pull/813
SAMZA-2004: Add ability to disable table metrics
For jobs with very high throughput, it is desirable to disable metrics on
tables. We would introduce the option to disable all metrics for a table o
We are replacing a node.js app that consumed topics on a Kafka cluster with
Samza jobs. We use kafka-offsets to trigger alerts based on message lag. e.g.,
message lag is greater than 10, wake up support persons.
Samza doesn't use the same mechanism for offset storage and the tools for
examinin
GitHub user shenodaguirguis opened a pull request:
https://github.com/apache/samza/pull/814
SAMZA-2002 SamzaSQL Diagnostics: instrument rest of operators (except join)
and at Query level
After instrumenting Project operator in Samza-1997, this PR instruments the
rest of operators,
GitHub user vjagadish1989 opened a pull request:
https://github.com/apache/samza/pull/815
Clean-up open source docs for Samza SQL
@atoomula @srinipunuru FYI..
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vjagadish1989/samza web
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/815
---
GitHub user weisong44 opened a pull request:
https://github.com/apache/samza/pull/816
SAMZA-2006: Removed config from table provider constructor
With the latest API change in Samza 1.0, config can be obtained from
Context object during init(), therefore we do not to pass this in the
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/816
---
Have you looked into KafkaSystemConsumerMetrics? Is the meaning of "lag"
there different from what you mean?
Jeremiah Adams writes:
We are replacing a node.js app that consumed topics on a Kafka cluster with
Samza jobs. We use kafka-offsets to trigger alerts based on message lag. e.g.,
messa
