Re: Snowflake account donation for ongoing testing

Thanks, Pablo! +Harsha Kapre , who appears to have been accidentally dropped from the original thread. -Tyler On Mon, May 18, 2020, 15:21 Pablo Estrada wrote: > Hello Harsha! > Thanks for contributing the connector, and the support for testing it. > This is great. > I am a PMC member, and

Re: Snowflake connector

On Tue, Mar 10, 2020 at 1:27 AM Elias Djurfeldt wrote: > From what I can tell, the only difference is that the Python connector is > a pure Python implementation and doesn't rely on ODBC or JDBC (it's just a > pip installable). Whereas the Java version needs JDBC. But that seems to be > the only

Re: [VOTE] Release Vendored gRPC 1.13.1 v0.2, release candidate #1

+1, Approve the release. -Tyler On Thu, Dec 20, 2018 at 9:49 AM Ahmet Altay wrote: > I meant BEAM-6249 in my last sentence. It should read: "BEAM-6249 has a > comment about user building the libraries themselves, I am not sure if they > are using the release 2.9 version directly or not." > >

Re: [ANNOUNCEMENT] New Beam chair: Kenneth Knowles

Thanks Davor, and congrats Kenn! -Tyler On Wed, Sep 19, 2018 at 2:43 PM Yifan Zou wrote: > Congratulations Kenn! > > On Wed, Sep 19, 2018 at 2:36 PM Robert Burke wrote: > >> Congrats Kenn! :D >> >> On Wed, Sep 19, 2018, 2:21 PM Ismaël Mejía wrote: >> >>> Congratulations and welcome Kenn as

Re: [DISCUSS] Communicating in dev@

+1 to all points made so far. I think docs are great for collaborating on bigger proposals, but mailing list summaries are very helpful since it's often unpractical to click through on each and every one (plus I can search archives more effectively that way). And email for shorter proposals is

Re: Wait.on() - "Do this, then that" transform

Nice! I like the clean integration with streaming. -Tyler On Mon, May 14, 2018 at 2:48 PM Eugene Kirpichov wrote: > Hi folks, > > Wanted to give a heads up about the existence of a commonly requested > feature and its first successful production usage. > > The feature is

Re: [ANNOUCEMENT] New Foundation members!

Congratulations! On Tue, Apr 3, 2018 at 10:31 AM Daniel Oliveira wrote: > Congrats! > > On Tue, Apr 3, 2018 at 2:05 AM Etienne Chauchot > wrote: > >> Congrats >> Le mardi 03 avril 2018 à 10:41 +0200, Kostas Kloudas a écrit : >> >> Congratulations

Re: [PROPOSAL] Scripting extension based on Java JSR-223

+1, I like it. Thanks! On Fri, Mar 23, 2018 at 9:03 AM Ahmet Altay wrote: > Thank you Ismaël, this looks really cool. > > On Fri, Mar 23, 2018 at 5:33 AM, Jean-Baptiste Onofré > wrote: > >> Hi, >> >> it sounds like a very good extension mechanism to

Re: [SQL] Windowing and triggering changes proposal

I'm late to the party as usual, but also added some comments. Overall supportive of this work. Thanks for the clear analysis, Anton. On Tue, Jan 16, 2018 at 10:58 AM Mingmin Xu wrote: > Thanks @Anton for the proposal. Window(w/ trigger) support in SQL is > limited now,

Re: Happy new year

+1 all around. 2017 was excellent, and we're in a great position for 2018 to be even better. Looking forward to it. :-) On Tue, Jan 2, 2018 at 10:34 AM Kenneth Knowles wrote: > Happy new year! Very excited for 2018's possibilities. And nice work, JB. > > Kenn > > On Tue, Jan 2,

Re: Euphoria Java 8 DSL - proposal

+1, I'm supportive of seeing this move forward. What remaining concrete concerns are there? -Tyler On Tue, Jan 2, 2018 at 8:35 AM David Morávek wrote: > Hello JB, > > can we help in any way to move things forward? > > Thanks, > D. > > On Mon, Dec 18, 2017 at 4:28 PM,

Re: Schema-Aware PCollections

On Wed, Nov 29, 2017 at 6:38 PM Reuven Lax wrote: > There has been a lot of conversation about schemas on PCollections > recently. There are a number of reasons for this. Schemas as first-class > objects in Beam provide a nice base for building BeamSQL. Spark has > provided

Re: [VOTE] Choose the "new" Spark runner

[ ] Use Spark 1 & Spark 2 Support Branch [X] Use Spark 2 Only Branch On Sun, Nov 19, 2017 at 1:46 PM Amit Sela wrote: > [X] Use Spark 2 Only Branch > > On Sun, Nov 19, 2017, 02:46 Reuven Lax wrote: > > > [ ] Use Spark 1 & Spark 2 Support Branch >

Re: [Proposal] Apache Beam Swag Store

