From 88d9c04fea04d32377aa5f79451c67dca9427a3a Mon Sep 17 00:00:00 2001 From: Daniel Tenedorio Date: Wed, 8 Jan 2025 14:47:14 -0800 Subject: [PATCH] update docs --- .../apache/spark/sql/catalyst/expressions/pipeOperators.scala | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/pipeOperators.scala b/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/pipeOperators.scala index b6e8df405f21d..40d7d24263a78 100644 --- a/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/pipeOperators.scala +++ b/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/pipeOperators.scala @@ -63,9 +63,7 @@ case class PipeExpression(child: Expression, isAggregate: Boolean, clause: Strin /** * Represents the location within a logical plan that a SQL pipe operator appeared. * This acts as a logical boundary that works to prevent the analyzer from modifying the logical - * operators above and below the boundary. For example, when adding a Filter operator after a - * Project to implement the "|> WHERE" operator, the analyzer might otherwise push the Filter below - * the project; this class prevents that by acting as a logical boundary. + * operators above and below the boundary. */ case class PipeOperator(child: LogicalPlan) extends UnaryNode { final override val nodePatterns: Seq[TreePattern] = Seq(PIPE_OPERATOR)