MaxGekk commented on issue #26092: [SPARK-29440][SQL] Support
java.time.Duration as an external type of CalendarIntervalType
URL: https://github.com/apache/spark/pull/26092#issuecomment-542830994
I am closing this since there is no consensus.
MaxGekk commented on issue #26092: [SPARK-29440][SQL] Support
java.time.Duration as an external type of CalendarIntervalType
URL: https://github.com/apache/spark/pull/26092#issuecomment-542375895
> I don't think we can map CalendarInterval to Duration as it's kind of a
truncation.
MaxGekk commented on issue #26092: [SPARK-29440][SQL] Support
java.time.Duration as an external type of CalendarIntervalType
URL: https://github.com/apache/spark/pull/26092#issuecomment-541461757
> What would this do in Pyspark?
I would use `timedelta` -
MaxGekk commented on issue #26092: [SPARK-29440][SQL] Support
java.time.Duration as an external type of CalendarIntervalType
URL: https://github.com/apache/spark/pull/26092#issuecomment-541450210
@cloud-fan @srowen @dongjoon-hyun @HyukjinKwon WDYT?
MaxGekk commented on issue #26092: [SPARK-29440][SQL] Support
java.time.Duration as an external type of CalendarIntervalType
URL: https://github.com/apache/spark/pull/26092#issuecomment-541331411
I think this should be hidden under a flag. For example,
MaxGekk commented on issue #26092: [SPARK-29440][SQL] Support
java.time.Duration as an external type of CalendarIntervalType
URL: https://github.com/apache/spark/pull/26092#issuecomment-541277110
jenkins, retest this, please
MaxGekk commented on issue #26092: [SPARK-29440][SQL] Support
java.time.Duration as an external type of CalendarIntervalType
URL: https://github.com/apache/spark/pull/26092#issuecomment-541276742
> ... should be determined by the current date.
@hvanhovell Strictly speaking, it
MaxGekk commented on issue #26092: [SPARK-29440][SQL] Support
java.time.Duration as an external type of CalendarIntervalType
URL: https://github.com/apache/spark/pull/26092#issuecomment-541086770
ping @cloud-fan @hvanhovell
