Github user hvanhovell commented on a diff in the pull request: https://github.com/apache/spark/pull/15363#discussion_r105023151 --- Diff: sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/planning/patterns.scala --- @@ -257,3 +258,28 @@ object PhysicalAggregation { case _ => None } } + +/** + * A pattern that matches a base table access and collects the + * the corresponding leaf node and the applied predicates. + * A base table access represents a LeafNode, or a Project or Filter operators + * above a LeafNode. + */ +object BaseTableAccess extends PredicateHelper { + def unapply(plan: LogicalPlan): Option[(LogicalPlan, Seq[Expression])] = plan match { --- End diff -- Is this the same a `PhysicalOperation`? Or, better question, what is the difference?
--- 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