Support legacy mode for yyyymmdd format [databricks]

[res-life]

closes #11505

Required by customer.

Similar to this PR which supports yyyyMMdd, this PR supports yyyymmdd

Note: MM is month while mm is minute

Note: GPU and CPU are not 100% consistent for yyyymmdd format, GPU only supports 8 digit strings.

Signed-off-by: Chong Gao [email protected]

[res-life]

build

[firestarman]

is yyyymmdd an legal format string for date ?

yyyy represents the year, but mm for minutes ? Isn't weird that a date is in the format of {year}{minute}{day} ?

[res-life]

is yyyymmdd an legal format string for date ?

yyyy represents the year, but mm for minutes ? Isn't weird that a date is in the format of {year}{minute}{day} ?

In general, it's weird. But it's a valid format.
{year}{minute}{day} does specify year, minute and day; the missed parts like {month}{hour}{second} have default values. e.g.: month default value is 1.

[firestarman]

is yyyymmdd an legal format string for date ?
yyyy represents the year, but mm for minutes ? Isn't weird that a date is in the format of {year}{minute}{day} ?

In general, it's weird. But it's a valid format. {year}{minute}{day} does specify year, minute and day; the missed parts like {month}{hour}{second} have default values. e.g.: month default value is 1.

The code looks good, but I am not 100% sure on its functionality, and would like to wait for the premerge result and verification from customer runs before approving it.

[res-life]

build

[res-life]

build

[pxLi]

build

[res-life]

build