Mailing-List: contact reviews-help@spark.apache.org; run by ezmlm
Precedence: bulk
From: gatorsmile <git@git.apache.org>
To: reviews@spark.apache.org
Reply-To: reviews@spark.apache.org
References: <git-pr-17353-spark@git.apache.org>
In-Reply-To: <git-pr-17353-spark@git.apache.org>
Subject: [GitHub] spark issue #17353: [SPARK-17080][SQL][FOLLOWUP] Improve documentation and n...
Content-Type: text/plain
Message-Id: <20170320062841.C29BADFD9E@git1-us-west.apache.org>
Date: Mon, 20 Mar 2017 06:28:41 +0000 (UTC)
archived-at: Mon, 20 Mar 2017 06:28:44 -0000

Github user gatorsmile commented on the issue:

    https://github.com/apache/spark/pull/17353
  
    Does it make sense to introduce some counts to decide how many new JoinPlan we build?
    
    We can find out what we pruned in the search. It can easy for us to ensure no regression happened when we improve the codes in the future.


---
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