HeartSaVioR commented on PR #36038: URL: https://github.com/apache/spark/pull/36038#issuecomment-1086968356
I see review comments about the doc which seem to be just copied from Scala/Java API doc. Since this PR focuses mainly to deal with feature parity, how about simply allowing copy-paste doc from Scala/Java API doc (with additional content if something only applies to PySpark), and having another PR fixing both Scala/Java and PySpark doc altogether after this has merged? The doc for Scala/Java API has been served for years and personally I'd consider commenting on the doc as proposing changes on "existing doc" instead of new doc, since the doc change here should trigger the change on Scala/Java doc to be in sync, effectively making changes on existing doc. Does it make sense for everyone? -- 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
