If the semantics of both APIs are 100% equivalent, I'm fine with the
renaming. Have you checked that?
Regards,
Timo
On 06.01.20 10:46, Zhenghua Gao wrote:
+1 to align the terminology.
*Best Regards,*
*Zhenghua Gao*
On Fri, Jan 3, 2020 at 12:59 PM Jingsong Li <jingsongl...@gmail.com> wrote:
+1 for this documentation change.
Hope less confuse to users.
Best,
Jingsong Lee
On Fri, Jan 3, 2020 at 12:09 PM Benchao Li <libenc...@gmail.com> wrote:
+1
It's good to align the terminology between Table API & SQL and
DataStream.
Jark Wu <imj...@gmail.com> 于2020年1月3日周五 下午12:04写道：
Hi everyone,
As we discussed in the mailing list[1], the current "Time-windowed
Join"
in
Table API & SQL is a little misleading which is not the same to "Window
Join" in DataStream, but the same to "Interval Join" in DataStream.
So I would like to start a vote to rename the terminology of
"Time-windowed
Join" to "Interval Join" in Table API & SQL **before 1.10 release**.
Note that this is a purely documentation change, no updates for public
API
or Javadocs. Updates for implementation codes (e.g. rename
DataStreamWindowJoin) is not targeted to 1.10.
This vote will be open for at least 72 hours. Unless there is an
objection.
This vote is required Consensus Approval which is the same to a FLIP
vote.
Best,
Jark
[1]:
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Correct-the-terminology-of-quot-Time-windowed-Join-quot-to-quot-Interval-Join-quot-in-Table-L-td36202.html
--
Benchao Li
School of Electronics Engineering and Computer Science, Peking University
Tel:+86-15650713730
Email: libenc...@gmail.com; libenc...@pku.edu.cn
--
Best, Jingsong Lee