One additional note: for the logos w/ the name below them, would be nice to not have quite so much whitespace between the logo and the name. Otherwise, trademark validation aside, this looks great. On Fri, Oct 27, 2017 at 10:15 AM Griselda Cuevas wrote: > Hi Dan -

Re: [DISCUSS] Switch to gitbox

+1 On Fri, Oct 6, 2017 at 8:54 AM Reuven Lax wrote: > +1 > > On Oct 6, 2017 4:51 PM, "Lukasz Cwik" wrote: > > > I think its a great idea and find that the mergebot works well on the > > website. > > Since gitbox enforces that the precommit

Re: Support for window analytic functions in SQL DSL

I'm not aware of analytic window support. +Mingmin Xu or +James could speak to any plans they might have regarding adding support. -Tyler On Mon, Oct 2, 2017 at 3:23 AM Kobi Salant wrote: > Hi, > > Calcite streaming

Re: Merge branch DSL_SQL to master

in > > > > On Thu, Sep 7, 2017 at 10:09 AM, Ahmet Altay <al...@google.com.invalid> > > wrote: > > > >> +1 Thanks to all contributors/reviewers! > >> > >> On Thu, Sep 7, 2017 at 9:55 AM, Kai Jiang <jiang...@gmail.com> wrote: > >>

Re: [DISCUSSION] using NexMark for Beam

Awesome news, thank you! :-D On Thu, Aug 24, 2017 at 12:40 AM Etienne Chauchot wrote: > Hi all, > > I wanted to let you know that the Nexmark PR is merged into master. Feel > free to use it (e.g. performance testing, release testing ...). > > Etienne > > Le 12/05/2017 à

Re: [DISCUSS] Capability Matrix revamp

Is there any way we could add quantitative runner metrics to this as well? Like by having some benchmarks that process X amount of data, and then detailing in the matrix latency, throughput, and (where possible) cost, etc, numbers for each of the given runners? Semantic support is one thing, but

Re: Hello from a newbie to the data world living in the city by the bay!

Welcome all! :-) On Wed, Aug 16, 2017 at 4:17 PM María García Herrero wrote: > Welcome Gris, Umang, and Justin! > > On Wed, Aug 16, 2017 at 1:15 AM, Jean-Baptiste Onofré > wrote: > > > Welcome ! > > > > Regards > > JB > > > > On Aug 16, 2017,

Re: [ANNOUNCEMENT] New PMC members, August 2017 edition!

Congrats! On Sat, Aug 12, 2017 at 1:51 AM Pei HE wrote: > Congratulations! > -- > Pei > > On Sat, Aug 12, 2017 at 3:10 PM, Aljoscha Krettek > wrote: > > > Congratulations! :-) > > > > Best, > > Aljoscha > > > > > On 12. Aug 2017, at 06:39, Robert Bradshaw

Re: [ANNOUNCEMENT] New committers, August 2017 edition!

Congrats and thanks all around! On Sat, Aug 12, 2017 at 12:09 AM Aljoscha Krettek wrote: > Congrats, everyone! It's well deserved. > > Best, > Aljoscha > > > On 12. Aug 2017, at 08:06, Pei HE wrote: > > > > Congratulations to all! > > -- > > Pei > > > >

Re: [PROPOSAL] "Requires deterministic input"

+1 to the annotation idea, and to having it on processTimer. -Tyler On Thu, Aug 10, 2017 at 2:15 AM Aljoscha Krettek wrote: > +1 to the annotation approach. I outlined how implementing this would work > in the Flink runner in the Thread about the exactly-once Kafka Sink. >

Re: Towards a spec for robust streaming SQL, Part 2

+d...@apex.apache.org, since I'm told Apex has a Calcite integration as well. If anyone on the Apex side wants to join in on the fun, your input would be welcomed! -Tyler On Mon, Jul 24, 2017 at 4:34 PM Tyler Akidau <taki...@apache.org> wrote: > Hello Flink, Calcite, and Beam

Towards a spec for robust streaming SQL, Part 2

Hello Flink, Calcite, and Beam dev lists! Linked below is the second document I promised way back in April regarding a collaborative spec for streaming SQL in Beam/Calcite/Flink (& apologies for the delay; I thought I was nearly done a while back and then temporal joins expanded to something much

Re: BeamSQL status and merge to master

/issues.apache.org/jira/browse/BEAM-2555?jql=labels%2 > > 0%3D%20dsl_sql_merge > > > > > > > > > Mingmin > > > > > > On Tue, Jun 13, 2017 at 8:51 AM, Lukasz Cwik <lc...@google.com.invalid > > > > > wrote: > > > > >

Re: BeamSQL status and merge to master

Thanks Mingmin. I've copied your list into a doc[1] to make it easier to collaborate on comments and edits. [1] https://s.apache.org/beam-dsl-sql-burndown -Tyler On Mon, Jun 12, 2017 at 10:09 PM Jean-Baptiste Onofré wrote: > Hi Mingmin > > Sorry, the meeting was in the

Re: Apache Beam SQL: DDL

Thanks James, added some initial comments. -Tyler On Thu, Jun 8, 2017 at 3:11 AM James wrote: > Hi team, I am working on BeamSQL now, and would like to add DDL for > BeamSQL, so prepared a design doc[1], would like to hear your opinions :) > > [1] > >

