I sent a PR about this all:
https://github.com/apache/beam/pull/3799
On Mon, Aug 28, 2017 at 8:45 AM Eugene Kirpichov
wrote:
> Thanks. I think I agree that file-based IOs (at least widely used ones)
> should, for convenience, still provide FooIO.read().from(filepattern),
Only apache/beam-site has migrated to using gitbox, I'm not sure why
apache/beam has not yet.
On Thu, Aug 31, 2017 at 5:49 PM, Thomas Weise wrote:
> Is the project using gitbox? If so, there should be a close button if you
> have linked your ASF id with your github ID and then
Is the project using gitbox? If so, there should be a close button if you
have linked your ASF id with your github ID and then complete the gitbox
account linking here:
https://gitbox.apache.org/setup/
Thanks,
Thomas
On Thu, Aug 31, 2017 at 5:01 PM, Ahmet Altay
Add https://issues.apache.org/jira/browse/BEAM-2833 which is a blocker to
merge DSL_SQL. There may be something wrong in the back-end(maybe
RunnerApi) to handle parametered CustomCoder in TestPipeline.
On Thu, Aug 31, 2017 at 10:38 AM, Jean-Baptiste Onofré
wrote:
> Fair
Fair enough.
That's fine for me.
Regards
JB
On Aug 31, 2017, 19:03, at 19:03, Steve Niemitz wrote:
>I'll chime in as a user who would love to see 2.2.0 sooner than later,
>specifically for the file IO Eugene mentioned. We're using the AvroIO
>enhancements extensively, but
I'll chime in as a user who would love to see 2.2.0 sooner than later,
specifically for the file IO Eugene mentioned. We're using the AvroIO
enhancements extensively, but I am hesitant to run from HEAD in master in
production.
On Thu, Aug 31, 2017 at 12:42 PM, Eugene Kirpichov <
Welcome Joey!
On 31 August 2017 at 07:43, Aviem Zur wrote:
> Welcome JB #2!
>
> Glad to have you on board.
>
> On Tue, Aug 29, 2017 at 5:38 PM Joey Baruch wrote:
>
> > my jira username is joeyfezster
> >
> > thanks
> >
> > On Tue, Aug 29, 2017 at 4:12
There are a lot of users including very large production customers who have
been asking specifically for the features that are in 2.2.0 (most of them
accumulated while 2.1.0 was being iterated on) - mostly I'm referring to
the vastly improved file IO - and they have been hesitant to use Beam at
Welcome JB #2!
Glad to have you on board.
On Tue, Aug 29, 2017 at 5:38 PM Joey Baruch wrote:
> my jira username is joeyfezster
>
> thanks
>
> On Tue, Aug 29, 2017 at 4:12 PM Jean-Baptiste Onofré
> wrote:
>
> > Welcome !
> >
> > What's your apache id ?
Agree, it sounds like a good idea to me.
Regards
JB
On 08/31/2017 10:35 AM, Etienne Chauchot wrote:
Hi,
I think Nexmark (https://github.com/apache/beam/tree/master/sdks/java/nexmark)
could help in getting quantitative benchmark metrics for all the runners like
Tyler suggested.
Another
As we released 2.1.0 couple of weeks ago, it could sound weird to the users to
do a 2.2.0 so fast. If we have a blocking issue, we can do a 2.1.1 If it's new
features, why not having a release pace in October (2.2.0) ?
Thoughts ?
Regards
JB
On 08/31/2017 08:27 AM, Eugene Kirpichov wrote:
I'd suggest to do 2.2.0 as quickly as possible, and target 2.3.0 for
October. I don't see a reason to delay 2.2.0 until October: there's a huge
amount of features worth releasing between when 2.1.0 was cut and the
current HEAD.
On Wed, Aug 30, 2017 at 10:18 PM Jean-Baptiste Onofré
12 matches
Mail list logo