Github user ericl commented on the issue:

    https://github.com/apache/spark/pull/14690
  
    Ok, take care!
    
    Just as a fyi, on our side we're investigating similar pruning support for
    Datasource tables, likely building on top of this work. The eventual goal
    is to have scalable and performant partition handling in Spark 2.1 for both
    Hive (converted) and native Datasource tables.
    
    On Fri, Sep 23, 2016, 2:06 AM Michael Allman <notificati...@github.com>
    wrote:
    
    > FYI I'll be mostly away the rest of this week and off the grid entirely
    > next week.
    >
    > I've continued to work on this patch on my side. Like I wrote earlier,
    > I've been awaiting the outcome of #14750
    > <https://github.com/apache/spark/pull/14750> before moving forward here.
    > However, I might proceed assuming the absence of that PR. It looks like it
    > may yet be some time before it's resolved either way. I'll see how things
    > look when I get back on the third.
    >
    > —
    > You are receiving this because you were mentioned.
    > Reply to this email directly, view it on GitHub
    > <https://github.com/apache/spark/pull/14690#issuecomment-249110309>, or 
mute
    > the thread
    > 
<https://github.com/notifications/unsubscribe-auth/AAA6Sos_o7oE_xVZ1weczGm_cFfNrq82ks5qs2xMgaJpZM4Jmu92>
    > .
    >



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Reply via email to