I am not an owner or maintainer of the PyPi package, so I'm not sure if
I'll be able to release Python artifacts.
On Fri, Nov 24, 2017 at 10:08 PM, Jean-Baptiste Onofré
wrote:
> Awesome, Thanks Reuven !
>
> Regards
> JB
>
> On 11/25/2017 07:01 AM, Reuven Lax wrote:
>
>> I'll
Awesome, Thanks Reuven !
Regards
JB
On 11/25/2017 07:01 AM, Reuven Lax wrote:
I'll go ahead and send the RESULT email right now.
On Fri, Nov 24, 2017 at 9:56 PM, Jean-Baptiste Onofré
wrote:
It's not sync: promoting the artifacts takes some time (at least 30
minutes).
I'm happy to announce that we have unanimously approved this release.
There are 9 approving votes, 5 of which are binding:
* Lukasz Cwik (binding)
* Romain Manni-Bucau (non binding)
* Jean-Baptiste Onofré (binding)
* Ahmet Altay (binding)
* Robert Bradshaw (binding)
* Konstantinos Katsiapis (non
I'll go ahead and send the RESULT email right now.
On Fri, Nov 24, 2017 at 9:56 PM, Jean-Baptiste Onofré
wrote:
> It's not sync: promoting the artifacts takes some time (at least 30
> minutes). So, the artifacts will be on central after a certain time.
>
> I confirm that
Hi all,
Has anyone seen this issue when building latest master on Mac ?
*[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (enforce)
on project beam-sdks-java-io-tika: Execution enforce of goal
Hi JB,
Thanks for the updates.
BTW I am myself in Microsoft but I am trying this out of my interest.
And it's good to know that someone else is also working on this.
-Milan.
-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
Sent: Thursday, November 23, 2017 1:47
reuvenlax commented on a change in pull request #4145: Many simplifications to
WriteFiles
URL: https://github.com/apache/beam/pull/4145#discussion_r152652760
##
File path: sdks/java/core/src/main/java/org/apache/beam/sdk/io/WriteFiles.java
##
@@ -824,177 +826,78 @@ public
reuvenlax commented on a change in pull request #4145: Many simplifications to
WriteFiles
URL: https://github.com/apache/beam/pull/4145#discussion_r153034261
##
File path: sdks/java/core/src/main/java/org/apache/beam/sdk/io/WriteFiles.java
##
@@ -339,50 +297,189 @@ public
Appears to be a problem :)
I tried publishing the latest artifact from Apache Nexus to Maven Central.
After clicking publish, Nexus claimed that the operation has completed.
However a look at the Maven Central page (
https://mvnrepository.com/artifact/org.apache.beam/beam-sdks-java-core)
does not
iemejia commented on a change in pull request #4174: [BEAM-3244] Ensure
execution of teardown method on Flink's DoFnOperator
URL: https://github.com/apache/beam/pull/4174#discussion_r153012280
##
File path:
iemejia opened a new pull request #4174: [BEAM-3244] Ensure execution of
teardown method on Flink's DoFnOperator
URL: https://github.com/apache/beam/pull/4174
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [x] Make sure there is a [JIRA
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346872620
Run Gearpump ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346872611
Run Dataflow ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346871884
Run Flink ValidatesRunner
Run Spark ValidatesRunner
Run Dataflow ValidatesRunner
Run Apex ValidatesRunner
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346872593
Run Apex ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346872574
Run Spark ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346703990
Run Spark ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346704033
Run Apex ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346704040
Run Gearpump ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346703983
Run Flink ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346872487
Run Flink ValidatesRunner
This is an automated
iemejia commented on issue #4170: Make ParDoLifecycleTest exception tests part
of the ValidatesRunner set
URL: https://github.com/apache/beam/pull/4170#issuecomment-346871884
Run Flink ValidatesRunner
Run Spark ValidatesRunner
Run Dataflow ValidatesRunner
Run Apex ValidatesRunner
xumingming commented on issue #4173: [DISCUSS] add a java profile to be able to
skip python/go when not relevant for current work
URL: https://github.com/apache/beam/pull/4173#issuecomment-346862839
I like this idea.
This is
lgajowy commented on a change in pull request #4149: [BEAM-3060] Add Compressed
TextIOIT
URL: https://github.com/apache/beam/pull/4149#discussion_r152999363
##
File path:
sdks/java/io/file-based-io-tests/src/test/java/org/apache/beam/sdk/io/text/TextIOIT.java
##
@@
lgajowy commented on a change in pull request #4149: [BEAM-3060] Add Compressed
TextIOIT
URL: https://github.com/apache/beam/pull/4149#discussion_r152998058
##
File path:
sdks/java/io/file-based-io-tests/src/test/java/org/apache/beam/sdk/io/text/TextIOIT.java
##
@@
+1 for new mailing list (reviews@)
On Fri, Nov 24, 2017 at 5:20 AM, James wrote:
> +1 for new mailling list (reviews@)
>
> On Thu, Nov 23, 2017 at 7:38 PM Ismaël Mejía wrote:
>
> > If github already does the notifications, I think that having an extra
+1
> On 23. Nov 2017, at 23:22, Manu Zhang wrote:
>
> +1
>
> On Thu, Nov 23, 2017 at 11:32 PM Maximilian Michels wrote:
>
>> +1
>>
>> Thanks for looking into it!
>>
>> On 23.11.17 00:25, Lukasz Cwik wrote:
>>> I have noticed that some e-mail
sduskis commented on a change in pull request #4171: [BEAM-3008] Extends API
for BigtableIO Read and Write by adding withInstanceId and withProjectId
URL: https://github.com/apache/beam/pull/4171#discussion_r152978149
##
File path:
xumingming commented on issue #4168: [BEAM-3238][SQL] Add
BeamRecordSqlTypeBuilder
URL: https://github.com/apache/beam/pull/4168#issuecomment-346831152
I like this idea!
One minor comment: Can we put the `BeamRecordSqlTypeBuilder` inside
`BeamRecordSqlType`? it will keep the
+1 for new mailling list (reviews@)
On Thu, Nov 23, 2017 at 7:38 PM Ismaël Mejía wrote:
> If github already does the notifications, I think that having an extra
> notifications/reviews mailing list could be overkill (or spammy).
> However I can see the value of this for
rmannibucau opened a new pull request #4173: [DISCUSS] add a java profile to be
able to skip python/go when not relevant for current work
URL: https://github.com/apache/beam/pull/4173
Often working on a feature or even more on a fix you only care about a
language - which is probably most
Hi Romain,
I guess they are not part of the repo (git clean -x -f -d removes it), correct ?
Let me try.
Thanks,
Regards
JB
On 11/24/2017 10:00 AM, Romain Manni-Bucau wrote:
Hi guys,
I don't really know if it comes from my gradle tests or the gradle
build itself but I realize this morning I
Hi guys,
I don't really know if it comes from my gradle tests or the gradle
build itself but I realize this morning I had ".gogradle" files in
beam in a few places and when building with maven the resource plugin
directory scanner goes through these files and seems it loops and
makes the build
33 matches
Mail list logo