Github user srowen commented on the issue:

    https://github.com/apache/spark/pull/22099
  
    To be clear you think this passed because it still uses jets3t and that 
still brings in BC? Then we can maybe merge this and rebase the other change to 
find out. This update won't have changed that situation with strong crypto 
being required right?


---

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

Reply via email to