Yun Gao created FLINK-25105:
---
Summary: Enables final checkpoint by default
Key: FLINK-25105
URL: https://issues.apache.org/jira/browse/FLINK-25105
Project: Flink
Issue Type: Sub-task
Hang Ruan created FLINK-25104:
-
Summary: Kafka table source cannot be used as bounded
Key: FLINK-25104
URL: https://issues.apache.org/jira/browse/FLINK-25104
Project: Flink
Issue Type:
wangbaohua created FLINK-25103:
--
Summary: KeyedBroadcastProcessFunction run set 6, parallelism
ValueState variables A, could you tell me how to store in the six tasks A
Key: FLINK-25103
URL:
Yun Gao created FLINK-25102:
---
Summary: ParquetFileSystemITCase.testPartialDynamicPartition
failed on azure
Key: FLINK-25102
URL: https://issues.apache.org/jira/browse/FLINK-25102
Project: Flink
Yun Gao created FLINK-25101:
---
Summary:
FlinkKafkaProducerITCase.testMigrateFromAtLeastOnceToExactlyOnce failed due to
Key: FLINK-25101
URL: https://issues.apache.org/jira/browse/FLINK-25101
Project: Flink
Yun Gao created FLINK-25100:
---
Summary: RMQSourceITCase failed on azure due to
java.io.EOFException
Key: FLINK-25100
URL: https://issues.apache.org/jira/browse/FLINK-25100
Project: Flink
Issue
+1 for the new GraphBuilder API supports more complex
estimator / model structure and helps to reduce the repeat
code. Thanks Dong for the proposal.
Best,
Yun
--
From:Becket Qin
Send Time:2021 Nov. 22 (Mon.) 11:45
To:dev
Thanks David, Matthias and Mika,
I like this FLIP in the way it handles potential re-execution and resource
leaks due to clean-up failures.
I have one question: Why is this JobResultStore not part of the high
availability services? Or ask differently, are there cases that we only
need the HA
chenqizhu created FLINK-25099:
-
Summary: flink on yarn Accessing two HDFS Clusters
Key: FLINK-25099
URL: https://issues.apache.org/jira/browse/FLINK-25099
Project: Flink
Issue Type: Bug
Hi,
I didn't fully read the FLIP but the name somehow confused me. My first
impression of
seeing this is we are providing some storage for job execution results,
like the one
returned with accumulators in batch mode. Would a name like
"JobStautsStore" be more
appropriate?
Best,
Kurt
On Mon,
Adrian Vasiliu created FLINK-25098:
--
Summary: Jobmanager CrashLoopBackOff in HA configuration
Key: FLINK-25098
URL: https://issues.apache.org/jira/browse/FLINK-25098
Project: Flink
Issue
>
> > One way to avoid write-read-merge is by wrapping SinkWriter with
> > another one, which would buffer input elements in a temporary storage
> > (e.g. local file) until a threshold is reached; after that, it would
> > invoke the original SinkWriter. And if a checkpoint barrier comes in
> >
Chu Xue created FLINK-25097:
---
Summary: Bug in inner join when the filter condition is boolean
type
Key: FLINK-25097
URL: https://issues.apache.org/jira/browse/FLINK-25097
Project: Flink
Issue
Mahima created FLINK-25096:
--
Summary: Issue in exceptions API(/jobs/:jobid/exceptions) in flink
1.13.2
Key: FLINK-25096
URL: https://issues.apache.org/jira/browse/FLINK-25096
Project: Flink
Issue
Thanks for drafting this FLIP, Matthias, Mika and David.
I like the proposed JobResultStore. Besides addressing the problem of
re-executing finished jobs, it's also an important step towards HA of
multi-job Flink applications.
I have one question that, in the "Cleanup" section, it shows that the
xiangqiao created FLINK-25095:
-
Summary: org.apache.flink.table.planner.codegen.CodeGenException:
Mismatch of function's argument data type 'BOOLEAN NOT NULL' and actual
argument type 'BOOLEAN'.
Key: FLINK-25095
Jinzhong Li created FLINK-25094:
---
Summary: The verify code in
LatencyTrackingMapStateTest#verifyIterator is not actually executed
Key: FLINK-25094
URL: https://issues.apache.org/jira/browse/FLINK-25094
Martijn Visser created FLINK-25093:
--
Summary: Implement retry function for Bash based Docker setup
Key: FLINK-25093
URL: https://issues.apache.org/jira/browse/FLINK-25093
Project: Flink
I agree with Ingo. We can open a new JIRA issue or thread to discuss it.
Best,
Jark
On Mon, 29 Nov 2021 at 16:26, Ingo Bürk wrote:
> I of course meant DQL, not DDL, but same thing either way. It is akin to
> e.g. SHOW TABLES.
>
> On Mon, Nov 29, 2021 at 9:24 AM Ingo Bürk wrote:
>
> > To me
Martijn Visser created FLINK-25092:
--
Summary: Implement retry function for Bash bashed Elasticsearch
test
Key: FLINK-25092
URL: https://issues.apache.org/jira/browse/FLINK-25092
Project: Flink
I definitely understand the argument to continue supporting the existing
(return null) as the default behaviour.
I'd like to point out though that if we decide this (option no.2) it's kind
of unnatural, to directly drop the flag in *Flink 2.0*
for example, and force the users at that point to use
Congrats!!
On Mon, Nov 22, 2021 at 9:14 AM 刘建刚 wrote:
> Congratulations!
>
> Matthias Pohl 于2021年11月22日周一 下午4:10写道：
>
> > Congratulations :-)
> >
> > On Thu, Nov 18, 2021 at 3:23 AM Jingsong Li
> > wrote:
> >
> > > Congratulations, Jing! Well deserved!
> > >
> > > On Wed, Nov 17, 2021 at 3:00
+1 from me as well on the Java 8 deprecation!
It's important to make the users aware, and "force" them but also the
communities of other
related projects (like the aforementioned Hive) to start preparing for the
future drop of Java 8
support and the upgrade to the recent stable versions.
On Sun,
Thanks all for the updates! To summarize, these are open tickets that are
considered blockers for Flink 1.14.1:
* https://issues.apache.org/jira/browse/FLINK-22113 - UniqueKey constraint
is lost with multiple sources join in SQL -> @Marios Trivyzas
can you give an estimate when you expect this
Hi Timo!
Thanks a lot for taking all that time and effort to put together this
proposal!
Regarding:
> For simplification of the design, we assume that upgrades use a step size
of a single
minor version. We don't guarantee skipping minor versions (e.g. 1.11 to
1.14).
I think that for this first
XiangQianLiu created FLINK-25091:
Summary: Official website document FileSink orc compression
attribute reference error
Key: FLINK-25091
URL: https://issues.apache.org/jira/browse/FLINK-25091
I of course meant DQL, not DDL, but same thing either way. It is akin to
e.g. SHOW TABLES.
On Mon, Nov 29, 2021 at 9:24 AM Ingo Bürk wrote:
> To me this doesn't seem too related to the FLIP – this feature would
> require new DDL, and new DDL should live in Flink itself, not in the SQL
> client.
To me this doesn't seem too related to the FLIP – this feature would
require new DDL, and new DDL should live in Flink itself, not in the SQL
client.
I don't think this requires a FLIP, necessarily, though. It can probably
just be discussed on a JIRA issue.
Ingo
On Mon, Nov 29, 2021 at 9:19 AM
Hi Daisy
Thank you for the proposal.
I like it.
It was not discussed within this FLIP.
I'm not sure about the procedure in such cases (since voting finished).
Maybe a separate discussion thread makes sense.
However I think it could be done as well if there is no objection.
On Fri, Nov 26,
Francesco Guardiani created FLINK-25090:
---
Summary: Run the assertj conversion script to convert assertions
Key: FLINK-25090
URL: https://issues.apache.org/jira/browse/FLINK-25090
Project: Flink
30 matches
Mail list logo
