+1 for the proposal
But "Since the signature of the public state API has been changed", I was
wondering whether this would be more fittable in Flink 2.0, instead of 1.19?
WDYT?
Best
Yuan
On Wed, Oct 11, 2023 at 4:34 PM David Radley
wrote:
> Hi Zakelly,
> Thanks for making this clear for me.
+1 (binding)
Thanks for the work, Joao!
Best,
Qingsheng
> On Oct 12, 2023, at 19:32, Leonard Xu wrote:
>
> Thanks Joao for driving this work.
>
> +1 (binding)
>
> Best,
> Leonard
>
>> On Oct 12, 2023, at 7:09 PM, Sergey Nuyanzin wrote:
>>
>> +1 (binding)
>
+1(non-binding)
Regards
Ahmed
On Fri, 13 Oct 2023, 10:49 Qingsheng Ren, wrote:
> +1 (binding)
>
> Thanks for the work, Joao!
>
> Best,
> Qingsheng
>
> > On Oct 12, 2023, at 19:32, Leonard Xu wrote:
> >
> > Thanks Joao for driving this work.
> >
> > +1 (binding)
> >
> > Best,
> > Leonard
> >
> >
Gabor Somogyi created FLINK-33268:
-
Summary: Flink REST API response parsing should support backward
compatible changes like new fields
Key: FLINK-33268
URL: https://issues.apache.org/jira/browse/FLINK-33268
Hi all.
If there are no further questions, we will start a vote on FLIP-375 next
week.
Best regards,
Yu Chen
Yu Chen 于2023年10月9日周一 17:24写道：
> Hi all,
>
> Yun Tang and I are opening this thread to discuss our proposal to
> integrate async-profiler's capabilities for profiling taskmananger (e.g.
One minor comment:
In general, the generic java profiler includes memory analysis,
cpu, thread, deadlock, etc. The FLIP title is java profiler, but
the FLIP just supports flamegraph at process level.
So the `powerful java profiler` title may not be suitable.
Would you mind updating the FLIP title?
Hi Zakelly,
What if an omitted key hint only applied for tables from the current query
> block?
>
Can you elaborate on some examples to illustrate? But if you're asking
about the usage mentioned in [1], like " SELECT * FROM left /*+ STATE_TTL(
'1h' ) */ JOIN right /*+ STATE_TTL('1d') */ ON ...; "
+1 (non-binding)
Best,
Jane
On Fri, Oct 13, 2023 at 11:20 AM Yuxin Tan wrote:
> +1(non-binding)
>
> Best,
> Yuxin
>
>
> Zhanghao Chen 于2023年10月13日周五 10:54写道：
>
> > +1 (non-binding)
> >
> > Best,
> > Zhanghao Chen
> >
> > From: Junrui Lee
> > Sent: Friday, Octo
Hi Yuan,
Thanks for sharing your thoughts!
In Flink 2.0 I believe we could design brand-new state APIs, which is
uncertain and may take some time. However, this proposal primarily
focuses on improving the consistency of interface definitions and
enhancing the user experience in error handling for
Hi all,
I am happy to announce that FLIP-239: Port JDBC Connector to
FLIP-27&FLIP-143[1] has been accepted.
There are 8 approving votes, 5 of which are binding:
- Yuepeng Pan (non-binding)
- Jing Ge (binding)
- Samrat Deb (non-binding)
- Martijn Visser (binding)
- Sergey Nuyanzin (binding)
- Leona
Hi Jane,
Actually, the first example that comes to mind is a simple group
aggregation, such as "SELECT /*+ STATE_TTL('1d') */ userid, SUM(price)
FROM orders GROUP BY userid;". However, as you mentioned, omitting the
key can introduce a lot of ambiguity, especially in nested query
blocks. I agree t
david radley created FLINK-33269:
Summary: light and dark scss files do not have apache licenses at
the top.
Key: FLINK-33269
URL: https://issues.apache.org/jira/browse/FLINK-33269
Project: Flink
Matthias Pohl created FLINK-33270:
-
Summary: Think about installing Java instead of providing it
through Docker
Key: FLINK-33270
URL: https://issues.apache.org/jira/browse/FLINK-33270
Project: Flink
HI Zakelly,
What about the jobs that catch those exceptions? Will these downstream
callers that expect this exception to be thrown break, since the exceptions
are part of the method's contract?
Best regards,
Jing
On Fri, Oct 13, 2023 at 11:01 AM Zakelly Lan wrote:
> Hi Yuan,
>
> Thanks for sha
Jing Ge created FLINK-33272:
---
Summary: CLONE - Build and stage Java and Python artifacts
Key: FLINK-33272
URL: https://issues.apache.org/jira/browse/FLINK-33272
Project: Flink
Issue Type: Sub-task
Jing Ge created FLINK-33271:
---
Summary: CLONE - Build Release Candidate: 1.18.0-rc2
Key: FLINK-33271
URL: https://issues.apache.org/jira/browse/FLINK-33271
Project: Flink
Issue Type: New Feature
Jing Ge created FLINK-33274:
---
Summary: CLONE - Propose a pull request for website updates
Key: FLINK-33274
URL: https://issues.apache.org/jira/browse/FLINK-33274
Project: Flink
Issue Type: Sub-task
Jing Ge created FLINK-33273:
---
Summary: CLONE - Stage source and binary releases on
dist.apache.org
Key: FLINK-33273
URL: https://issues.apache.org/jira/browse/FLINK-33273
Project: Flink
Issue Type
Jing Ge created FLINK-33275:
---
Summary: CLONE - Vote on the release candidate
Key: FLINK-33275
URL: https://issues.apache.org/jira/browse/FLINK-33275
Project: Flink
Issue Type: Sub-task
Affects
Hi,
It seems that migrating to the next dot version and finding you need to
recompile, would be frustrating and couse unexpected work, as I suspect a jar
file using the old API will give an exception around not finding the method – I
am not sure how this would surface in typical applications at
Matthias Pohl created FLINK-33276:
-
Summary: Reorganize CI stages
Key: FLINK-33276
URL: https://issues.apache.org/jira/browse/FLINK-33276
Project: Flink
Issue Type: Technical Debt
C
Hi Jing,
For jobs that catch exceptions, they will need to modify their code.
If they still wish to catch the exception, they should catch the
`Throwable` instead.
As I explained, this use case is not common because:
1. The user-defined processElement function, where the state APIs are
called, al
In the Wiki, this FLIP is motivated by:
- That the current flamegraph functionality can only see operator-level
stack traces, while async-profiler provides CPU/allocation/locks
information, along with deeper Java & system call stack information.
- Low configurability (e.g. cannot set the sampling
23 matches
Mail list logo
