Jingsong Lee created FLINK-31236:
Summary: Limit pushdown will open useless RecordReader
Key: FLINK-31236
URL: https://issues.apache.org/jira/browse/FLINK-31236
Project: Flink
Issue Type:
leo.zhi created FLINK-31235:
---
Summary: Flink Jdbc Connector can not push down where condition
Key: FLINK-31235
URL: https://issues.apache.org/jira/browse/FLINK-31235
Project: Flink
Issue Type: Bug
Thanks for the response. I think we can also incorporate the performance
regression monitoring with Slack in the feature, which Yanfei ever did [1].
[1] https://lists.apache.org/thread/b75j2sgzhf25298p4982fy9tzdjrvght
Best
Yun Tang
From: Jingsong Li
Sent:
Hi Jark,
thanks for your comment.
>Considering they
> are orthogonal and information schema requires more complex design and
> discussion, it deserves a separate FLIP
I'm ok with a separate FLIP for INFORMATION_SCHEMA.
>Sergey, are you willing to contribute this FLIP?
Seems I need to have more
+1 (non-binding)
BTW, should we follow the content style [1] to describe the new rule using
1.2.x, 1.1.y, 1.1.z?
[1] https://flink.apache.org/downloads/#update-policy-for-old-releases
Best regards,
Jing
On Mon, Feb 27, 2023 at 1:06 PM Matthias Pohl
wrote:
> Thanks, Danny. Sounds good to me.
Hi, dev,
We recently used *SourceCoordinator* and *ExternallyInducedSource* to work
together on some file type connectors to fulfill some requirements, but we
found that these two interfaces do not work well together.
*SourceCoordinator* (FLINK-15101) and *ExternallyInducedSource*
(FLINK-20270)
Amit Gurdasani created FLINK-31243:
--
Summary: KryoSerializer when loaded from user code classloader
cannot load Scala extensions from app classloader
Key: FLINK-31243
URL:
Thanks, Danny. Sounds good to me.
+1 (non-binding)
On Wed, Feb 22, 2023 at 10:11 AM Danny Cranmer
wrote:
> I am starting a vote to update the "Update Policy for old releases" [1] to
> include additional bugfix support for end of life versions.
>
> As per the discussion thread [2], the change
Hi Timo,
Thanks for your advice. I totally agree with your suggestion of naming
convention, I will rename these options and update the flip later, thanks
very much.
In our internal implementation we had put these options inside the
`FactoryUtil`, just as you expect. We have also taken into
Hi everyone,
I would like to begin a discussion on FLIP-298: Unifying the Implementation
of SlotManager[1]. There are currently two types of SlotManager in Flink:
DeclarativeSlotManager and FineGrainedSlotManager. FineGrainedSlotManager
should behave as DeclarativeSlotManager if the user does not
Matthias Pohl created FLINK-31244:
-
Summary:
OffHeapUnsafeMemorySegmentTest.testCallCleanerOnceOnConcurrentFree prints
IllegalStateException
Key: FLINK-31244
URL:
Zhanghao Chen created FLINK-31245:
-
Summary: Adaptive scheduler does not reset the state of
GlobalAggregateManager when rescaling
Key: FLINK-31245
URL: https://issues.apache.org/jira/browse/FLINK-31245
Thanks for driving this topic. I think this FLIP could help clean up the
codebase to make it easier to maintain. +1 on it.
Best,
Zhanghao Chen
From: Weihua Hu
Sent: Monday, February 27, 2023 20:40
To: dev
Subject: [DISCUSS] FLIP-298: Unifying the Implementation
Hi Kui Yuan,
thanks for working on this FLIP. Let me also give some comments about
the proposed changes.
I support the direction of this FLIP about handling these
watermark-specific properties through options and /*+OPTIONS(...) */ hints.
Regarding naming, I would like to keep the options
Matthias Pohl created FLINK-31241:
-
Summary: Hive dependency cannot be resolved
Key: FLINK-31241
URL: https://issues.apache.org/jira/browse/FLINK-31241
Project: Flink
Issue Type: Bug
jackylau created FLINK-31237:
Summary: Fix possible bug of array_distinct
Key: FLINK-31237
URL: https://issues.apache.org/jira/browse/FLINK-31237
Project: Flink
Issue Type: Bug
Affects
Yue Ma created FLINK-31238:
--
Summary: Use IngestDB to speed up Rocksdb rescaling recovery
Key: FLINK-31238
URL: https://issues.apache.org/jira/browse/FLINK-31238
Project: Flink
Issue Type:
Hi Daniel,
Thanks for reaching out. Keep in mind that you weren't subscribed to the
Flink Dev mailing list, I've just pushed this through the mailing list
moderation.
The process for contributing a connector is to create a Connector FLIP [1],
which needs to be discussed and voted on in the Dev
Good morning,
I am a senior software engineer at Bloomberg working on a streaming system that
uses Apache Flink. I would like to join the Slack community to ask a few
questions regarding the best practices for structuring the pipeline.
Unfortunately, the invite link listed in the Community &
dalongliu created FLINK-31239:
-
Summary: Fix sum function can't get the corrected value when the
argument type is string
Key: FLINK-31239
URL: https://issues.apache.org/jira/browse/FLINK-31239
Project:
Hi Yun and Shammon,
> track the performance changes of the micro benchmark
I think we can create a github action for this. Print results everyday.
Best,
Jingsong
On Mon, Feb 27, 2023 at 5:59 PM Shammon FY wrote:
>
> Hi jingsong
>
> Getting rid of JMH is a good idea. For the second point, how
Hello flink devs,
My name is Daniel, I'm the tech lead for Google's Pub/Sub Lite streaming
system, which is a lower cost streaming data system with semantics more
similar to OSS streaming solutions. I've authored a source and sink
connector for flink and load tested it at GiB/s scale- what would
Hi Viacheslav,
Thanks for flagging this. I've updated the Slack invite link.
Best regards,
Martijn
On Mon, Feb 27, 2023 at 10:01 AM Viacheslav Chernyshev <
v.chernys...@outlook.com> wrote:
> Good morning,
>
> I am a senior software engineer at Bloomberg working on a streaming system
> that
Jiang Xin created FLINK-31240:
-
Summary: Reduce the overhead of conversion between DataStream and
Table
Key: FLINK-31240
URL: https://issues.apache.org/jira/browse/FLINK-31240
Project: Flink
Hi jingsong
Getting rid of JMH is a good idea. For the second point, how can we track
the performance changes of the micro benchmark? What do you think?
Best,
Shammon
On Mon, Feb 27, 2023 at 10:57 AM Jingsong Li wrote:
> Thanks Yun.
>
> Another way is we can get rid of JMH, something like
Thank you!
From: Martijn Visser
Sent: 27 February 2023 09:24
To: dev@flink.apache.org
Subject: Re: Slack community invitation request
Hi Viacheslav,
Thanks for flagging this. I've updated the Slack invite link.
Best regards,
Martijn
On Mon, Feb 27, 2023 at
Xianxun Ye created FLINK-31242:
--
Summary: Correct the definition of creating functions in the SQL
client documentation
Key: FLINK-31242
URL: https://issues.apache.org/jira/browse/FLINK-31242
Project:
Hi Ming,
I am not sure if I fully understand what you want. It seems what you are
looking for is to have a checkpoint triggered at a customized timing which
aligns with some semantic. This is not what the current checkpoint in Flink
was designed for. I think the basic idea of checkpoint is to
Hi Ran,
It would be great if we could support ILIKE [1]. If you figure out that the
effort is bigger than you expected, you might want to create a ticket for
beginners(?) who are interested in Flink development to make a further
contribution. WDYT?
Best regards,
Jing
[1]
Sergio Sainz created FLINK-31247:
Summary: Support for fine-grained resource allocation (slot
sharing groups) at the TableAPI level
Key: FLINK-31247
URL: https://issues.apache.org/jira/browse/FLINK-31247
Peter Vary created FLINK-31246:
--
Summary: Remove PodTemplate description from the SpecChange message
Key: FLINK-31246
URL: https://issues.apache.org/jira/browse/FLINK-31246
Project: Flink
Issue
Hi, Shammon,
I think the method `void deserialize(byte[] message, Collector out)`
with a default implementation encapsulate how to deal with null for
developers. If we remove the `T deserialize(byte[] message)`, the
developers have to remember to handle null. Maybe we will get duplicate
code
Thanks, Danny.
+1 (non-binding)
Best,
Weihua
On Tue, Feb 28, 2023 at 12:38 PM weijie guo
wrote:
> Thanks Danny for bring this.
>
> +1 (non-binding)
>
> Best regards,
>
> Weijie
>
>
> Jing Ge 于2023年2月27日周一 20:23写道：
>
> > +1 (non-binding)
> >
> > BTW, should we follow the content style [1] to
Shammon created FLINK-31251:
---
Summary: Deprecate deserialize method in DeserializationSchema
Key: FLINK-31251
URL: https://issues.apache.org/jira/browse/FLINK-31251
Project: Flink
Issue Type:
Nicholas Jiang created FLINK-31250:
--
Summary: ParquetSchemaConverter supports MULTISET type for parquet
format
Key: FLINK-31250
URL: https://issues.apache.org/jira/browse/FLINK-31250
Project: Flink
Hi devs
Currently there are two deserialization methods in `DeserializationSchema`
1. `T deserialize(byte[] message)`, only deserialize one record from
binary, if there is no record it should return null.
2. `void deserialize(byte[] message, Collector out)`, supports
deserializing none, one or
This is a good proposal for me, it will make the code of the SlotManager more
clear.
--
Best,
Matt Wang
Replied Message
| From | David Morávek |
| Date | 02/27/2023 22:45 |
| To | |
| Subject | Re: [DISCUSS] FLIP-298: Unifying the Implementation of SlotManager |
Hi Weihua, I
Thanks Danny for driving it.
+1 (non-binding)
Best regards,
Yuxia
- 原始邮件 -
发件人: "Weihua Hu"
收件人: "dev"
发送时间: 星期二, 2023年 2 月 28日 下午 12:48:09
主题: Re: [VOTE] Flink minor version support policy for old releases
Thanks, Danny.
+1 (non-binding)
Best,
Weihua
On Tue, Feb 28, 2023 at
Hi, guys. thanks for advices.
allow me to make a small summary:
1.Support ILIKE
2.Using catalog api to support show operations
3.Need a dedicated FLIP try to support INFORMATION_SCHEMA
4.Support SHOW CONNECTORS
If there are no other questions, i will try to start a VOTE for this FLIP.
WDYT?
Hi, Jiangjie,
Thanks for your reply and suggestion.
In fact, we don't want to modify the way JM triggers checkpoint, but we
hope to give OperatorCoodinator a mechanism similar to
ExternallyInducedSourceReader to coordinate the sending timing of
checkpoint barrier (just advance from Source to
Jingsong Lee created FLINK-31252:
Summary: Improve StaticFileStoreSplitEnumerator to assign batch
splits
Key: FLINK-31252
URL: https://issues.apache.org/jira/browse/FLINK-31252
Project: Flink
Jingsong Lee created FLINK-31248:
Summary: Improve documentation for append-only table
Key: FLINK-31248
URL: https://issues.apache.org/jira/browse/FLINK-31248
Project: Flink
Issue Type:
renxiang zhou created FLINK-31249:
-
Summary: Checkpoint Timer failed to process timeout events when it
blocked at writing _metadata to DFS
Key: FLINK-31249
URL: https://issues.apache.org/jira/browse/FLINK-31249
Thanks Danny for bring this.
+1 (non-binding)
Best regards,
Weijie
Jing Ge 于2023年2月27日周一 20:23写道：
> +1 (non-binding)
>
> BTW, should we follow the content style [1] to describe the new rule using
> 1.2.x, 1.1.y, 1.1.z?
>
> [1]
Jingsong Lee created FLINK-31253:
Summary: Port itcases to Flink 1.15 and 1.14
Key: FLINK-31253
URL: https://issues.apache.org/jira/browse/FLINK-31253
Project: Flink
Issue Type: Improvement
Jingsong Lee created FLINK-31254:
Summary: Improve the read performance for files table
Key: FLINK-31254
URL: https://issues.apache.org/jira/browse/FLINK-31254
Project: Flink
Issue Type:
Hi Jing, I think we can support it, it's not a very difficult job.
thank you.
Best Regards,
Ran Tao
Jing Ge 于2023年2月28日周二 06:04写道：
> Hi Ran,
>
> It would be great if we could support ILIKE [1]. If you figure out that the
> effort is bigger than you expected, you might want to create a ticket
Hi dev,
I'd like to open discussion on deprecating Global Aggregate Manager in favor of
Operator Coordinator.
1. Global Aggregate Manager is rarely used and can be replaced by Opeator
Coordinator. Global Aggregate Manager was introduced in
I think this makes sense, +1 from my side; as I wrote on the ticket, I'm
not aware of any other usages apart from the kinesis connector, and we
already have more feature complete API that can replace the functionality
there.
Best,
D.
On Mon, Feb 27, 2023 at 2:44 PM Zhanghao Chen
wrote:
> Hi
Hi Weihua, I still need to dig into the details, but the overall sentiment
of this change sounds reasonable.
Best,
D.
On Mon, Feb 27, 2023 at 2:26 PM Zhanghao Chen
wrote:
> Thanks for driving this topic. I think this FLIP could help clean up the
> codebase to make it easier to maintain. +1 on
Hello Martijn,
Thanks for the redirect!
> The process for contributing a connector is to create a Connector FLIP
[1], which needs to be discussed and voted on in the Dev mailing list [2]
I don't mind doing this, but would like to get a read of the room before
doing so. If people object to it,
51 matches
Mail list logo
