魏旭斌 created FLINK-19407:
---
Summary: Translate "Elasticsearch Connector" page of "Connectors"
into Chinese
Key: FLINK-19407
URL: https://issues.apache.org/jira/browse/FLINK-19407
Project: Flink
Issue
Rui Li created FLINK-19406:
--
Summary: Casting row time to timestamp loses nullability info
Key: FLINK-19406
URL: https://issues.apache.org/jira/browse/FLINK-19406
Project: Flink
Issue Type: Bug
+1
> 在 2020年9月24日，21:54，Seth Wiesman 写道：
>
> +1
>
> On Thu, Sep 24, 2020 at 2:49 AM Rui Li wrote:
>
>> +1
>>
>> On Thu, Sep 24, 2020 at 2:59 PM Timo Walther wrote:
>>
>>> +1
>>>
>>> On 24.09.20 06:54, Jark Wu wrote:
+1 to move it there.
On Thu, 24 Sep 2020 at 12:16,
Hi，Aljoscha, I would like to share a use case to second setting parallelism
of table sink(or limiting parallelism range of table sink): When writing
data to databases, there is limitation for number of jdbc connections and
query TPS. we would get errors of too many connections or high load for
db
weizheng created FLINK-19405:
Summary: Translate "DataSet Connectors" page of "Connectors" into
Chinese
Key: FLINK-19405
URL: https://issues.apache.org/jira/browse/FLINK-19405
Project: Flink
Huang Xingbo created FLINK-19404:
Summary: Support Pandas Stream Over Window Aggregation
Key: FLINK-19404
URL: https://issues.apache.org/jira/browse/FLINK-19404
Project: Flink
Issue Type:
Huang Xingbo created FLINK-19403:
Summary: Support Pandas Stream Group Window Aggregation
Key: FLINK-19403
URL: https://issues.apache.org/jira/browse/FLINK-19403
Project: Flink
Issue Type:
Hi Yu,
bq* I thought the FLIP aims at resolving some *existing* confusion, i.e.
the durability mystery to users.
I think it might help to highlight specific stumbling blocks users have
today and why I believe this change addresses those issues. Some frequent
things I've heard over the past
Yu Yang created FLINK-19402:
---
Summary: Metrics for measuring Flink application deployment
latency in Yarn
Key: FLINK-19402
URL: https://issues.apache.org/jira/browse/FLINK-19402
Project: Flink
Guowei,
Thanks a lot for updating the wiki page. It looks great.
I noticed one inconsistency in the wiki with your last summary email for
GlobalCommitter interface. I think the version in the summary email is the
intended one, because rollover from previous failed commits can accumulate
a list.
Steven Zhen Wu created FLINK-19401:
--
Summary: Job stuck in restart loop due to "Could not find
registered job manager"
Key: FLINK-19401
URL: https://issues.apache.org/jira/browse/FLINK-19401
Arvid Heise created FLINK-19400:
---
Summary: Removed unused BufferPoolOwner
Key: FLINK-19400
URL: https://issues.apache.org/jira/browse/FLINK-19400
Project: Flink
Issue Type: Bug
And to make it clear, I'm +1 on the idea of decoupling state backends with
checkpointing. I don't have any question about making it clear that
heap/RocksDB is where we serve the routine state read/write and where to
put the checkpoint data is another story. My only concern lies in the newly
*bq. What new confusion would be introduced here?*
No *new* confusion introduced, but as mentioned at the very beginning of
the motivation ("Apache Flink's durability story is a mystery to many
users"), I thought the FLIP aims at resolving some *existing*
confusions, i.e. the durability mystery to
Igal Shilman created FLINK-19399:
Summary: Add Python AsyncRequestReplyHandler docs
Key: FLINK-19399
URL: https://issues.apache.org/jira/browse/FLINK-19399
Project: Flink
Issue Type: Task
Thanks for the proposal! I think the use cases that we are trying to
solve are indeed valid. However, I think we might have to take a step
back to look at what we're trying to solve and how we can solve it.
The FLIP seems to have two broader topics: 1) add "get parallelism" to
sinks/sources
+1 (binding)
- built from source
- built docker image
- verified Rust SDK works with the 2.2.0 docker image
Aljoscha
On 24.09.20 10:32, Tzu-Li (Gordon) Tai wrote:
FYI - the PR for the release announcement has just been drafted:
https://github.com/apache/flink-web/pull/379
Any comments
+1
On Thu, Sep 24, 2020 at 2:49 AM Rui Li wrote:
> +1
>
> On Thu, Sep 24, 2020 at 2:59 PM Timo Walther wrote:
>
> > +1
> >
> > On 24.09.20 06:54, Jark Wu wrote:
> > > +1 to move it there.
> > >
> > > On Thu, 24 Sep 2020 at 12:16, Jingsong Li
> > wrote:
> > >
> > >> Hi devs and users:
> > >>
>
Fabian Hueske created FLINK-19398:
-
Summary: Hive connector fails with IllegalAccessError if submitted
as usercode
Key: FLINK-19398
URL: https://issues.apache.org/jira/browse/FLINK-19398
Project:
Matthias created FLINK-19397:
Summary: Offering error handling for the SerializationSchema
analogous to DeserializationSchema
Key: FLINK-19397
URL: https://issues.apache.org/jira/browse/FLINK-19397
Hi Jingsong,
Thanks for preparing this FLIP.
WRT ParallelismProvider, it looks good to me.
Kurt Young 于2020年9月24日周四 下午4:14写道：
> Yeah, JDBC is definitely a popular use case we should consider.
>
> Best,
> Kurt
>
>
> On Thu, Sep 24, 2020 at 4:11 PM Flavio Pompermaier
> wrote:
>
> > Hi Kurt, in
Thanks Kurt and Flavio for your feedback.
To Kurt:
> Briefly introduce use cases and what kind of options are needed in your
opinion.
In the "Choose Scan Parallelism" chapter:
- I explained the user cases
- I adjusted the relationship to make user specified parallelism more
convenient
To
Hi, all
After the discussion in [1], I would like to open a voting thread for
FLIP-143 [2], which proposes a unified sink api.
The vote will be open until September 29th (72h + weekend), unless there is
an objection or not enough votes.
[1]
zhangmeng created FLINK-19396:
-
Summary: Fix properties type cast error
Key: FLINK-19396
URL: https://issues.apache.org/jira/browse/FLINK-19396
Project: Flink
Issue Type: Bug
Timo Walther created FLINK-19395:
Summary: Replace SqlConversionException with either TableException
or ValidationException
Key: FLINK-19395
URL: https://issues.apache.org/jira/browse/FLINK-19395
+1 (binding)
Best,
Jark
On Thu, 24 Sep 2020 at 16:22, Jingsong Li wrote:
> +1 (binding)
>
> Best,
> Jingsong
>
> On Thu, Sep 24, 2020 at 4:18 PM Kurt Young wrote:
>
> > +1 (binding)
> >
> > Best,
> > Kurt
> >
> >
> > On Thu, Sep 24, 2020 at 4:01 PM Timo Walther wrote:
> >
> > > Hi all,
> > >
Roc Marshal created FLINK-19394:
---
Summary: Translate the 'Monitoring Checkpointing' page of
'Debugging & Monitoring' into Chinese
Key: FLINK-19394
URL: https://issues.apache.org/jira/browse/FLINK-19394
Roc Marshal created FLINK-19393:
---
Summary: Translate the 'SQL Hints' page of 'Table API & SQL' into
Chinese
Key: FLINK-19393
URL: https://issues.apache.org/jira/browse/FLINK-19393
Project: Flink
FYI - the PR for the release announcement has just been drafted:
https://github.com/apache/flink-web/pull/379
Any comments there is also highly appreciated!
On Thu, Sep 24, 2020 at 5:47 AM Seth Wiesman wrote:
> +1 (non binding)
>
> - Verified signatures and checksums
> - Checked licenses and
+1 (binding)
Best,
Jingsong
On Thu, Sep 24, 2020 at 4:18 PM Kurt Young wrote:
> +1 (binding)
>
> Best,
> Kurt
>
>
> On Thu, Sep 24, 2020 at 4:01 PM Timo Walther wrote:
>
> > Hi all,
> >
> > after the discussion in [1], I would like to open a second voting thread
> > for FLIP-136 [2] which
+1 (binding)
Best,
Kurt
On Thu, Sep 24, 2020 at 4:01 PM Timo Walther wrote:
> Hi all,
>
> after the discussion in [1], I would like to open a second voting thread
> for FLIP-136 [2] which covers different topic to improve the
> back-and-forth communication between DataStream API and Table
Yeah, JDBC is definitely a popular use case we should consider.
Best,
Kurt
On Thu, Sep 24, 2020 at 4:11 PM Flavio Pompermaier
wrote:
> Hi Kurt, in the past we had a very interesting use case in this regard: our
> customer (oracle) db was quite big and running too many queries in parallel
>
Hi Kurt, in the past we had a very interesting use case in this regard: our
customer (oracle) db was quite big and running too many queries in parallel
was too heavy and it was causing the queries to fail.
So we had to limit the source parallelism to 2 threads. After the fetching
of the data the
Hi all,
after the discussion in [1], I would like to open a second voting thread
for FLIP-136 [2] which covers different topic to improve the
back-and-forth communication between DataStream API and Table API.
The vote will be open until September 29th (72h + weekend), unless there
is an
Thanks Jingsong for driving this, this is indeed a useful feature and lots
of users are asking for it.
For setting a fixed source parallelism, I'm wondering whether this is
necessary. For kafka,
I can imagine users would expect Flink will use the number of partitions as
the parallelism. If it's
+1
On Thu, Sep 24, 2020 at 2:59 PM Timo Walther wrote:
> +1
>
> On 24.09.20 06:54, Jark Wu wrote:
> > +1 to move it there.
> >
> > On Thu, 24 Sep 2020 at 12:16, Jingsong Li
> wrote:
> >
> >> Hi devs and users:
> >>
> >> After the 1.11 release, I heard some voices recently: How can't Hive's
>
Kostas Kloudas created FLINK-19392:
--
Summary: Detect the execution mode based on the sources in the job.
Key: FLINK-19392
URL: https://issues.apache.org/jira/browse/FLINK-19392
Project: Flink
Arvid Heise created FLINK-19391:
---
Summary: Deadlock during partition update
Key: FLINK-19391
URL: https://issues.apache.org/jira/browse/FLINK-19391
Project: Flink
Issue Type: Bug
badqiu created FLINK-19390:
--
Summary: mysql jdbc join error java.lang.ClassCastException:
java.math.BigInteger cannot be cast to java.lang.Long
Key: FLINK-19390
URL: https://issues.apache.org/jira/browse/FLINK-19390
+1
On 24.09.20 06:54, Jark Wu wrote:
+1 to move it there.
On Thu, 24 Sep 2020 at 12:16, Jingsong Li wrote:
Hi devs and users:
After the 1.11 release, I heard some voices recently: How can't Hive's
documents be found in the "Table & SQL Connectors".
Actually, Hive's documents are in the
40 matches
Mail list logo
