Hi Dongjoon,
Yes, As we want make CalenderIntervalType deprecated and so far, we just find
1. The make_interval function that produces legacy CalenderIntervalType values,
2. `interval` -> CalenderIntervalType support in the parser
Thanks
Kent Yao
Data Science Center, Hangzhou Research Institute, Netease Corp.
PHONE: (86) 186-5715-3499
EMAIL: hzyao...@corp.netease.com
On 01/11/2020 01:57，Dongjoon Hyun<dongjoon.h...@gmail.com> wrote：
Hi, Kent.Thank you for the proposal.Does your proposal need to revert something from the master branch?I'm just asking because it's not clear in the proposal document.Bests,Dongjoon.On Fri, Jan 10, 2020 at 5:31 AM Dr. Kent Yao <yaooq...@qq.com> wrote:Hi, Devs
I’d like to propose to add two new interval types which are year-month and
day-time intervals for better ANSI support and future improvements. We will
keep the current CalenderIntervalType but mark it as deprecated until we
find the right time to remove it completely. The backward compatibility of
the old interval type usages in 2.4 will be guaranteed.
Here is the design doc:
[SPIP] Support Year-Month and Day-Time Intervals -
https://docs.google.com/document/d/1JNRzcBk4hcm7k2cOXSG1A9U9QM2iNGQzBSXZzScUwAU/edit?usp=sharing
All comments are welcome!
Thanks,
Kent Yao
--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
