Re: TikaIO concerns

Hi Eugene, fully agree ! My point was more in term of features: I think it's fair to postpone some features in an IO in new PRs. For example, when we created JmsIO, it only supports TextMessage and new message types support will be added in new improvement PRs. It's what I meant by "basically

Re: Proposal: Unbreak Beam Python 2.1.0 with 2.1.1 bugfix release

+1 Regards JB On 09/19/2017 11:05 PM, Charles Chen wrote: The latest version (2.1.0) of Beam Python ( https://pypi.python.org/pypi/apache-beam) is broken due to a change in the "six" dependency (BEAM-2964 ). For instance, installing "apache-beam

Re: Update on 2.2.0 release

Hi Reuven, thanks for the update. I will pick up some Jira in my bucket (to verify/double check or implement). Regards JB On 09/20/2017 04:23 AM, Reuven Lax wrote: There are 7 issues left on https://issues.apache.org/jira/projects/BEAM/versions/12341044 after I moved some items to 2.3.0 if t

Re: Proposal: Unbreak Beam Python 2.1.0 with 2.1.1 bugfix release

Or unpin apitools. The bug there is being followed at https://github.com/benjaminp/six/issues/210 On Tue, Sep 19, 2017 at 6:08 PM, Charles Chen wrote: > There is an incompatibility between the apitools > library and the newest > version of the six li

Update on 2.2.0 release

There are 7 issues left on https://issues.apache.org/jira/projects/BEAM/versions/12341044 after I moved some items to 2.3.0 if they appeared to not need to be in 2.2.0 (some were originally slated for 2.1.0, and there was no apparent progress on them). Please object if you feel that it's important

Re: Proposal: Unbreak Beam Python 2.1.0 with 2.1.1 bugfix release

There is an incompatibility between the apitools library and the newest version of the six library , on which we have a dependency. The underlying bug in apitools is fixed here

Re: Proposal: Unbreak Beam Python 2.1.0 with 2.1.1 bugfix release

Any elaboration or jira issues describing what is broken? Any proposal for what changes need to happen to fix it? On Tue, Sep 19, 2017, 5:49 PM Chamikara Jayalath wrote: > +1 for cutting 2.1.1 for Python SDK only. > > Thanks, > Cham > > On Tue, Sep 19, 2017 at 5:43 PM Robert Bradshaw > > wrote:

Re: Proposal: Unbreak Beam Python 2.1.0 with 2.1.1 bugfix release

+1 for cutting 2.1.1 for Python SDK only. Thanks, Cham On Tue, Sep 19, 2017 at 5:43 PM Robert Bradshaw wrote: > +1. Right now anyone who follows our quickstart instructions or > otherwise installs the latest release of apache_beam is broken. > > On Tue, Sep 19, 2017 at 2:05 PM, Charles Chen >

Re: Proposal: Unbreak Beam Python 2.1.0 with 2.1.1 bugfix release

+1. Right now anyone who follows our quickstart instructions or otherwise installs the latest release of apache_beam is broken. On Tue, Sep 19, 2017 at 2:05 PM, Charles Chen wrote: > The latest version (2.1.0) of Beam Python ( > https://pypi.python.org/pypi/apache-beam) is broken due to a change

Re: TikaIO concerns

On Tue, Sep 19, 2017 at 5:13 AM Jean-Baptiste Onofré wrote: > Hi Sergey, > > as discussed together during the review, I fully understand the choices > you did. > > Your plan sounds reasonable. Thanks ! > > Generally speaking, in order to give visibility and encourage > contribution, I > think it

Re: TikaIO concerns

Hi, Replies inline. On Tue, Sep 19, 2017 at 3:41 AM Sergey Beryozkin wrote: > Hi All > > This is my first post the the dev list, I work for Talend, I'm a Beam > novice, Apache Tika fan, and thought it would be really great to try and > link both projects together, which led me to opening [1] wh

Proposal: Unbreak Beam Python 2.1.0 with 2.1.1 bugfix release

The latest version (2.1.0) of Beam Python ( https://pypi.python.org/pypi/apache-beam) is broken due to a change in the "six" dependency (BEAM-2964 ). For instance, installing "apache-beam" in a clean environment and running "python -m apache_beam.ex

Re: [DISCUSSION] using NexMark for Beam

I think adding a new query for window merging makes sense and would be easier to follow and maintain. Regards JB On Sep 19, 2017, 18:09, at 18:09, Reuven Lax wrote: >On Tue, Sep 19, 2017 at 7:29 AM, Etienne Chauchot >wrote: > >> Hi all, >> >> I'm resuming my work on Nexmark a bit, starting to

Re: [DISCUSSION] using NexMark for Beam

On Tue, Sep 19, 2017 at 7:29 AM, Etienne Chauchot wrote: > Hi all, > > I'm resuming my work on Nexmark a bit, starting to do some maintenance on > the tickets > > @Reuven: I have some comments inline below. > > Le 14/05/2017 à 14:29, Reuven Lax a écrit : > >> Great to hear! A couple of comments:

Problem with throttle update in dataflow pipeline

Hi, I got the following message on dataflow : (3ab7c60e46263340): Workflow failed. Causes: (8218eb08eddcd37d): S105:get_num_lines_integrated_billing_92bab7e1/CombineGlobally(CountCombineFn)/DoOnce/Read+get_num_lines_integrated_billing_92bab7e1/CombineGlobally(CountCombineFn)/InjectDefault/Do+get_

Re: Problem while upgrading lib

Hi, No help on this? Regards, *Sébastien MORAND* Team Lead Solution Architect Technology & Operations / Digital Factory Veolia - Group Information Systems & Technology (IS&T) Cell.: +33 7 52 66 20 81 / Direct: +33 1 85 57 71 08 Bureau 0144C (Ouest) 30, rue Madeleine-Vionnet - 93300 Aubervilliers

Re: [DISCUSSION] using NexMark for Beam

Hi all, I'm resuming my work on Nexmark a bit, starting to do some maintenance on the tickets @Reuven: I have some comments inline below. Le 14/05/2017 à 14:29, Reuven Lax a écrit : Great to hear! A couple of comments: When Query 10 was written, the file-based sinks did not supported unboun

Re: TikaIO concerns

Hi Sergey, as discussed together during the review, I fully understand the choices you did. Your plan sounds reasonable. Thanks ! Generally speaking, in order to give visibility and encourage contribution, I think it would make sense to accept a PR if it's basically right (even if it's not ye

TikaIO concerns

Hi All This is my first post the the dev list, I work for Talend, I'm a Beam novice, Apache Tika fan, and thought it would be really great to try and link both projects together, which led me to opening [1] where I typed some early thoughts, followed by PR [2]. I noticed yesterday I had the

Build failed in Jenkins: beam_Release_NightlySnapshot #537

See Changes: [echauchot] [BEAM-2957] Fix flaky ElasticsearchIOTest.testSplit in [kirpichov] Speeds up CompressedSourceTest -- [...truncated 3.91 MB...] File