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

[SPARK-29947][SQL][FOLLOWUP] Fix table lookup cache #27341

Closed
wants to merge 1 commit into from

Conversation

cloud-fan
Copy link
Contributor

What changes were proposed in this pull request?

Fix a bug in #26589 , to make this feature work.

Why are the changes needed?

This feature doesn't work actually.

Does this PR introduce any user-facing change?

no

How was this patch tested?

new test

@cloud-fan
Copy link
Contributor Author

@SparkQA
Copy link

SparkQA commented Jan 23, 2020

Test build #117304 has finished for PR 27341 at commit 86a3d81.

  • This patch fails SparkR unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

import org.apache.spark.sql.internal.SQLConf
import org.apache.spark.sql.types._

class TableLookupCacheSuite extends AnalysisTest with Matchers {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for adding this test suite, @cloud-fan .

@dongjoon-hyun dongjoon-hyun changed the title [SPARK-29947][SQL] table lookup cache [SPARK-29947][SQL][FOLLOWUP] Fix table lookup cache Jan 23, 2020
Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM. The test suite is very useful for validation. Thanks.
Merged to master.

All test passed. The R failure is a known incoming feasibility check flakiness. cc @viirya

* checking CRAN incoming feasibility ...Error in .check_package_CRAN_incoming(pkgdir) : 
  dims [product 26] do not match the length of object [0]

@viirya
Copy link
Member

viirya commented Jan 23, 2020

hmm, is CRAN failure still there now? I got their reply that was fixed. This failure looks like 5hrs ago. If there is new failure, please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants