Github user vanzin commented on the issue:

    https://github.com/apache/spark/pull/20601
  
    I'm trying to think of a way that we can avoid these issues going forward - 
not that I expect this code to change much. Maybe have a unit test that makes 
sure all declared header constants are mapped to some index, or something like 
that, and fails if you add a new header constant without a mapping.


---

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

Reply via email to