Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/21679
For your information, @cloud-fan and I are discussing how we expose
calendar interval data types. Will post the proposal later.
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/21679
I think we should close this for now then.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21679
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/21679
I would better open a discussion thread in the mailing list before making a
PR to expose it. Shell we leave this close this meanwhile? I think it's better
to leave active and actionable PRs
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21679
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user priyankagargnitk commented on the issue:
https://github.com/apache/spark/pull/21679
What if i make changes to expose it?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/21679
Yea, so it's kind of half public now but not completely exposed. It should
be exposed before we extend its support.
---
-
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/21679
Actually, the unsafe package does not include user-facing classes.
---
-
To unsubscribe, e-mail:
Github user priyankagargnitk commented on the issue:
https://github.com/apache/spark/pull/21679
org.apache.spark.unsafe.types.CalenderInterval is already public, am i
missing something.
Also, what if i want to do some computation on any data type and return
Calender Interval..
