spark-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vanzin <...@git.apache.org>
Subject [GitHub] spark issue #20169: [SPARK-17088][hive] Fix 'sharesHadoopClasses' option whe...
Date Wed, 24 Jan 2018 18:29:36 GMT
Github user vanzin commented on the issue:

    https://github.com/apache/spark/pull/20169
  
    > That is why I suggested above to ping me and @cloud-fan when the community does the
change in Spark SQL.
    
    The point I'm making (and I believe Hyukjin too) is that it should be the opposite. If
you want to be involved in all these reviews, it's up to you to monitor what's going on. A
new contributor, for example, cannot know who to ping when he wants to make a change.
    
    And I hope you see how "x and y must be pinged in any SQL review" goes against the idea
that the project is owned by all committers, not just a few of them.


---

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


Mime
View raw message