[GitHub] beam pull request #4074: [BEAM-3130] View.asMap() causes a ClassCastExceptio...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/4074 [BEAM-3130] View.asMap() causes a ClassCastException in Apex runner Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA issue. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @jkff You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-3130_View.asMap Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/4074.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4074 commit 266b521b605ee6e2601af4d2f8e09562e212c942 Author: Thomas Weise Date: 2017-11-03T17:49:10Z [BEAM-3130] View.asMap() causes a ClassCastException in Apex runner ---
[GitHub] beam pull request #3893: [BEAM-1037] Support for new State API in ApexRunner
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/3893 [BEAM-1037] Support for new State API in ApexRunner Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA issue. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @kennknowles You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-1037.ApexStatefulProcessing Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3893.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3893 commit 0dd01bd6ef956dce8ac321e4e8b69ad6996ea198 Author: Thomas Weise Date: 2017-09-23T02:11:56Z BEAM-1037 Support for new State API in ApexRunner ---
[GitHub] beam pull request #3529: BEAM-2575 ApexRunner doesn't emit watermarks for ad...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/3529 BEAM-2575 ApexRunner doesn't emit watermarks for additional outputs Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @reuvenlax @kennknowles You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-2575_additonalOutputs Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3529.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3529 commit cb5061e7149519cb18673f4c572757dce3cc7bd1 Author: Thomas Weise Date: 2017-07-09T18:57:43Z BEAM-2575 ApexRunner doesn't emit watermarks for additional outputs --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2952: Beam 831 par do chaining 2.0.0
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2952 Beam 831 par do chaining 2.0.0 Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @kennknowles You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-831-ParDoChaining-2.0.0 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2952.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2952 commit 6eab5c9465bda3da4d8a1ea9f73a74e9c8faec85 Author: chinmaykolhatkar Date: 2017-03-01T11:29:46Z [BEAM-831] ParDo Fusion of Apex Runner commit 3f5282d515fa53516fda6d0376cc912560fd6d85 Author: Thomas Weise Date: 2017-05-05T13:45:34Z [BEAM-831] Fix chaining, add test. closes #2216 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2927: [BEAM-831] ParDo Chaining of Apex Runner
Github user tweise closed the pull request at: https://github.com/apache/beam/pull/2927 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2927: [BEAM-831] ParDo Chaining of Apex Runner
GitHub user tweise reopened a pull request: https://github.com/apache/beam/pull/2927 [BEAM-831] ParDo Chaining of Apex Runner Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @kennknowles based on #2216 You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-831-ParDoChaining Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2927.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2927 commit e09aceff2276955edd481981013738a63d738bcb Author: chinmaykolhatkar Date: 2017-03-01T11:29:46Z [BEAM-831] ParDo Fusion of Apex Runner commit cad694ae0f641b69e3a12eb15b82a3234b793216 Author: Thomas Weise Date: 2017-05-05T13:45:34Z [BEAM-831] Adjustments to the chaining logic. closes #2216 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2927: [BEAM-831] ParDo Chaining of Apex Runner
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2927 [BEAM-831] ParDo Chaining of Apex Runner Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @kennknowles based on #2216 You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-831-ParDoChaining Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2927.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2927 commit e09aceff2276955edd481981013738a63d738bcb Author: chinmaykolhatkar Date: 2017-03-01T11:29:46Z [BEAM-831] ParDo Fusion of Apex Runner commit cad694ae0f641b69e3a12eb15b82a3234b793216 Author: Thomas Weise Date: 2017-05-05T13:45:34Z [BEAM-831] Adjustments to the chaining logic. closes #2216 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2912: [BEAM-2180] update Apex version to 3.6.0
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2912 [BEAM-2180] update Apex version to 3.6.0 Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam apex-3.6.0 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2912.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2912 commit 0066ca8d9bca3a5e2106548f2736351913c7f681 Author: Thomas Weise Date: 2017-05-02T15:21:45Z [BEAM-2180] update Apex version to 3.6.0 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2855: [BEAM-1888] ApexRunner SDF support
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2855 [BEAM-1888] ApexRunner SDF support Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- @jkff @kennknowles The feature isn't fully working yet, there is a problem with firing all processing timers before final watermark which I have not resolved yet. I would however like to merge the current state (plus some cleanup) so that branch does not keep going out of sync. I will mention below the things the I will remove from the PR when you are ready to merge it. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam Apex-SDF Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2855.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2855 commit aa8e116dba1ba4eff7584278931aa0bb306e8854 Author: Thomas Weise Date: 2017-04-08T20:58:48Z ApexRunner SDF support --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2782: [BEAM-2022] fix triggering for processing time time...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2782 [BEAM-2022] fix triggering for processing time timers Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @kennknowles You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-2022-processingTimeTimers Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2782.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2782 commit eb860388a8626837655e82171c8480421384e419 Author: Thomas Weise Date: 2017-04-29T08:17:22Z BEAM-2022 fix triggering for processing time timers --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2742: [BEAM-1766] Remove Aggregators from Apex runner
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2742 [BEAM-1766] Remove Aggregators from Apex runner Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @kennknowles You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-1766 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2742.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2742 commit 62fc6489699130b50237731105884d3a3f993db9 Author: Thomas Weise Date: 2017-04-27T16:13:19Z BEAM-1766 Remove Aggregators from Apex runner --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2734: [BEAM-1981] Fix ApexTimerInternals serialization er...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2734 [BEAM-1981] Fix ApexTimerInternals serialization error. Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @kennknowles @dhalperi You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-1981-ApexTimerInternals Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2734.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2734 commit d85da488970677c5b90eb5dd7f2fbb88fb68ec09 Author: Thomas Weise Date: 2017-04-27T09:06:50Z BEAM-1981 Fix ApexTimerInternals serialization error. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam-site pull request #219: [BEAM-825] Fill in the documentation/runners/ap...
GitHub user tweise opened a pull request: https://github.com/apache/beam-site/pull/219 [BEAM-825] Fill in the documentation/runners/apex portion of the website R: @davorbonaci This is on top of #98 Please note that the example command doesn't actually use HDFS yet, the provider isn't present. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/incubator-beam-site pr98 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam-site/pull/219.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #219 commit 468d2fd6e12e6d97f6cded081786193f62a71546 Author: Sandeep Deshmukh Date: 2016-12-01T13:49:17Z [BEAM-825] Fill in the documentation/runners/apex portion of the website commit ec5b573895b9a37f86d1015b055ae9bcb2b119da Author: Thomas Weise Date: 2017-04-21T07:16:59Z Merge commit 'refs/pull/98/head' of https://github.com/apache/beam-site into pr98 commit b681fa2217eba34400c83693ea8d2a55cd2e0639 Author: Thomas Weise Date: 2017-04-21T07:55:52Z Fix Apex runner instructions (pending review comments and other changes) closes #98 --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2473: [BEAM-1053] ApexGroupByKeyOperator serialization is...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2473 [BEAM-1053] ApexGroupByKeyOperator serialization issues Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @jkff Probably this code will go away after the SDF work but this bug is trivial to fix and has been there for a while, so let's close it out separately. For stateInternals it was already addressed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-1053_ApexGroupByKeySerialization Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2473.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2473 commit adf378568e7c676c3b2780c07caae679ea461f01 Author: Thomas Weise Date: 2017-04-08T20:01:01Z BEAM-1053 ApexGroupByKeyOperator serialization issues --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2472: [BEAM-1390] Update top level README.md to include A...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2472 [BEAM-1390] Update top level README.md to include Apex Runner Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-1390-README Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2472.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2472 commit 0667f9aa3bad1e33705db1de7ec56d3b1c5946e9 Author: Thomas Weise Date: 2017-04-08T19:48:09Z BEAM-1390 Update top level README.md to include Apex Runner --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2450: [BEAM-1887] Switch Apex ParDo to new DoFn.
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2450 [BEAM-1887] Switch Apex ParDo to new DoFn. Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- R: @kennknowles @jkff You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-1887_Apex-NewDoFn Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2450.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2450 commit 629887cb124134cdae06087cb5159efa834df0b9 Author: Thomas Weise Date: 2017-04-04T07:33:35Z BEAM-1887 Switch Apex ParDo to new DoFn. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #2125: [BEAM-1571] fix FlattenPCollectionList with single ...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/2125 [BEAM-1571] fix FlattenPCollectionList with single input translation in ApexRunner Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- R: @tgroh fix for #2120 You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-1571-singleton-flatten Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2125.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2125 commit 0166c996039042452b17cee51af20b2d2f32f8a4 Author: Thomas Weise Date: 2017-02-28T06:32:28Z BEAM-1571 fix FlattenPCollectionList with single input translation in ApexRunner --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #1850: [BEAM-980] Support configuration of Apex DAG throug...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/1850 [BEAM-980] Support configuration of Apex DAG through properties file. Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- R: @kennknowles You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-980 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/1850.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1850 commit 02bbf4357fe1e10c8646d4101a721721d400e997 Author: Thomas Weise Date: 2017-01-26T06:22:36Z BEAM-980 Support configuration of Apex DAG through properties file. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam pull request #1727: [BEAM-1140] terminate stream in interval following ...
GitHub user tweise opened a pull request: https://github.com/apache/beam/pull/1727 [BEAM-1140] terminate stream in interval following the final mark to reduce test flakiness (stop gap measure). Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/beam BEAM-1140 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/1727.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1727 commit bb11170915f5c05629f591304f01fbc528e2ea57 Author: Thomas Weise Date: 2017-01-03T05:58:57Z BEAM-1140 terminate stream in interval following the final mark to reduce test flakiness (stop gap measure). --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] beam-site pull request #119: Added post for 0.4.0 release with Apex runner a...
GitHub user tweise opened a pull request: https://github.com/apache/beam-site/pull/119 Added post for 0.4.0 release with Apex runner addition. @davorbonaci please review You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/incubator-beam-site added-apex-runner-post Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam-site/pull/119.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #119 commit 6ecb17e61b3353f19fd35882de41df478c659a24 Author: Thomas Weise Date: 2016-12-31T18:10:28Z Added post for 0.4.0 release with Apex runner addition. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-beam pull request #1683: Remove warnings in Apex runner tests.
GitHub user tweise opened a pull request: https://github.com/apache/incubator-beam/pull/1683 Remove warnings in Apex runner tests. Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the PR title is formatted like: `[BEAM-] Description of pull request` - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes). - [ ] Replace `` in the title with the actual Jira issue number, if there is one. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/tweise/incubator-beam remove-warnings Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-beam/pull/1683.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1683 commit bab424bb9b1f420a28dd3505ed721a5462021265 Author: Thomas Weise Date: 2016-12-22T01:39:36Z Remove warnings in Apex runner tests. --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