Re: First stable release completed!

Well done everyone. Thanks to all who helped make this happen. :-) -Tyler On Thu, May 18, 2017 at 6:52 PM Etienne Chauchot wrote: > This is awesome! Congrats to everyone! > > Etienne > > > Le 17/05/2017 à 18:34, Thomas Groh a écrit : > > Well done all! > > > > On Wed, May

Re: Towards a spec for robust streaming SQL, Part 1

e such > flexibility (as compared with TableAPI) in SQL query, we need find a way to > embed this EMIT config. > > Regards, > Shaoxuan > > > On Fri, May 12, 2017 at 4:28 PM, Fabian Hueske <fhue...@gmail.com> wrote: > > > 2017-05-11 7:14 GMT+02:00 Tyler Akidau <

Re: Towards a spec for robust streaming SQL, Part 1

riggering on every element, basically as you described in the previous paragraph. -Tyler > > I'm looking forward to the second part. > > Cheers, Fabian > > > > 2017-05-09 0:34 GMT+02:00 Tyler Akidau <taki...@google.com.invalid>: > > > Any thoughts here Fabian? I

Re: Towards a spec for robust streaming SQL, Part 1

ave more time to read and comment. > > Thanks, > Fabian > > > 2017-04-22 0:16 GMT+02:00 Tyler Akidau <taki...@google.com.invalid>: > > > Good point, when you start talking about anything less than a full join, > > triggers get involved to describe how one act

Re: Towards a spec for robust streaming SQL, Part 1

t; (delightful doc, as usual) > > Kenn > > On Fri, Apr 21, 2017 at 1:33 PM, Tyler Akidau <taki...@google.com.invalid> > wrote: > > > Thanks for reading, Luke. The simple answer is that CoGBK is basically > > flatten + GBK. Flatten is a non-grouping operation

Re: Towards a spec for robust streaming SQL, Part 1

iple streams writing to a table, how > does that impact window merging? > > On Thu, Apr 20, 2017 at 5:57 PM, Tyler Akidau <taki...@google.com.invalid> > wrote: > > > Hello Beam, Calcite, and Flink dev lists! > > > > Apologies for the big cross post, but I thou

Towards a spec for robust streaming SQL, Part 1

Hello Beam, Calcite, and Flink dev lists! Apologies for the big cross post, but I thought this might be something all three communities would find relevant. Beam is finally making progress on a SQL DSL utilizing Calcite, thanks to Mingmin Xu. As you can imagine, we need to come to some

Re: [PROPOSAL]: a new feature branch for SQL DSL

t; i just want to know what the SQL State API equivalent is for SQL, since > beam has already support stateful processing using state DoFn > > 2017-04-11 2:12 GMT+08:00 Tyler Akidau <taki...@google.com.invalid>: > > > 陈竞, what are you specifically curious about regarding state?

Re: [PROPOSAL]: a new feature branch for SQL DSL

I'm very excited by this development as well, thanks for continuing to push this forward, Mingmin. :-) I noticed you'd made some changes to your design doc . Is it ready for another review? How reflective is it

Re: [PROPOSAL] @OnWindowExpiration

+1. I'm assuming this is much easier for the user in the case of merging windows (i.e., or do we disallow user-specified timers for merging windows currently, similar to value state)? -Tyler On Wed, Mar 29, 2017 at 2:38 PM Aljoscha Krettek wrote: > +1 I had also already

Re: [ANNOUNCEMENT] New committers, March 2017 edition!

Welcome! On Mon, Mar 20, 2017, 02:25 Jean-Baptiste Onofré wrote: > Welcome aboard, and congrats ! > > Really happy to count you all in the team ;) > > Regards > JB > > On 03/17/2017 10:13 PM, Davor Bonaci wrote: > > Please join me and the rest of Beam PMC in welcoming the

Re: [BEAM-301] Add a Beam SQL DSL

Hi Mingmin, Thanks for your interest in helping out on this task, and for your initial proposal. I'm also very happy to work with you on this, and excited to see some progress made here. Added a few more comments on the doc, but will summarize them below as well. As far as the DSL point goes, I

Re: [jira] [Created] (BEAM-1261) State API should allow state to be managed in different windows

On Wed, Jan 11, 2017 at 9:43 AM Robert Bradshaw wrote: > On Wed, Jan 11, 2017 at 8:59 AM, Lukasz Cwik > wrote: > > I was under the impression that user state was scoped to a ParDo and was > > not shareable across multiple ParDos. Wouldn't