[SPARK-8841] [SQL] Fix partition pruning percentage log message

[srlindemann]

When pruning partitions for a query plan, a message is logged indicating what how many partitions were selected based on predicate criteria, and what percent were pruned.

The current release erroneously uses 1 - total/selected to compute this quantity, leading to nonsense messages like "pruned -1000% partitions". The fix is simple and obvious.

[AmplabJenkins]

Can one of the admins verify this patch?

[squito]

Jenkins, ok to test

[squito]

lgtm

[rxin]

Jenkins, test this please.

(Did something go wrong with Jenkins?)

[rxin]

cc @liancheng

[liancheng]

ok to test

[AmplabJenkins]

Merged build triggered.

[liancheng]

@srlindemann Thanks for fixing this! Could you please file a JIRA and change the PR title to "[SPARK-xxxx] [SQL] Fix partition pruning percentage log message"?

[srowen]

Is this even worth a JIRA? there is virtually no difference between the description and fix

[AmplabJenkins]

Merged build started.

[SparkQA]

Test build #36567 has started for PR 7227 at commit c788061.

[SparkQA]

Test build #36567 has finished for PR 7227 at commit c788061.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[AmplabJenkins]

Merged build finished. Test PASSed.

[srlindemann]

I saw on one of the contrib pages that trivial changes might not have a
JIRA, so I skipped it here. Happy to do it though if you like.
On Jul 6, 2015 4:38 AM, "Sean Owen" [email protected] wrote:

Is this even worth a JIRA? there is virtually no difference between the
description and fix

—
Reply to this email directly or view it on GitHub
#7227 (comment).

[liancheng]

@srowen Hm, yeah, now I'd agree that this might not worth a JIRA. Anyway, filing one to track it does no harm :)

@srlindemann Thanks! Merging to master.