[GitHub] spark issue #17744: [SPARK-20426] Lazy initialization of FileSegmentManagedB...

[jinxing64 <gi...@git.apache.org>]

Github user jinxing64 commented on the issue:

    https://github.com/apache/spark/pull/17744
  
    @tgravescs 
    Thanks a lot for merging.
    I proposed to resolve this by "Lazy initialization of FileSegmentManagedBuffer" and simplify the change. But after checking the code, could we remove `OpenBlocks`. In my understanding, `OpenBlocks` is just a handshake before fetching remote blocks and could be removed conceptually(did I miss something?). This is just a brainstorming and will be a bigger change.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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