date:20170131

[jira] (BEAM-1360) Reference to the obsolete python-sdk branch in the documentation.

2017-01-31 Thread Prabeesh K (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Prabeesh K created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Beam /  BEAM-1360 
 
 
 
  Reference to the obsolete python-sdk branch in the documentation.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Davor Bonaci 
 
 
 

Components:
 

 project-management 
 
 
 

Created:
 

 31/Jan/17 08:30 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Prabeesh K 
 
 
 
 
 
 
 
 
 
 
Following documents contains reference to obsolete python-sdk 
 

README
 

PYTHON SDK README
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[jira] (BEAM-1354) TextIO should comply with PTransform style guide

2017-01-31 Thread Aviem Zur (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aviem Zur updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Beam /  BEAM-1354 
 
 
 
  TextIO should comply with PTransform style guide  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aviem Zur 
 
 
 
 
 
 
 
 
 
 * TextIO.Read,Write.Bound,Unbound - Bound,Unbound are banned names. Instead, TextIO should make the user specify the type parameters explicitly, and have simply TextIO.Read and TextIO.Write themselves be the transform tyles.* Both should take simply String, and not use Coder as a general-purpose serialization mechanism.* * The Javadoc should be changed to reflect this.*  Should perhaps use AutoValue for parameter builders 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[jira] (BEAM-1361) Update build documentation with the new Python SDK

2017-01-31 Thread JIRA

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sergio Fernández created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Beam /  BEAM-1361 
 
 
 
  Update build documentation with the new Python SDK  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Affects Versions:
 

 0.5.0 
 
 
 

Assignee:
 
 Ahmet Altay 
 
 
 

Components:
 

 sdk-py 
 
 
 

Created:
 

 31/Jan/17 12:29 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Sergio Fernández 
 
 
 
 
 
 
 
 
 
 
Superseding the work on BEAM-378, now that the Python SDK has been merged into master, there are some details of the build process that has to be properly updated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[GitHub] beam pull request #1879: BEAM-1361: update Python build instructinons

2017-01-31 Thread wikier

GitHub user wikier opened a pull request:

https://github.com/apache/beam/pull/1879

BEAM-1361: update Python build instructinons

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [X] Make sure the PR title is formatted like:
   `[BEAM-] Description of pull request`
 - [X] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [X] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [X] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).

---

As described at 
[BEAM-1361](https://issues.apache.org/jira/browse/BEAM-1361).


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/wikier/beam BEAM-1361_python_build

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/beam/pull/1879.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 #1879


commit bddc1c3ea671dc2b7b367a89590769f2652f3efc
Author: Sergio FernÃ¡ndez 
Date:   2017-01-31T12:31:42Z

BEAM-1361: updated sdk status at readme

commit 2e5a67a3d1ad5cb1427cc45e7b13c2a306c7
Author: Sergio FernÃ¡ndez 
Date:   2017-01-31T12:35:48Z

BEAM-1361: updated basic system requiremets




---
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.
---

[jira] (BEAM-1361) Update build documentation with the new Python SDK

2017-01-31 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  BEAM-1361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update build documentation with the new Python SDK  
 
 
 
 
 
 
 
 
 
 
GitHub user wikier opened a pull request: 
 https://github.com/apache/beam/pull/1879 
 BEAM-1361: update Python build instructinons 
 Be sure to do all of the following to help us incorporate your contribution quickly and easily: 
 

[X] Make sure the PR title is formatted like: `BEAM- Description of pull request`
 

[X] Make sure tests pass via `mvn clean verify`. (Even better, enable Travis-CI on your fork and ensure the whole test matrix passes).
 

[X] Replace `` in the title with the actual Jira issue number, if there is one.
 

[X] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt).
 
 
 — 
 As described at BEAM-1361(https://issues.apache.org/jira/browse/BEAM-1361). 
You can merge this pull request into a Git repository by running: 
 $ git pull https://github.com/wikier/beam BEAM-1361_python_build 
Alternatively you can review and apply these changes as the patch at: 
 https://github.com/apache/beam/pull/1879.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 #1879 
 
commit bddc1c3ea671dc2b7b367a89590769f2652f3efc Author: Sergio Fernández  Date: 2017-01-31T12:31:42Z 
 BEAM-1361: updated sdk status at readme 
commit 2e5a67a3d1ad5cb1427cc45e7b13c2a306c7 Author: Sergio Fernández  Date: 2017-01-31T12:35:48Z 
 BEAM-1361: updated basic system requiremets 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[GitHub] beam pull request #1880: [BEAM-1360] Remove reference to the obsolete python...

2017-01-31 Thread prabeesh

GitHub user prabeesh opened a pull request:

https://github.com/apache/beam/pull/1880

[BEAM-1360] Remove reference to the obsolete python-sdk branch

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/prabeesh/beam master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/beam/pull/1880.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 #1880


commit 1846a226c5cadc9b1cf27a60dac2bf0598ccee55
Author: Prabeesh 
Date:   2017-01-31T12:55:03Z

remove reference to the obsolete python-sdk branch




---
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.
---

[jira] (BEAM-1360) Reference to the obsolete python-sdk branch in the documentation.

2017-01-31 Thread ASF GitHub Bot (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ASF GitHub Bot commented on  BEAM-1360 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reference to the obsolete python-sdk branch in the documentation.  
 
 
 
 
 
 
 
 
 
 
GitHub user prabeesh opened a pull request: 
 https://github.com/apache/beam/pull/1880 
 BEAM-1360 Remove reference to the obsolete python-sdk branch 
 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/prabeesh/beam master 
Alternatively you can review and apply these changes as the patch at: 
 https://github.com/apache/beam/pull/1880.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 #1880 
 
commit 1846a226c5cadc9b1cf27a60dac2bf0598ccee55 Author: Prabeesh  Date: 2017-01-31T12:55:03Z 
 remove reference to the obsolete python-sdk branch 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[jira] (BEAM-1278) Use checkstyle on everything

2017-01-31 Thread Benson Margulies (JIRA)

Title: Message Title

Benson Margulies commented on BEAM-1278

Re: Use checkstyle on everything

There is a dilemma here which surfaced in a discussion I had with Davor Bonaci yesterday.
The PR enables checkstyle everywhere by using a file system path for the rules instead of the classpath. It uses a Maven plugin to acquire the 'project root directory' from the subdirectories. (I don't really know how that plugin manages to do the right thing if you cd into some subdir and run it; does it just chase relativePath until it hits a parent which is somewhere else?)
In any case, the effect of this is to make it impossible to build a submodule in isolation by unpacking its source jar. We're not happy to break that.
There is an alternative: use the classpath when we can, and use the file path when we cannot. The top-level pom, and the 'sdks' pom, and the 'sdks/java' pom, would use the file path. The poms that currently use the classpath to enable checkstyle would override the configuration to use the classpath. That forces some duplication of the configuration; given the current directory structure, I don't know a way to avoid repeating this in several jars.
Well, actually, I do, but it would be rather structurally violent: the top-level pom would need to have two children: buildtools and 'everything else'.
Before I either go rework the patch to have this checkstyle repetition, or we close this down as a cure worse than a disease, I want to just point back to JB's remark: a common practice is to separately release a maven project containing these materials. We don't need to have a separate git repo; we can just have a directory which has an independent pom with the necessary maven-release-plugin configuration. The claim here is that the checkstyle rules do not change very often, so having to release the buildtools component whenever you change them is not so awful.