GideonPotok commented on PR #46597:
URL: https://github.com/apache/spark/pull/46597#issuecomment-2119215757

   > I wouldn't say there's a preference on whether to include both support for 
string type and complex types within the same PR - if you think that the 
changes might end up being too large, then it's fine to split it into separate 
PRs.
   > 
   > 
   > 
   > However I would say that we need to make sure there's no unexpected 
behaviour - for example, MODE shouldn't have correct support for collated 
StringType, but incorrect behaviour for ArrayType(StringType), 
StructType(...StringType...), etc.
   > 
   > 
   > 
   > With that in mind, it seems that we should adopt one of two approaches:
   > 
   > 
   > 
   > - implement the support for collated StringType in this PR, but fail 
(throw exception) for complex types that have collated strings
   > 
   > - implement full support at once
   
   @uros-db if you are fine with me splitting it into two PRs, that's what I 
will do! I will modify this PR to fail for complex types that have collated 
strings. And I will get the PR to implement full (recursive) support for said 
complex types ready to be reviewed right after this one is merged. I appreciate 
your flexibility!


-- 
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.

To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to