Github user foxish commented on the issue:

    https://github.com/apache/spark/pull/21032
  
    Yes, that is what I was indicating as well. We should have a design for all
    different volume types. Extending this PR as the design evolves is a good
    way to go about that.
    
    On Thu, Apr 12, 2018, 11:37 AM Yinan Li <notificati...@github.com> wrote:
    
    > I think we should have a more general solution so it works for other types
    > of volumes. Particularly, we should have a design discussion on the format
    > of values of such a property so it works for any type of volumes. I 
suggest
    > we hold on on this PR until we setup a general solution. @foxish
    > <https://github.com/foxish> @felixcheung <https://github.com/felixcheung>
    > .
    >
    > —
    > You are receiving this because you were mentioned.
    > Reply to this email directly, view it on GitHub
    > <https://github.com/apache/spark/pull/21032#issuecomment-380903531>, or 
mute
    > the thread
    > 
<https://github.com/notifications/unsubscribe-auth/AA3U51kqvGuyzur2h9KXvBYaWcZU6ME5ks5tn571gaJpZM4TOyZd>
    > .
    >



---

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

Reply via email to