yaooqinn opened a new pull request #28197: [SPARK-31431][SQL] Add 
CalendarInterval encoder support
URL: https://github.com/apache/spark/pull/28197
 
 
   
   
   ### What changes were proposed in this pull request?
   
   CalenderInterval is available to be converted to/from internal Spark SQL 
representation when it is a member of a Scala's product type e.g tuples/ case 
class etc but not as a primitive type
   
   In this PR, we add a new seder rules to map CalenderInterval to 
CalenderIntervalType directly.
   
   ### Why are the changes needed?
   
   improve CalenderInterval
   
   
   ### Does this PR introduce any user-facing change?
   <!--
   If yes, please clarify the previous behavior and the change this PR proposes 
- provide the console output, description and/or an example to show the 
behavior difference if possible.
   If no, write 'No'.
   -->
   
   yes, CalenderInterval are now can be implicitly converted to 
Dataset/DataFame without being wrapped as scala Products
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some 
test cases that check the changes thoroughly including negative and positive 
cases if possible.
   If it was tested in a way different from regular unit tests, please clarify 
how you tested step by step, ideally copy and paste-able, so that other 
reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why 
it was difficult to add.
   -->
   
   add new tests

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to