Thank you Fred for shepherding this release and to everyone for your
contributions!
On Fri, Aug 25, 2017 at 5:40 PM Fred Haifeng Ji
wrote:
> Hi, all,
>
> I am pleased to let you know that we have officially released Samza 0.13.1!
>
> Huge thanks to everyone for working on the features and bugs i
Hi, Xiaochuan,
Please refer to the document here:
https://samza.apache.org/learn/tutorials/0.13/samza-async-user-guide.html
As stated, by default, when task.max.concurrency=1, in-order processing
within a task is guaranteed, no matter whether you implement StreamTask or
AsyncStreamTask. The engin
Hi, all,
I am pleased to let you know that we have officially released Samza 0.13.1!
Huge thanks to everyone for working on the features and bugs in this
release, and cooperating in the release process.
Here is the announcement blog:
https://blogs.apache.org/samza/
Cheers!
Fred
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/285
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user fredji97 opened a pull request:
https://github.com/apache/samza/pull/288
SAMZA-1409 add missing parts and make guideline clearer for docs/README.md
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fredji97/samza master
Hi Jagadish,
This is a rather late reply but I don't think I understand of the effect of
changing job.container.thread.pool.size config in the synchronous case very
well.
Suppose I have an input topic partitioned by memberID processed by a
synchronous job.
Does increasing container thread pool siz
Github user fredji97 closed the pull request at:
https://github.com/apache/samza/pull/287
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
GitHub user fredji97 opened a pull request:
https://github.com/apache/samza/pull/287
SAMZA-1049 add the missing parts and make guideline clearer for
docs/README.md
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fredji97/samza m
Github user fredji97 closed the pull request at:
https://github.com/apache/samza/pull/276
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
GitHub user fredji97 opened a pull request:
https://github.com/apache/samza/pull/286
SAMZA-1408 update the branch doc for 0.13.1 release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fredji97/samza 0.13.1_doc
Alternatively you
GitHub user fredji97 opened a pull request:
https://github.com/apache/samza/pull/285
SAMZA-1408 update master doc to use 0.14.0-SNAPSHOT after 0.13.1 release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fredji97/samza master_d
GitHub user sborya opened a pull request:
https://github.com/apache/samza/pull/284
SAMZA-1385: Coordination utils factory with distributed lock
this PR includes some changes from another PR. I will re-merge it again,
after the other PR is in.
You can merge this pull request into a
GitHub user shanthoosh opened a pull request:
https://github.com/apache/samza/pull/283
SAMZA-1406: Fix potential orphaned containers problem in stand alone.
Changes:
* Switch from `executorService.shutdown()` to
`executorService.shutdownNow()` in `stopScheduler()` implement
Hi Shuqi,
Glad that you figured out the problem. In general, we recommend Filesystem
instances should always be scoped to their corresponding objects and
discourage sharing.
Please do let us know should you need more help!
Thanks
-- Forwarded message -
From: 舒琦
Date: Thu, Aug
14 matches
Mail list logo
