谢波 created FLINK-20463:
--
Summary: flink-1.11.2 -sql cannot ignore exception record
Key: FLINK-20463
URL: https://issues.apache.org/jira/browse/FLINK-20463
Project: Flink
Issue Type: Bug
Compon
Hi Dhurandar,
I'm afraid that Flink's rest API cannot satisfy your request as it would not
act as any source. One possible example could be SocketWindowWordCount [1]
which listens data on a port from all taskmanagers with sources.
[1]
https://github.com/apache/flink/blob/master/flink-examples/
Huang Xingbo created FLINK-20462:
Summary: MailboxOperatorTest.testAvoidTaskStarvation
Key: FLINK-20462
URL: https://issues.apache.org/jira/browse/FLINK-20462
Project: Flink
Issue Type: Bug
Huang Xingbo created FLINK-20461:
Summary:
YARNFileReplicationITCase.testPerJobModeWithDefaultFileReplication
Key: FLINK-20461
URL: https://issues.apache.org/jira/browse/FLINK-20461
Project: Flink
Jark Wu created FLINK-20460:
---
Summary: Support async lookup for HBase connector
Key: FLINK-20460
URL: https://issues.apache.org/jira/browse/FLINK-20460
Project: Flink
Issue Type: New Feature
Qingsheng Ren created FLINK-20459:
-
Summary: Handle null message correctly in JSON RowData deserializer
Key: FLINK-20459
URL: https://issues.apache.org/jira/browse/FLINK-20459
Project: Flink
CaoZhen created FLINK-20458:
---
Summary: Translate page 'SQL-gettingStarted' into Chinese
Key: FLINK-20458
URL: https://issues.apache.org/jira/browse/FLINK-20458
Project: Flink
Issue Type: Sub-task
Dian Fu created FLINK-20457:
---
Summary: Fix the handling of timestamp in
DataStream.from_collection
Key: FLINK-20457
URL: https://issues.apache.org/jira/browse/FLINK-20457
Project: Flink
Issue Type
Seth Wiesman created FLINK-20456:
Summary: Make streaming SQL concepts more approachable
Key: FLINK-20456
URL: https://issues.apache.org/jira/browse/FLINK-20456
Project: Flink
Issue Type: Imp
Can Flink job be running as Rest Server, Where Apache Flink job is
listening on a port (443). When a user calls this URL with payload,
data directly goes to the Apache Flink windowing function.
Right now Flink can ingest data from Kafka or Kinesis, but we have a use
case where we would like to pus
Robert Metzger created FLINK-20455:
--
Summary: Add check to LicenseChecker for top level /LICENSE files
in shaded jars
Key: FLINK-20455
URL: https://issues.apache.org/jira/browse/FLINK-20455
Project:
Jark Wu created FLINK-20454:
---
Summary: Allow to read metadata for debezium-avro-confluent format
Key: FLINK-20454
URL: https://issues.apache.org/jira/browse/FLINK-20454
Project: Flink
Issue Type: S
Roman Khachatryan created FLINK-20453:
-
Summary: Move checkpointing classes to a the appropriate package
Key: FLINK-20453
URL: https://issues.apache.org/jira/browse/FLINK-20453
Project: Flink
Hi guys,
I'd like to start a discussion about providing HiveQL compatibility for
users connecting to a hive warehouse. FLIP-123 has already covered most
DDLs. So now it's time to complement the other big missing part -- queries.
With FLIP-152, the hive dialect covers more scenarios and makes it ev
HideOnBush created FLINK-20452:
--
Summary: Mysql JDBC Sink UpsertStreamTableSink requires that Table
has a full primary keys
Key: FLINK-20452
URL: https://issues.apache.org/jira/browse/FLINK-20452
Project
xiaozilong created FLINK-20451:
--
Summary: Taskmanager Could't apply resources if use configs
`env.java.opts.taskmanager: -javaagent:`
Key: FLINK-20451
URL: https://issues.apache.org/jira/browse/FLINK-20451
Hi everyone,
We have resolved the licensing issue Chesnay found.
Please review and vote on the release candidate #3 for the version 1.12.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for y
Matthias created FLINK-20450:
Summary: Missing usage information on "run-application" in Flink
CLI
Key: FLINK-20450
URL: https://issues.apache.org/jira/browse/FLINK-20450
Project: Flink
Issue Ty
Hey,
Thanks a lot for that.
Best Regards,
Dom.
śr., 2 gru 2020 o 03:45 Yun Tang napisał(a):
> Hi Dom,
>
> + user mail list
>
> Once you got to know the state descriptor, I think you could query the
> join state. The state name is easy to get via [1], it should be
> "left-records" and "right-reco
19 matches
Mail list logo