Skip to content

[SPARK-15211][SQL] Select features column from LibSVMRelation causes failure - #12986

Closed
viirya wants to merge 1 commit into
apache:masterfrom
viirya:fix-libsvmrelation
Closed

[SPARK-15211][SQL] Select features column from LibSVMRelation causes failure#12986
viirya wants to merge 1 commit into
apache:masterfrom
viirya:fix-libsvmrelation

Conversation

@viirya

Copy link
Copy Markdown
Member

What changes were proposed in this pull request?

We need to use requiredSchema in LibSVMRelation to project the fetch required columns when loading data from this data source. Otherwise, when users try to select features column, it will cause failure.

How was this patch tested?

LibSVMRelationSuite.

@SparkQA

Copy link
Copy Markdown

Test build #58099 has finished for PR 12986 at commit f15e461.

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

@viirya

Copy link
Copy Markdown
MemberAuthor

ping @liancheng@yhuai Please take a look of this. Thanks.

@liancheng

Copy link
Copy Markdown
Contributor

LGTM. This bug was introduced in #12866. Thanks for fixing this! I'm merging it to master and branch-2.0.

asfgit pushed a commit that referenced this pull request May 9, 2016
…failure
## What changes were proposed in this pull request?
We need to use `requiredSchema` in `LibSVMRelation` to project the fetch required columns when loading data from this data source. Otherwise, when users try to select `features` column, it will cause failure.
## How was this patch tested?
`LibSVMRelationSuite`.
Author: Liang-Chi Hsieh <simonh@tw.ibm.com>
Closes#12986 from viirya/fix-libsvmrelation.
(cherry picked from commit 635ef40)
Signed-off-by: Cheng Lian <lian@databricks.com>
@asfgitasfgit closed this in 635ef40May 9, 2016
@viirya
viirya deleted the fix-libsvmrelation branch December 27, 2023 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@viirya@SparkQA@liancheng