Hi Andrey,
Thanks for providing so detailed concerns and enlightenments for this proposal.
We exchanged our views of three main issues on google doc last week and it
seems more appropriate to further contact here. :)
1. Configuration level for shuffle (cluster/job/operator)
- how do we share s
Hi all,
It's great to see we have an agreement on MVP.
4.b) Ingesting and writing timestamps to systems.
I would treat the field as a physical column not a virtual column. If we
treat it as computed column, it will be confused that the behavior is
different when it is a source or sink.
When it is
hi all,
Thanks for your valuable input!
4) Event-Time Attributes and Watermarks:
4.b) @Fabian As you mentioned using a computed columns `ts AS
SYSTEMROWTIME()`
for writing out to kafka table sink will violate the rule that computed
fields are not emitted.
Since the timestamp column in kafka's head
Weihua Jiang created FLINK-5:
Summary: Port some flink.ml algorithms to table based
Key: FLINK-5
URL: https://issues.apache.org/jira/browse/FLINK-5
Project: Flink
Issue Type: Sub-
Weihua Jiang created FLINK-4:
Summary: Support wrapping inference pipeline as a UDF function in
SQL
Key: FLINK-4
URL: https://issues.apache.org/jira/browse/FLINK-4
Project: Flink
Weihua Jiang created FLINK-3:
Summary: Support periodically update models when inferencing
Key: FLINK-3
URL: https://issues.apache.org/jira/browse/FLINK-3
Project: Flink
Issue Typ
Weihua Jiang created FLINK-2:
Summary: Support pipeline import/export
Key: FLINK-2
URL: https://issues.apache.org/jira/browse/FLINK-2
Project: Flink
Issue Type: Sub-task
Weihua Jiang created FLINK-1:
Summary: Create a new set of parameters
Key: FLINK-1
URL: https://issues.apache.org/jira/browse/FLINK-1
Project: Flink
Issue Type: Sub-task
Weihua Jiang created FLINK-11108:
Summary: Create a new set of table based ML Pipeline classes
Key: FLINK-11108
URL: https://issues.apache.org/jira/browse/FLINK-11108
Project: Flink
Issue Typ
Weihua Jiang created FLINK-0:
Summary: Support pipeline stage type inference
Key: FLINK-0
URL: https://issues.apache.org/jira/browse/FLINK-0
Project: Flink
Issue Type: Sub-task
Weihua Jiang created FLINK-11109:
Summary: Create Table based optimizers
Key: FLINK-11109
URL: https://issues.apache.org/jira/browse/FLINK-11109
Project: Flink
Issue Type: Sub-task
Xianda Ke
9:47 AM (11 minutes ago)
to dev, user
After communicating with some of the internal users at Alibaba, my
impression is that:
- Most of them need C extensions support, they want to integrated their
algorithms with stream processing，but Jython is unacceptable for them.
- For some
After communicating with some of the internal users at Alibaba, my impression
is that:
* Most of them need C extentions support, they want to integrated their
algorithms with stream processing，but Jython is unacceptable for them.
* For some users, who are only familiar with SQL/Python, developin
+1. There are incompatible improvements between 1.5.x and 1.6/1.7, so many
1.5.x users may not be willing to upgrade to 1.6 or 1.7 due to migration
costs, so it makes sense to creating last bug fix release for 1.5 branch.
Bests,
Jincheng
Jeff Zhang 于2018年12月10日周一 上午9:24写道：
> +1, I think very fe
+1, I think very few people would use 1.6 or 1.7 in their production in
near future, so I expect they would use 1.5 in production for a long
period，it makes sense to provide a stable version for production usage.
Ufuk Celebi 于2018年12月9日周日 下午6:07写道：
> +1. This seems reasonable to me. Since the fi
Hi Zhijiang,
Thanks for sharing the document Zhijiang.
I decided to compile my thoughts to consider here, not to overload document
comments any more :)
I think I still have question about job level configuration for the shuffle
service. You mentioned that we can keep several shuffle manager ob
Few thoughts from my side:
(1) The client needs big refactoring / cleanup. It should use a proper HTTP
client library to help with future authentication mechanisms.
Once that is done, we should identify a "client API" that we make stable,
just as the DataStream / DataSet API.
(2) We will most lik
Yun Tang created FLINK-11107:
Summary: [state] Avoid memory stateBackend to create arbitrary
folders under HA path when no checkpoint path configured
Key: FLINK-11107
URL: https://issues.apache.org/jira/browse/FLINK-1
+1. This seems reasonable to me. Since the fixes are already in and
also part of other releases, the release overhead should be
manageable.
@Vino: I agree with your assessment.
@Qi: As Till mentioned, the official project guideline is to support
the last two minor releases, e.g. currently 1.7 and
19 matches
Mail list logo
