[
https://issues.apache.org/jira/browse/IGNITE-24676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-24676:
--------------------------------------
Description:
This is an umbrella ticket to keep track of all work related to productization
of temporal types.
The first phase is to review existing test coverage according to a test plan
(presented below) and add absent tests. The goal is to identify all issues
related to a temporal types. All found problems (as well as already filed ones)
must be linked to this epic.
Second phase will include fixing all attached issues, as well as amending
documentation with known limitation in case of problem that we are not going to
fix in the nearest future (for instance, a type `TIME WITH TIME ZONE` is not
supported and we have no plan to support it any time soon, therefor this must
be mentioned as known limitation).
Note: phases not necessary should be executed sequentially; critical issues may
be fixed asap.
A temporal types hierarchy is as follow:
* All temporal types
** Datetime types
*** DATE
*** TIME [WITHOUT TIME ZONE]
*** TIME WITH TIME ZONE // not supported; known limitation
*** TIME WITH LOCAL TIME ZONE // not supported; known limitation
*** TIMESTAMP [WITHOUT TIME ZONE]
*** TIMESTAMP WITH TIME ZONE // not supported; known limitation
*** TIMESTAMP WITH LOCAL TIME ZONE // not defined by SQL standard; extension
** Interval types
*** YEAR TO MONTH intervals
*** DAY TO SECOND intervals
Test plan is as follow:
* For all temporal types check different values (literals, dyn params, table
columns):
** check boundaries
** check different precisions for fraction of second
** for datetime types check leap year/month/second
** for literals check supported formats
** for table columns check support for defaults; boundaries check; different
precision for fraction of second
** for table columns check support in indexes (both SORTED and HASH)
* For all temporal types check operations:
** check type coercion for all allowed operations
** below operations must be checked with similar types and types of different
precision:
*** comparison
*** arithmetic
** check conversion between different types (aka CAST operator)
*** for conversion from character string to temporal type check conversion
from all allowed formats
*** for conversion to character string check that result satisfies the format
described in SQL standard
** check built-in function
*** make sure all required by SQL standard function are presented and work as
expected
was:
This is an umbrella ticket to keep track of all work related to productization
of temporal types.
The first phase is to review existing test coverage according to a test plan
(presented below) and add absent tests. The goal is to identify all issues
related to a temporal types. All found problems (as well as already filed ones)
must be linked to this epic.
Second phase will include fixing all attached issues, as well as amending
documentation with known limitation in case of problem that we are not going to
fix in the nearest future (for instance, a type `TIME WITH TIME ZONE` is not
supported and we have no plan to support it any time soon, therefor this must
be mentioned as known limitation).
Note: phases not necessary should be executed sequentially; critical issues may
be fixed asap.
A temporal types hierarchy is as follow:
* All temporal types
** Datetime types
*** DATE
*** TIME [WITHOUT TIME ZONE]
*** TIME WITH TIME ZONE // not supported; known limitation
*** TIMESTAMP [WITHOUT TIME ZONE]
*** TIMESTAMP WITH TIME ZONE // not supported; known limitation
*** TIMESTAMP WITH LOCAL TIME ZONE // not defined by SQL standard; extension
** Interval types
*** YEAR TO MONTH intervals
*** DAY TO SECOND intervals
Test plan is as follow:
* For all temporal types check different values (literals, dyn params, table
columns):
** check boundaries
** check different precisions for fraction of second
** for datetime types check leap year/month/second
** for literals check supported formats
** for table columns check support for defaults; boundaries check; different
precision for fraction of second
** for table columns check support in indexes (both SORTED and HASH)
* For all temporal types check operations:
** check type coercion for all allowed operations
** below operations must be checked with similar types and types of different
precision:
*** comparison
*** arithmetic
** check conversion between different types (aka CAST operator)
*** for conversion from character string to temporal type check conversion
from all allowed formats
*** for conversion to character string check that result satisfies the format
described in SQL standard
** check built-in function
*** make sure all required by SQL standard function are presented and work as
expected
> Productization of Temporal Types
> --------------------------------
>
> Key: IGNITE-24676
> URL: https://issues.apache.org/jira/browse/IGNITE-24676
> Project: Ignite
> Issue Type: Epic
> Components: sql
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> This is an umbrella ticket to keep track of all work related to
> productization of temporal types.
> The first phase is to review existing test coverage according to a test plan
> (presented below) and add absent tests. The goal is to identify all issues
> related to a temporal types. All found problems (as well as already filed
> ones) must be linked to this epic.
> Second phase will include fixing all attached issues, as well as amending
> documentation with known limitation in case of problem that we are not going
> to fix in the nearest future (for instance, a type `TIME WITH TIME ZONE` is
> not supported and we have no plan to support it any time soon, therefor this
> must be mentioned as known limitation).
> Note: phases not necessary should be executed sequentially; critical issues
> may be fixed asap.
> A temporal types hierarchy is as follow:
> * All temporal types
> ** Datetime types
> *** DATE
> *** TIME [WITHOUT TIME ZONE]
> *** TIME WITH TIME ZONE // not supported; known limitation
> *** TIME WITH LOCAL TIME ZONE // not supported; known limitation
> *** TIMESTAMP [WITHOUT TIME ZONE]
> *** TIMESTAMP WITH TIME ZONE // not supported; known limitation
> *** TIMESTAMP WITH LOCAL TIME ZONE // not defined by SQL standard; extension
> ** Interval types
> *** YEAR TO MONTH intervals
> *** DAY TO SECOND intervals
> Test plan is as follow:
> * For all temporal types check different values (literals, dyn params, table
> columns):
> ** check boundaries
> ** check different precisions for fraction of second
> ** for datetime types check leap year/month/second
> ** for literals check supported formats
> ** for table columns check support for defaults; boundaries check; different
> precision for fraction of second
> ** for table columns check support in indexes (both SORTED and HASH)
> * For all temporal types check operations:
> ** check type coercion for all allowed operations
> ** below operations must be checked with similar types and types of
> different precision:
> *** comparison
> *** arithmetic
> ** check conversion between different types (aka CAST operator)
> *** for conversion from character string to temporal type check conversion
> from all allowed formats
> *** for conversion to character string check that result satisfies the
> format described in SQL standard
> ** check built-in function
> *** make sure all required by SQL standard function are presented and work
> as expected
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
