Hello, one last note on this thread: we've processed and published the
Flink user survey results, and you can find a file with graphs summarizing
multiple-choice responses as well as anonymous feedback from open-ended
questions in a GitHub repository [1]. We also published a summary of
responses on
Hi everyone,
A quick heads-up that we'll be closing the Flink user survey to new
responses this coming Monday 12 Dec around 9am EST.
If you'd still like to respond before Monday, you can do so here:
http://www.surveygizmo.com/s3/3166399/181bdb611f22.
We've seen more than 100 responses so far. Th
There's a newline that disrupts the URL.
http://www.surveygizmo.com/s3/3166399/181bdb611f22
Not:
http://www.surveygizmo.com/s3/
3166399/181bdb611f22
---
>> *From:* Kostas Tzoumas
>> *To:* "d...@flink.apache.org" ;
>> user@flink.apache.org
>> *Sent:* Friday, November 18, 2016 7:28 AM
>> *Subject:* Flink survey by data Artisans
>>
>> Hi everyone!
>>
>> The Apache Flink community has evolved
ber 18, 2016 7:28 AM
> *Subject:* Flink survey by data Artisans
>
> Hi everyone!
>
> The Apache Flink community has evolved quickly over the past 2+ years, and
> there are now many production Flink deployments in organizations of all
> sizes. This is both exciting and humblin
From: Kostas Tzoumas
To: "d...@flink.apache.org" ; user@flink.apache.org
Sent: Friday, November 18, 2016 7:28 AM
Subject: Flink survey by data Artisans
Hi everyone!
The Apache Flink community has evolved quickly over the past 2+ years, and
there are now many produc
Hi everyone!
The Apache Flink community has evolved quickly over the past 2+ years, and
there are now many production Flink deployments in organizations of all
sizes. This is both exciting and humbling :-)
data Artisans is running a brief survey to understand Apache Flink usage
and the needs of
