Github user concretevitamin commented on a diff in the pull request:
https://github.com/apache/spark/pull/956#discussion_r13577888
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -269,6 +271,22 @@ class SQLContext(@transient val sparkContext:
SparkContext)
protected abstract class QueryExecution {
def logical: LogicalPlan
+ def eagerlyProcess(plan: LogicalPlan): RDD[Row] = plan match {
+ case SetCommand(key, value) =>
--- End diff --
Hey @liancheng -- so this function `eagerlyProcess` is supposed to be
triggered as soon as `hql("set ...")` is typed in / is being evaluated. The
actual physical operator `SetCommandPhysical` handles evaluating the *actual
contents of the SchemaRDD*. These contents are not (and need not be, in the
spirit of RDDs) eagerly processed at this particular place.
---
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.
---
