Github user liancheng commented on the pull request:

    https://github.com/apache/spark/pull/948#issuecomment-45046324
  
    @marmbrus Agree. I'll try to remove the `lazy` qualifier of 
`SchemaRDD.queryExecution` since the field object itself is rather cheap (all 
of its fields are lazy), and then call the `process()` method in 
`QueryExecution` constructor to evaluate native commands eagerly.
    
    @concretevitamin `InsertIntoHiveTable` and `InsertIntoParquetTable` are 
physical operations, which are parts of physical plans. However, we only need 
to take care of logical plan here. `InsertIntoTable` and 
`InsertIntoCreatedTable` are translated into those physical operators after 
logical plan optimization.


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to