[
https://issues.apache.org/jira/browse/IGNITE-29045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119964#comment-18119964
]
Ignite TC Bot commented on IGNITE-29045:
----------------------------------------
Calcite SQL: Added support for Java temporal types in user-defined function and
table function parameters and results.
The Release Note field has been filled with the wording above. Please review it
and edit it if needed.
> SQL Calcite: Support Java temporal types in UDF and UDTF parameters and
> results
> -------------------------------------------------------------------------------
>
> Key: IGNITE-29045
> URL: https://issues.apache.org/jira/browse/IGNITE-29045
> Project: Ignite
> Issue Type: Bug
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: calcite, ignite-2, sql
> Fix For: 2.19
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> Java UDFs and UDTFs using temporal types fail because some {{java.time}}
> types are mapped to {{{}OTHER{}}}, and SQL temporal values are represented
> internally as {{{}Integer{}}}/{{{}Long{}}} without consistent conversion at
> the function boundary.
> Add SQL type mapping and bidirectional conversion for JDBC temporal types,
> {{{}java.util.Date{}}}, {{{}LocalDate{}}}, {{{}LocalTime{}}},
> {{{}LocalDateTime{}}}, {{{}Duration{}}}, and {{Period}} in UDF and UDTF
> parameters and results. User-defined functions should use Java temporal types
> without depending on Calcite’s internal representation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
