Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18080
I think that if Spark's behavior matches Hive's, that's what we want here.
Other variations can be implemented in UDFs, which provide all the flexibility
you'd want. These functions exist in all
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18080
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18080
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18080
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18080
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user setjet commented on the issue:
https://github.com/apache/spark/pull/18080
This variant is available in other DB's, albeit with slightly different
function and parameter naming. For example, MySQL allows it via the `week()`
function:
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18080
Is this variant available in any other DB? A lot of the goal of providing
built-in functions is compatibility. Beyond that a lot of things are better
handled with UDFs for special cases, not new
Github user setjet commented on the issue:
https://github.com/apache/spark/pull/18080
I agree that we shouldn't change the behavior, hence I suggested we could
do it the other way around: make a new function for gregorian instead and
leave weekofyear as is.
I suppose we
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18080
I don't think you can just change the behavior. It would possibly break
apps and I presume no longer matches Hive. If it already implements a standard
too, it sounds like it is correct. A second
Github user setjet commented on the issue:
https://github.com/apache/spark/pull/18080
Coming to think of it, it might actually be better to switch it around:
have ISO8601 as function weekofyear, and make a separate function for gregorian
because ISO is more of a commonly used term.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18080
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
11 matches
Mail list logo
