[GitHub] beam pull request #3802: [BEAM-2822] Add fn API progress reporting protos
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3802 [BEAM-2822] Add fn API progress reporting protos 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). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam progress_proto Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3802.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 #3802 commit a953356674adbfcfc97be019c8cc494ef94d2210 Author: Vikas Kedigehalli Date: 2017-09-01T16:45:22Z Add fn API progress reporting protos --- 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 #3784: [BEAM-2822] Enable progress request handling in pyt...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3784 [BEAM-2822] Enable progress request handling in python SDK harness 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). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam py_progress_pool Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3784.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 #3784 commit 20a8ce6ccb899b0a7abc203641ca10dbb7e25284 Author: Vikas Kedigehalli Date: 2017-08-29T19:32:38Z Enable progress request handling in python SDK harness --- 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 #3781: [BEAM-2820] Measure time spent for active transitio...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3781 [BEAM-2820] Measure time spent for active transition in python StateSampler 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). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam state_sampler Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3781.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 #3781 commit cec7c6925368f0ebe6e7b95afb3f5aa33ab74752 Author: Vikas Kedigehalli Date: 2017-08-29T16:58:41Z Measure time spent for active transitions in StateSampler --- 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 #3586: Increase the gRPC message size to max value
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3586 Increase the gRPC message size to max value 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-1234] Fixes bug in ApproximateQuantiles`, where you replace `BEAM-1234` 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). --- The default message size that can be sent or received over gRPC is 4MB. For the fn API case we do buffering at a layer above, so setting the message size at the gRPC level to a max value. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam msg_size Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3586.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 #3586 commit 2814ed32b79c53451635b8cbc5b264b2f6c0837c Author: Vikas Kedigehalli Date: 2017-07-18T17:06:46Z Increase the gRPC message size to max value --- 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 #3559: Retry on Datastore client python socket errors
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3559 Retry on Datastore client python socket errors 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/vikkyrk/incubator-beam py_ds_retry Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3559.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 #3559 commit 288def3a556ded4dc4c116dd7b7c9ff42b671ef8 Author: Vikas Kedigehalli Date: 2017-07-13T17:29:23Z datastoreio: retry on socket errors --- 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 #3445: [BEAM-2509}] Enable grpc controller in fn_api_runne...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3445 [BEAM-2509}] Enable grpc controller in fn_api_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). --- You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam fn_api_runner_test Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3445.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 #3445 commit 556d291bc3154695450ac18076c82790ecb7 Author: Vikas Kedigehalli Date: 2017-06-27T01:47:39Z Enable grpc controller in fn_api_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 #3431: Fix python fn API data plane remote grpc port acces...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3431 Fix python fn API data plane remote grpc port access 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/vikkyrk/incubator-beam py_fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3431.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 #3431 commit 19251ebd9ddd9e4ef162bf91c5056dfe8a595e66 Author: Vikas Kedigehalli Date: 2017-06-23T18:50:12Z Fix python fn API data plane remote grpc port access --- 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 #3393: Fix Dataflow runner test to call pipeline.run inste...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3393 Fix Dataflow runner test to call pipeline.run instead of runner.run 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/vikkyrk/incubator-beam df_fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3393.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 #3393 commit 3fe720641159df9303bc4108073af11a15eb4688 Author: Vikas Kedigehalli Date: 2017-06-19T18:24:14Z Fix dataflow runner test to call pipeline.run instead of runner.run --- 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 #3385: Add dry run option to DataflowRunner in python SDK
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3385 Add dry run option to DataflowRunner in python SDK 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/vikkyrk/incubator-beam df_runner_dry_run Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3385.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 #3385 commit 388890df98c8de889a36e8b48db13c8faf4f9b4d Author: Vikas Kedigehalli Date: 2017-06-17T00:18:57Z Add dry run option to DataflowRunner --- 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 #3350: Fix WindowValueCoder for large timestamps
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3350 Fix WindowValueCoder for large timestamps 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/vikkyrk/incubator-beam wv_coder Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3350.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 #3350 commit 614b4f8eddad37c91f3cf6a3d55269d180b057eb Author: Vikas Kedigehalli Date: 2017-06-13T06:11:22Z Fix WindowValueCoder for large timestamps --- 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 #3349: Python streaming Create override as a composite of ...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3349 Python streaming Create override as a composite of Impulse and a 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`. - [ ] 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/vikkyrk/incubator-beam impulse Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3349.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 #3349 commit d75e7e0645876feb972a67ac7b1aea7081988e41 Author: Vikas Kedigehalli Date: 2017-06-13T05:32:39Z Python streaming Create override as a composite of Impulse and a 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 #3317: python pubsub io fixes for streaming
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3317 python pubsub io fixes for streaming 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). --- - include coder info in pubsub source and sink - use `GlobalWindowCoder` as a place holder instead of default `PickleCoder` - fix pubsub source to accept either a topic or subscription. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam pubsub Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3317.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 #3317 commit 58285834ca29ad9be8189aa526fac748cea7c079 Author: Vikas Kedigehalli Date: 2017-06-07T23:28:18Z Add coder info to pubsub io --- 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 #3316: Make BytesCoder to be a known type
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3316 Make BytesCoder to be a known type 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/vikkyrk/incubator-beam streaming Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3316.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 #3316 commit ec2fb60df664092f7907fc308c0b8b6caabcb8a0 Author: Vikas Kedigehalli Date: 2017-06-07T23:26:21Z Make BytesCoder to be a known type --- 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 #3155: Use built-in cmp python function in comparing Datas...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3155 Use built-in cmp python function in comparing Datastore paths 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/vikkyrk/incubator-beam ds_py Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3155.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 #3155 commit 2ede86de42b005d7d393ac24dd6a6f3ed9093235 Author: Vikas Kedigehalli Date: 2017-05-15T22:50:25Z Use built-in cmp python function in comparing datastore paths --- 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 #3098: Fix lint error in fake_datastore.py
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3098 Fix lint error in fake_datastore.py 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/vikkyrk/incubator-beam fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3098.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 #3098 commit b5cc8b85f3fbe279d0817782b01caaee4c981a3c Author: Vikas Kedigehalli Date: 2017-05-11T21:39:55Z fix lint error in fake_datastore.py --- 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 #3088: Mark internal modules in python datastoreio
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3088 Mark internal modules in python datastoreio 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/vikkyrk/incubator-beam py_doc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3088.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 #3088 --- 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 #3083: Cherry-pick #3072: Remove protobuf and http-client ...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3083 Cherry-pick #3072: Remove protobuf and http-client dependency from runners/google-cloud-dataflow 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/vikkyrk/incubator-beam cp_3072 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3083.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 #3083 commit 998e42f90c58726f31be5621369784532d2a67ff Author: Vikas Kedigehalli Date: 2017-05-11T00:39:01Z Remove protobuf and http-client dependency from runners/google-cloud-dataflow --- 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 #3072: Remove protobuf and http-client dependency from Dat...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3072 Remove protobuf and http-client dependency from Dataflow runner runners/google-cloud-dataflow 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/vikkyrk/incubator-beam pbf Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3072.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 #3072 commit 8be5466567dfe79fb7382c56cee44ab5c39ac01c Author: Vikas Kedigehalli Date: 2017-05-11T00:39:01Z Remove protobuf and http-client dependency from runners/google-cloud-dataflow --- 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 #3028: Shade protobuf-java in runners/google-cloud-dataflo...
Github user vikkyrk closed the pull request at: https://github.com/apache/beam/pull/3028 --- 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 #3063: Fix a typo in TestDataflowRunnerTest
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3063 Fix a typo in TestDataflowRunnerTest 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/vikkyrk/incubator-beam fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3063.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 #3063 commit 22d87785cf1bb32af31628813f20a2d2ad854dcd Author: Vikas Kedigehalli Date: 2017-05-10T22:19:50Z Fix a typo in TestDataflowRunnerTest --- 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 #3062: Skip generating empty jars for parent poms
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3062 Skip generating empty jars for parent poms 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/vikkyrk/incubator-beam jar_plugin Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3062.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 #3062 commit 96528716f72451baed1640981d7a2131d9087500 Author: Vikas Kedigehalli Date: 2017-05-10T21:29:45Z Skip generating empty jars for parent poms --- 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 #3026: Include sun.reflect in allowed api surface packages...
Github user vikkyrk closed the pull request at: https://github.com/apache/beam/pull/3026 --- 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 #3028: Shade protobuf-java in runners/google-cloud-dataflo...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3028 Shade protobuf-java in runners/google-cloud-dataflow-java 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/vikkyrk/incubator-beam df_shade Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3028.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 #3028 commit c668642ab5b4e5df0b0db93d6325191cdfd11b88 Author: Vikas Kedigehalli Date: 2017-05-09T23:47:06Z shade protobuf-java in runners/google-cloud-dataflow-java --- 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 #3026: Include sun.reflect in allowed api surface packages...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3026 Include sun.reflect in allowed api surface packages for GcpCoreApiSurfaceTest 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/vikkyrk/incubator-beam release-2.0.0 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3026.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 #3026 commit c7b3df656aee00ff7c09db1a47bb19262f759c06 Author: Vikas Kedigehalli Date: 2017-05-10T00:44:31Z Include sun.reflect in allowed api surface packages for GcpCoreApiSurfaceTest --- 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 #3009: Fix checkstyle issue in ApiSurface
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3009 Fix checkstyle issue in ApiSurface 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/vikkyrk/incubator-beam fix_checkstyle Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3009.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 #3009 commit bc2f619217fc5b3644f08b9391c6fa5511df650f Author: Vikas Kedigehalli Date: 2017-05-09T21:49:32Z Fix checkstyle issue in ApiSurface --- 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 #3004: [BEAM-1871] [BEAM-1019 ] Cherry-pick: Shade depende...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/3004 [BEAM-1871] [BEAM-1019 ] Cherry-pick: Shade dependencies in sdks/coreShade dependencies in sdks/core 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). --- - cherry-pick of [BEAM-1871] [BEAM-1019 ] https://github.com/apache/beam/pull/2996 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam shade Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/3004.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 #3004 commit d540ac63862b980abf151e98e924ec67782dc5d6 Author: Vikas Kedigehalli Date: 2017-05-09T18:41:29Z Shade dependencies in sdks/core --- 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 #2996: [BEAM-1871] [BEAM-1019 ] Shade dependencies in sdks...
Github user vikkyrk closed the pull request at: https://github.com/apache/beam/pull/2996 --- 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 #2996: [BEAM-1871] [BEAM-1019 ] Shade dependencies in sdks...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2996 [BEAM-1871] [BEAM-1019 ] Shade dependencies in sdks/core 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). --- - Shade `com.google.guava:guava`, `com.google.protobuf:protobuf-java`, `net.bytebuddy:byte-buddy`, `org.apache.commons:*` - Shading `net.bytebuddy` fails the `GcpApiSurfaceTest` with `NoClassDefFoundError` for ` org/apache/beam/sdk/repackaged/net/bytebuddy/jar/asm/tree/MethodNode`. Looks like an issue with how `net.bytebuddy` does shading for `org.objectweb.asm`. Either way the `ApiSurfaceTest` should be fixed to be able to prune and load classes lazily. For release-2.0.0 we catch and ignore any class loading errors. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam shade_2.0.0 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2996.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 #2996 commit feee8daa0f90eb779edb44b4cfafcee6b7ac7faf Author: Vikas Kedigehalli Date: 2017-05-09T18:41:29Z Shade dependencies in sdks/core --- 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 #2982: [BEAM-1871] Remove google api BackOff usage from sd...
Github user vikkyrk closed the pull request at: https://github.com/apache/beam/pull/2982 --- 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 #2982: [BEAM-1871] Remove google api BackOff usage from sd...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2982 [BEAM-1871] Remove google api BackOff usage from sdks/core 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). --- - cheryy-pick of https://github.com/apache/beam/pull/2937 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam backoff_2.0.0 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2982.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 #2982 commit 08f10b87dc99c082bbd6f0972ac0972f2a514f70 Author: Vikas Kedigehalli Date: 2017-05-06T02:24:51Z Remove google api BackOff usage from sdks/core --- 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 #2937: [BEAM-1871] Remote google api client from sdks/core
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2937 [BEAM-1871] Remote google api client from sdks/core 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). --- - Remove usage of google api client base64 encoding - Copy google api client versions of BackOff, BackOffUtils and Sleeper classes into sdks/core. - Use an adapters to convert from beam to google api client interfaces. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam thin_sdk_core Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2937.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 #2937 commit 10bfb1b97b8577f177e3add165477bdbe1b42bf6 Author: Vikas Kedigehalli Date: 2017-05-06T02:33:45Z Use guava Base64 encoding instead of google api client commit 11074ebd029e3f76a79b168411a569157d2c28c6 Author: Vikas Kedigehalli Date: 2017-05-06T02:24:51Z Remove google api BackOff usage from sdks/core --- 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 #2907: [BEAM-2143]: Fix default temp location for Dataflow...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2907 [BEAM-2143]: Fix default temp location for DataflowRunner 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). --- - https://github.com/apache/beam/pull/2602 made `gs://some-bucket` path invalid and expects it to be of the form `gs://some-bucket/basename`. So adding `/temp` as the basename for the default `tempLocation`. - Also fix log messages. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam df_temp_loc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2907.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 #2907 commit ea165bfba449cd5572f9342bf8107018dc584a30 Author: Vikas Kedigehalli Date: 2017-05-05T01:30:35Z Fix default temp location for DataflowRunner --- 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 #2889: [BEAM-59] Remove IOChannelUtil/Factory from BigQuer...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2889 [BEAM-59] Remove IOChannelUtil/Factory from BigQueryIO 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/vikkyrk/incubator-beam bq_ioc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2889.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 #2889 commit 8f1216624782e356933a2457168743f7c01aec7d Author: Vikas Kedigehalli Date: 2017-05-04T05:41:06Z Remove IOChannelUtil/Factory from BigQueryIO --- 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 #2873: [BEAM-828] BigQueryIO: Remove tempLocation usage at...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2873 [BEAM-828] BigQueryIO: Remove tempLocation usage at pipeline construction time 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). --- No semantic changes, just moves tempLocation access to runtime. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam bq_templocation Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2873.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 #2873 commit 78ed5740ab97cf6daa99fd62c385ef1c7bc10f35 Author: Vikas Kedigehalli Date: 2017-05-03T22:42:50Z BigQueryIO: Remove tempLocation usage at pipeline construction time --- 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 #2865: [BEAM-1902] Retry on correct error codes for datast...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2865 [BEAM-1902] Retry on correct error codes for datastoreio 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/vikkyrk/incubator-beam ds_retry Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2865.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 #2865 commit bae0fc78f4599b931fd46aa53e00d5356b91d3f5 Author: Vikas Kedigehalli Date: 2017-05-03T20:14:20Z Retry on correct error codes for datastoreio --- 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 #2849: Trigger for Java SDK post submit tests
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2849 Trigger for Java SDK post submit 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`. - [ ] 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/vikkyrk/incubator-beam post_submit_trigger Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2849.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 #2849 commit bc91825a836f421857fcf2439fc989a231c92322 Author: Vikas Kedigehalli Date: 2017-05-02T23:11:09Z Triggers for Java SDK post submit 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. ---
[GitHub] beam pull request #2846: [BEAM-2128] Remove job name usages from BigQueryIO ...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2846 [BEAM-2128] Remove job name usages from BigQueryIO at pipeline construction time 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/vikkyrk/incubator-beam bqio Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2846.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 #2846 commit a70c69408e5ba863abef9061f95e143d9ae034da Author: Vikas Kedigehalli Date: 2017-05-02T20:55:32Z Remove job name usages from BigQueryIO at pipeline construction time --- 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 #2798: [BEAM-59] Remove IOChannelUtils from BigQuery Table...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2798 [BEAM-59] Remove IOChannelUtils from BigQuery TableRowWriter 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/vikkyrk/incubator-beam bq_iochannel Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2798.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 #2798 --- 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 #2775: [BEAM-59] Remove IOChannelUtils from PackageUtil
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2775 [BEAM-59] Remove IOChannelUtils from PackageUtil 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/vikkyrk/incubator-beam package_util Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2775.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 #2775 commit 47ba9832217658f823f87ffc1b5b66197116a990 Author: Vikas Kedigehalli Date: 2017-04-29T01:07:31Z Remove IoChannelUtils from PackageUtil --- 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 #2768: [BEAM-59] Remove IOChannelUtils from a few ITs
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2768 [BEAM-59] Remove IOChannelUtils from a few ITs 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/vikkyrk/incubator-beam ioc_ITs Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2768.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 #2768 commit fb4f259a3ce69ee24370d3366e88742e8a26d047 Author: Vikas Kedigehalli Date: 2017-04-28T19:12:43Z Remove IOChannelUtils from a few ITs commit 840c8e761a0902f32022d0ea360831c7d020cacc Author: Vikas Kedigehalli Date: 2017-04-28T19:14:24Z Use getFileName in NumberedShardedFile --- 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 #2754: [Beam-59] Add getFilename method to ResourceId
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2754 [Beam-59] Add getFilename method to ResourceId 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/vikkyrk/incubator-beam resource_name Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2754.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 #2754 commit cd61d5ea308901dc7ff6add8b984ec793e56f2eb Author: Vikas Kedigehalli Date: 2017-04-27T22:58:26Z Add getFilename method to ResourceId --- 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 #2749: [Beam-59] Remove IOChannelFactory usage from Number...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2749 [Beam-59] Remove IOChannelFactory usage from NumberedShardedFile 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/vikkyrk/incubator-beam numberedshardedfile Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2749.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 #2749 commit 97aae4f5c61383725ff0f368e7ce4f955c9d6aba Author: Vikas Kedigehalli Date: 2017-04-27T21:58:24Z Remove IOChannelFactory usage from NumberedShardedFile --- 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 #2688: [BEAM-2080]: Add a custom enforcer rule to check fo...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2688 [BEAM-2080]: Add a custom enforcer rule to check for banned classes. 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). --- - Add a custom rule to catch banned classes which can be specified using full path like `org/apache/beam/Foo.class` or using wildcards like `org/apache/maven/**` - Disable enforcer plugin in parent pom to avoid circular dependency issues with the custom rule - Move enforcer executions to `pluginManagement` and explicitly include them in `sdks`, `examples` and `runners`. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam mvn_enforcer Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2688.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 #2688 commit 48034b365ab89b4e4f37c64345269cb534a87212 Author: Vikas Kedigehalli Date: 2017-04-21T22:10:21Z Add a custom rule to check for banned classes. --- 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 #2639: Change dataflow Job log from info to debug
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2639 Change dataflow Job log from info to debug 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/vikkyrk/incubator-beam py_log Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2639.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 #2639 commit e232ddecb2bc7f8a5afa129fcd8d9763ed671b59 Author: Vikas Kedigehalli Date: 2017-04-21T22:26:50Z Change dataflow Job log from info to debug --- 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 #2604: Remove bigshuffle from python examples
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2604 Remove bigshuffle from python examples 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/vikkyrk/incubator-beam remove_bigshuffle Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2604.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 #2604 commit 8fda8130bbbef5a5614428508c5a39640301ca8c Author: Vikas Kedigehalli Date: 2017-04-20T00:12:52Z Remove bigshuffle from python examples --- 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 #2543: [BEAM-1956] Modify types for input PCollections of ...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2543 [BEAM-1956] Modify types for input PCollections of Flatten transform 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). --- Modify types for input PCollections of Flatten transform to that of the output PCollection You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam py_flatten_visitor Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2543.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 #2543 commit e3ac1f4d3298b2e32463b6b132dda89706a6bc58 Author: Vikas Kedigehalli Date: 2017-04-14T20:53:13Z Modifying types for input PCollectios of Flatten transform with that of the output PCollection --- 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 #2470: [BEAM-1865]: Fix GroupByKeyInputVisitor for Direct ...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2470 [BEAM-1865]: Fix GroupByKeyInputVisitor for Direct 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). --- - Also handle `None` input types which is the case when `TypeOptions.pipeline_type_check` is disabled. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam py_gbk_type_check Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2470.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 #2470 commit c7f1a44dc5259164f326bef23ff4620b4ffbcb77 Author: Vikas Kedigehalli Date: 2017-04-08T02:22:27Z Fix GroupByKeyInputVisitor for Direct 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 #2446: [BEAM-1895] Python Create as a custom source
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2446 [BEAM-1895] Python Create as a custom source 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/vikkyrk/incubator-beam py_custom_create Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2446.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 #2446 commit 43b8c6ded42054734c3f6d207ffd14b74a048285 Author: Vikas Kedigehalli Date: 2017-04-03T17:01:45Z Create as custom source --- 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 #2409: [BEAM-1865]: Replace Any type with a KV type for in...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2409 [BEAM-1865]: Replace Any type with a KV type for inputs of a GroupByKey step Be sure to do all of the following to help us incorporate your contribution quickly and easily: - Relying on existing tests to ensure nothing breaks. For proper coverage I will defer to BEAM-115 being fixed, which allows the pipeline representation testing in a runner independent way. - [ ] 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/vikkyrk/incubator-beam runner_gbk_coder Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2409.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 #2409 commit 9cad8884e350eb9332f2677f99de5cb646d11c06 Author: Vikas Kedigehalli Date: 2017-04-03T03:46:55Z Replace Any type with a KV type for inputs of a GroupByKey step --- 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 #2385: Add request number of splits to display data in Dat...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2385 Add request number of splits to display data in DatastoreIO 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/vikkyrk/incubator-beam ds_data Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2385.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 #2385 commit c14bf8dbf083de0926adfe76db632756f88afdf1 Author: Vikas Kedigehalli Date: 2017-03-31T00:31:18Z Add request number of splits to display data in DatastoreIO --- 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 #2376: Annotate output type for python CoGroupByKey
Github user vikkyrk closed the pull request at: https://github.com/apache/beam/pull/2376 --- 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 #2376: Annotate output type for python CoGroupByKey
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2376 Annotate output type for python CoGroupByKey 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/vikkyrk/incubator-beam cogbk_output Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2376.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 #2376 commit 4416d225e6d3e987fb6a5cab4b477f9890afd59d Author: Vikas Kedigehalli Date: 2017-03-30T20:54:53Z Annotate output type for python CoGroupByKey --- 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 #2297: [BEAM-1590]: Roll forward #2140
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2297 [BEAM-1590]: Roll forward #2140 â¦I based jobs"" This reverts commit b31be1caef6a691006082e3e440d0b42ff1d4165. 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/vikkyrk/incubator-beam moe Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2297.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 #2297 commit efdf49ed4e3974e586104782c3fc29fed9edf7fc Author: Vikas Kedigehalli Date: 2017-03-10T18:47:20Z Revert "Revert "DataflowRunner: experimental support for issuing FnAPI based jobs"" This reverts commit b31be1caef6a691006082e3e440d0b42ff1d4165. --- 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 #2260: Use underscore instead of hypen in Datastore kind n...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2260 Use underscore instead of hypen in Datastore kind name. 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/vikkyrk/incubator-beam ds_test_Fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2260.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 #2260 commit 9bf2ea92ce9277fff9c978b2adf0c3a529ef8cac Author: Vikas Kedigehalli Date: 2017-03-16T21:45:44Z Use underscore instead of hypen in Datastore kind name. --- 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 #1724: [BEAM-991] Flush Datastore writes at max byte batch...
Github user vikkyrk closed the pull request at: https://github.com/apache/beam/pull/1724 --- 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 #2128: Update output stream cython declaration
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2128 Update output stream cython declaration 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/vikkyrk/incubator-beam itcdr_fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2128.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 #2128 --- 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 #2081: [BEAM-1539]: Support unkown length iterables for It...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2081 [BEAM-1539]: Support unkown length iterables for IterableCoder in python SDK 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/vikkyrk/incubator-beam it_cdr Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2081.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 #2081 commit dcc4b6bd7970741b03766fb162f367d0c6343551 Author: Vikas Kedigehalli Date: 2017-02-23T03:36:33Z Support unkown length iterables for IterableCoder in python SDK --- 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 #2068: Respect type hints for IterableCoder
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2068 Respect type hints for IterableCoder 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/vikkyrk/incubator-beam iterable_cdr_type_hint Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2068.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 #2068 commit 54587f50b34c3e97a265fc3108c068375112f4d5 Author: Vikas Kedigehalli Date: 2017-02-22T05:50:48Z Respect type hints for IterableCoder --- 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 #2028: [BEAM-1504] Parameterized tests for standard coders...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2028 [BEAM-1504] Parameterized tests for standard coders in Python SDK Be sure to do all of the following to help us incorporate your contribution quickly and easily: `python setup.py test -s apache_beam.coders.standard_coders_test ... test_standard_coder_0_bytes (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok test_standard_coder_1_bytes (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok test_standard_coder_2_varint (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok test_standard_coder_3_kv (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok test_standard_coder_4_kv (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok test_standard_coder_5_kv (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok test_standard_coder_6_intervalwindow (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok test_standard_coder_7_stream (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok test_standard_coder_8_stream (apache_beam.coders.standard_coders_test.StandardCodersTest) ... ok ` - [ ] 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/vikkyrk/incubator-beam parameterized_tests Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2028.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 #2028 commit bb7e91b45f1d47642720e035ff549bfafe0bfbfe Author: Vikas Kedigehalli Date: 2017-02-17T00:55:20Z Parameterized tests for standard coders in Python SDK --- 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 #2018: [BEAM-1467] dd cross-SDK implementations and tests ...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2018 [BEAM-1467] dd cross-SDK implementations and tests of WindowedValueCoder Be sure to do all of the following to help us incorporate your contribution quickly and easily: - Tests for GlobalWindowCoder - Cross-sdk implementation / tests for WindowedValueCoder - Note: PaneInfo isn't supported in python SDK yet, so we hard code the value to 0x0F which represents PaneInfo.NO_FIRING - [ ] 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/vikkyrk/incubator-beam common_windowed_value_coder Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2018.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 #2018 commit e0c5025ecc6529e2db04aff9e892ef045f7a7451 Author: Vikas Kedigehalli Date: 2017-02-16T02:13:12Z Add cross-SDK implementations and tests of WindowedValueCoder commit aa9840fe7c616c9ed85b475684fff61205449502 Author: Vikas Kedigehalli Date: 2017-02-16T02:40:29Z Fix lint errors --- 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 #2004: Add unsigned 64 bit int read/write methods to cytho...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/2004 Add unsigned 64 bit int read/write methods to cythonized stream 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/vikkyrk/incubator-beam py_coder_cy Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/2004.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 #2004 commit a08967b32ab7482c70017e2824a226869d6f4866 Author: Vikas Kedigehalli Date: 2017-02-14T06:11:25Z Add unsigned 64 bit int read/write methods to cythonized stream --- 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 #1996: Add cross-sdk tests for IterableCoder
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/1996 Add cross-sdk tests for IterableCoder 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/vikkyrk/incubator-beam common_iterable_coder Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/1996.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 #1996 commit 965160c0c0bada4500d51ca44c6c8e5e1c0476bf Author: Vikas Kedigehalli Date: 2017-02-13T18:23:28Z Add cross-sdk tests for IterableCoder --- 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 #1724: [BEAM-991] Flush Datastore writes at max byte batch...
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/1724 [BEAM-991] Flush Datastore writes at max byte batch limit 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/vikkyrk/incubator-beam ds_limit Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/1724.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 #1724 commit 6cb55b51df9d66a2cba1c1821a57457e5c01855d Author: Vikas Kedigehalli Date: 2016-12-27T19:58:42Z Flush Datastore writes at max byte batch limit. --- 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 #1704: Add ToString helper transform
GitHub user vikkyrk opened a pull request: https://github.com/apache/beam/pull/1704 Add ToString helper transform 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/vikkyrk/incubator-beam to_str Alternatively you can review and apply these changes as the patch at: https://github.com/apache/beam/pull/1704.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 #1704 commit 6fb3870b569fab051cc4ea989cfb9e7eb15f3da8 Author: Vikas Kedigehalli Date: 2016-12-28T00:37:03Z Add ToString helper transform --- 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 #1682: Add experiments alias for DebugOptions
Github user vikkyrk closed the pull request at: https://github.com/apache/incubator-beam/pull/1682 --- 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 #1699: [BEAM-1216] Assert transform without side...
GitHub user vikkyrk opened a pull request: https://github.com/apache/incubator-beam/pull/1699 [BEAM-1216] Assert transform without side inputs 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/vikkyrk/incubator-beam py_assert Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-beam/pull/1699.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 #1699 commit 1c795c10f0017766462cced1db1295c50bf2e32f Author: Vikas Kedigehalli Date: 2016-12-27T19:09:26Z Assert transform without side inputs --- 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 #1682: Add experiments alias for DebugOptions
GitHub user vikkyrk opened a pull request: https://github.com/apache/incubator-beam/pull/1682 Add experiments alias for DebugOptions 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). --- To keep parity with Java SDK. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vikkyrk/incubator-beam py_exp Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-beam/pull/1682.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 #1682 commit 3c1c1998bddad1026c219a31b0d345face532297 Author: Vikas Kedigehalli Date: 2016-12-22T00:53:30Z Add experiments alias for DebugOptions --- 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. ---
