Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FOLLOW-UP][SPARK-26065][SQL] Fix the Failure when having two Consecutive Hints #23501

Closed
wants to merge 1 commit into from

Conversation

maryannxue
Copy link
Contributor

What changes were proposed in this pull request?

This is to fix a bug in #23036, which would lead to an exception in case of two consecutive hints.

How was this patch tested?

Added a new test.

@dongjoon-hyun
Copy link
Member

dongjoon-hyun commented Jan 9, 2019

Hi, @maryannxue .
Although this is Spark 3.0 only change, could you file a new SPARK JIRA issue, please?
Also, please update the title. The title of followup PRs have better describe their own commit contents.

@gatorsmile gatorsmile changed the title [FOLLOW-UP][SPARK-26065][SQL] Change query hint from a LogicalPlan to a field [FOLLOW-UP][SPARK-26065][SQL] Fix the Failure when having two Consecutive Hints Jan 9, 2019
@gatorsmile
Copy link
Member

I updated the title. Thanks! Merged to master.

@SparkQA
Copy link

SparkQA commented Jan 9, 2019

Test build #100985 has finished for PR 23501 at commit a30c0bd.

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

@asfgit asfgit closed this in 2d01bcc Jan 9, 2019
jackylee-ch pushed a commit to jackylee-ch/spark that referenced this pull request Feb 18, 2019
…tive Hints

## What changes were proposed in this pull request?

This is to fix a bug in apache#23036, which would lead to an exception in case of two consecutive hints.

## How was this patch tested?

Added a new test.

Closes apache#23501 from maryannxue/query-hint-followup.

Authored-by: maryannxue <maryannxue@apache.org>
Signed-off-by: gatorsmile <gatorsmile@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants