GitHub user vjagadish1989 opened a pull request:
https://github.com/apache/samza/pull/210
Update RELEASE documentation to include steps related to integration tests
You can merge this pull request into a Git repository by running:
$ git pull
Chatted with Yi offline and we both agree on keeping watermarks and
end-of-stream separate. @Chris: thanks for the detailed explanation.
@Yi: for you questions:
1) The propagation and the reconciliation process of watermarks and
end-of-stream are the same. As we discussed, this can be done
Verified PGP key
The build and check-all scripts were successful for me.
I had trouble with the integration tests.
Looks like `./samza-test/src/main/python/configs/tests.json` needs to
be updated
s.t. '"samza_executable": "samza-test_2.11-0.13.0.tgz"'
On Thu, Jun 1, 2017 at 11:55 AM, Boris S
Github user sborya closed the pull request at:
https://github.com/apache/samza/pull/200
---
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
Downloaded, ran build and test and integration tests on Linux RedHat.
Integration tests passed (using python 2.7).
+1 (non-binding)
On Wed, May 31, 2017 at 7:33 PM, Jagadish Venkatraman
wrote:
> This is a call for a vote on a release of Apache Samza 0.13.0. Thanks to
>
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/198
---
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
I would recommend keeping watermarks and end-of-stream separate. It is
lossy to represent end-of-stream as a watermark - does that mean we
hit the max watermark on a stream or that we're in a bounded stream
with an end-of-stream marker? Also keep in mind that watermarks will
eventually be user
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/209
---
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
GitHub user jmakes opened a pull request:
https://github.com/apache/samza/pull/209
Adding gpg key for Jake Maes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jmakes/samza gpg-key
Alternatively you can review and apply these
Hey Yi,
Thanks much for the comment. I have updated the doc to address all your
comments except the one related to the interface. I am not sure I
understand your suggestion of the new interface. Will discuss tomorrow.
Thanks,
Dong
On Wed, May 31, 2017 at 4:29 PM, Yi Pan
Hey Navina,
My point is that, suppose the underlying system allows user to select
arbitrary partition number during partition expansion, which I assume is
applicable to all input systems that Samza will use, then we can easily
enforce the rule that expansion of partitions should always happen by
11 matches
Mail list logo