Hi,
It is thrilling to see the foreseeable upcoming rollouts of Flink 2.x releases,
and I believe that this roadmap can take Flink to the next stage of a
top-of-notch unified streaming & batch computing engine.
Given that all of the existing user programs are written and run in Flink 1.x
versi
Hi,
Thank you for bringing this up, and I am +1 for this feature.
IMO, one important thing that I would like to mention is that an
improperly-designed FLIP-27 connector could impose very severe memory pressure
on the JobManager, especially when there are enormous number of splits for the
sourc
Hi Qin,
Thanks for bringing up this issue. AFAIK, there is no such mechanism in
Flink for dynamic task re-assignment at runtime, as states need to be
correctly re-distributed across the nodes, which is highly error-prone and
not well-suited for the current computation model.
However, if the data-
+1 for the LTS proposal, so that existing users do not have to frequently
keep up with the latest Flink version in order to get necessary bug fixes
and security improvements. AFAIK, It is really a burden for them to
upgrade big projects from time to time.
Best,
Weike
tison 于2021年11月11日 周四下午9:46写
Hi Jark,
+1 for this proposal. Glad to see more details : )
Sincerely,
Weike
On Mon, Jan 25, 2021 at 2:03 PM Jark Wu wrote:
> Hi all,
>
> I would like to propose introducing a new method "retractAccumulators()" to
> the `AggregateFunction` in Table/SQL.
>
> *Motivation*
>
> The motivation is t
.
[image: image.png]
[image: image.png]
So these logic flaws eventually lead to this serious bug, and we recommend
that initialization of FlinkKafkaPartitioners could be done in
KafkaSerializationSchemaWrapper#open.
Sincerely,
Weike
On Thu, Sep 3, 2020 at 8:15 PM DONG, Weike wrote:
>
Hi community,
We have found a serious issue with the newly-introduced
*KafkaSerializationSchemaWrapper
*class, which eventually let *FlinkKafkaProducer *only write to partition 0
in the given Kafka topic under certain conditions.
First let's look at this constructor in the universal version of
*F
Thanks Jinsong for the suggestions.
+1 for #1, as users are constantly puzzled by the inconsistencies between
the Table / SQL module and SQL Client.
Best,
Weike
On Mon, Jul 6, 2020 at 11:55 AM Jingsong Li wrote:
> +1 for expanding the scope of #2, a SQL test framework(Should not be too
> heav
Hi community,
Recently we found out an issue with the Top-N feature in blink planner, and
here is the JIRA ticket https://issues.apache.org/jira/browse/FLINK-18452.
After analysis, we believe that it is the flaw in the implementation of
equals method, as it does not take the random numbers within
Hi dev,
Recently we have found that when* `rest.bind-port`* parameter is specified
as a port range (i.e. "5000-8000"), Flink may bind to some port (like 6000)
that is not allowed by Chrome (showing a "ERR_UNSAFE_PORT" message and
preventing users to continue accessing the website), similarly Firef
Hi Stephan,
+1 for the removal, as there are so many deprecated methods scattered
around, making APIs a little bit messy and confusing.
Best,
Weike
Stephan Ewen 于2020年4月23日 周四下午8:07写道：
> Hi all!
>
> There are a bunch of deprecated methods for state access:
>
> - RuntimeContext.getFoldingState
Hi Yu,
Thanks for your updates. I am still working on the fix for FLINK-16626 and
it is expected to be completed by this Sunday after thorough testing.
Sincerely,
Weike
On Fri, Apr 3, 2020 at 8:43 PM Yu Li wrote:
> Updates for 1.10.1 watched issues (we are in good progress and almost there
> t
gt;> remember whether a request is currently ongoing or not.
>>
>> Cheers,
>> Till
>>
>> On Tue, Mar 17, 2020 at 9:01 AM DONG, Weike
>> wrote:
>>
>>> Hi Tison & Till and all,
>>>
>>> I have uploaded the client, taskmanager an
gt;> RestServer which then is not able to serve the response to the client. I'm
>>> pulling in Aljoscha and Tison who introduced this change. They might be
>>> able to verify my theory and propose a solution for it.
>>>
>>> [1] https://issues.apa
consumer thread without any logging
or warnings, so Flink can do nothing but finish the job.
[image: image.png]
In conclusion, it is my fault not to catch the exception in KafkaFetcher,
and Flink is not the one to blame : )
Thanks
Sincerely,
Weike
On Tue, Mar 17, 2020 at 11:44 AM DONG, Weike
wrote
Hi community,
I have noticed that when a wrong CSV record is ingested and deserialized at
CsvRowDeserializationSchema, when ignoreParseErrors is set to false, then
an IOException is thrown, which is expected, and in earlier Flink versions,
the Flink YARN app would terminated with FINISHED state an
hy the task executor
> is killed? If it is killed by Yarn, you might get such info in Yarn
> NM/RM logs.
>
> Best,
> Yangze Guo
>
> Best,
> Yangze Guo
>
>
> On Fri, Mar 13, 2020 at 12:31 PM DONG, Weike
> wrote:
> >
> > Hi,
> >
> > Recently
Hi,
Recently I have encountered a strange behavior of Flink on YARN, which is
that when I try to cancel a Flink job running in per-job mode on YARN using
commands like
"cancel -m yarn-cluster
-yid application_1559388106022_9412 ed7e2e0ab0a7316c1b65df6047bc6aae"
the client happily found and conne
PIs
> etc.) around it.
>
> For pure SQL users, there are discussions of making the SQL Client
> richer in the future see:
>
>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-91%3A+Support+SQL+Client+Gateway
>
> Regards,
> Timo
>
>
> On 09.03.20 08:15
Hi Danny,
This is a nice feature, +1.
One thing I am interested in but not mentioned in the proposal is the error
handling, as it is quite common for users to write inappropriate hints in
SQL code, if illegal or "bad" hints are given, would the system simply
ignore them or throw exceptions?
Than
ment, I agree that it helps on
> consistent user
> experience using *just* SQL to describe their Flink job. Looking forward to
> maintainers'
> idea on the possibility & plan.
>
> Best,
> tison.
>
> [1]
> https://cwiki.apache.org/confluence/pages/viewpa
Hi dev,
Recently we have tested the brand-new SQLClient and Flink SQL module, and
we are amazed at this simple way of programming for streaming data
analysis. However, as far as I know, the SET command is only available in
the SQL Client, but not in SQL API.
Although we understand that developers
+1 for RAW type, which is easy to guess its actual meaning, even for a new
user.
Best,
Weike
On Tue, Oct 22, 2019 at 5:31 PM David Anderson wrote:
> +1 for RAW.
>
> I agree that this is clearer than OPAQUE (which I initially proposed).
>
> On Mon, Oct 21, 2019 at 10:33 AM Jark Wu wrote:
> >
>
Hi Quan,
Currently namespace is only useful in WindowOperator (see
WindowOperator.java), and for other places, VoidNamespace is used as the
placeholder.
: )
On Mon, May 6, 2019 at 9:36 PM Shi Quan wrote:
> Hi,
>
> Few documentation mention “namespace” when talking about state. What’s the
> mea
Hi,
I want to contribute to Apache Flink.
Would you please give me the contributor permission?
My JIRA ID is kyledong
Thanks : )
25 matches
Mail list logo
