TisonKun created FLINK-11106:
Summary: Remove legacy flink-yarn component
Key: FLINK-11106
URL: https://issues.apache.org/jira/browse/FLINK-11106
Project: Flink
Issue Type: Sub-task
Hi All,
Thank Aljoscha for further spitting up topics.
I will start separate threads on each topic which you propose.
Best,
Haibo
Aljoscha Krettek-2 wrote
> Hi All,
>
> this is a great discussion! (I have some thoughts on most of the topics
> but I'll wait for the separate discussion
Yang Wang created FLINK-11105:
-
Summary: Add an new implementation of the HighAvailabilityServices
using etcd
Key: FLINK-11105
URL: https://issues.apache.org/jira/browse/FLINK-11105
Project: Flink
Hi all,
I think we are making good progress. Thanks for all the feedback so far.
3. Sources/Sinks:
It seems that I can not find supporters for explicit SOURCE/SINK
declaration so I'm fine with not using those keywords.
@Fabian: Maybe we don't haven have to change the TableFactory interface
Dear community,
I wanted to reach out to you and discuss whether we should release a last
bug fix release for the 1.5 branch.
Since we have already released Flink 1.7.0, we only need to support the
1.6.x and 1.7.x branches (last two major releases). However, the current
release-1.5 branch
Dear Flink community,
in order to better understand the needs of our users and to plan for the
future, I wanted to reach out to you and ask how much you use Flink's
Python API, namely flink-python and flink-streaming-python.
In order to gather feedback, I would like to ask all Python users to
Dear community,
this is the weekly community update thread #49. Please post any news and
updates you want to share with the community to this thread.
# Flink 1.7.0 has been released
The community has release Flink 1.7.0 [1].
# Flink intro slide set
Fabian has refined the slide set for an
Hi,
this is a very nice effort!
There is one thing that we should change, though. In the batch API we have a
clear separation between API and runtime, and using the API (depending on
flink-batch) does not "expose" the runtime classes that are in flink-runtime.
For the streaming API, we made
Denys Fakhritdinov created FLINK-11104:
--
Summary: LEFT JOIN with Table Function not working
Key: FLINK-11104
URL: https://issues.apache.org/jira/browse/FLINK-11104
Project: Flink
Issue
Hi all,
Thanks for the discussion.
I'd like to share my point of view as well.
4) Event-Time Attributes and Watermarks:
4.a) I agree with Lin and Jark's proposal. Declaring a watermark on an
attribute declares it as an event-time attribute.
4.b) Ingesting and writing timestamps to systems (like
Nico Kruber created FLINK-11103:
---
Summary: Set a default uncaught exception handler
Key: FLINK-11103
URL: https://issues.apache.org/jira/browse/FLINK-11103
Project: Flink
Issue Type:
Nico Kruber created FLINK-11102:
---
Summary: Enable check for previous data in SpanningRecordSerializer
Key: FLINK-11102
URL: https://issues.apache.org/jira/browse/FLINK-11102
Project: Flink
Chesnay Schepler created FLINK-11101:
Summary: Ineffective openjdk exclusion Presto S3 FileSystem module
Key: FLINK-11101
URL: https://issues.apache.org/jira/browse/FLINK-11101
Project: Flink
Chesnay Schepler created FLINK-11100:
Summary: Presto S3 FileSystem E2E test broken
Key: FLINK-11100
URL: https://issues.apache.org/jira/browse/FLINK-11100
Project: Flink
Issue Type: Bug
xuqianjin created FLINK-11099:
-
Summary: Migrate flink-table runtime Row Types classes
Key: FLINK-11099
URL: https://issues.apache.org/jira/browse/FLINK-11099
Project: Flink
Issue Type: Sub-task
xuqianjin created FLINK-11098:
-
Summary: Migrate flink-table runtime Row Types classes
Key: FLINK-11098
URL: https://issues.apache.org/jira/browse/FLINK-11098
Project: Flink
Issue Type: New
xuqianjin created FLINK-11097:
-
Summary: Migrate flink-table runtime io classes
Key: FLINK-11097
URL: https://issues.apache.org/jira/browse/FLINK-11097
Project: Flink
Issue Type: Bug
Weihua Jiang created FLINK-11096:
Summary: Create a new table based flink ML package
Key: FLINK-11096
URL: https://issues.apache.org/jira/browse/FLINK-11096
Project: Flink
Issue Type:
Hi Timo,
Thanks for your quickly feedback! Here are some of my thoughts:
Append, upserts, retract mode on sinks is also a very complex problem. I
think append/upserts/retract is the ability of a table, user do not need to
specify a table is used for append or retraction or upsert. The query can
Hi Timo,
Thanks for your feedback, here's some thoughts of mine:
3. Sources/Sinks:
"Let's assume an interactive CLI session, people should be able to list all
source table and sink tables to know upfront if they can use an INSERT INTO
here or not."
This requirement can be simply resolved by a
Hi all
Glad to see the discussion, we are now designing to enhance the scheduling
of batch job, a unified api will help a lot.
Haibo Sun 于2018年12月5日周三 下午4:45写道：
> Hi all,
>
> Thank Kurt, you see more benefits of the unification than I do.
>
> I quite agree Kurt's views. DataStream, DataSet and
Weihua Jiang created FLINK-11095:
Summary: Table based ML Pipeline
Key: FLINK-11095
URL: https://issues.apache.org/jira/browse/FLINK-11095
Project: Flink
Issue Type: New Feature
22 matches
Mail list logo
