Uh oh!
There was an error while loading. Please reload this page.
[SPARK-11622][MLLIB] Make LibSVMRelation extends HadoopFsRelation and… - #9595
[SPARK-11622][MLLIB] Make LibSVMRelation extends HadoopFsRelation and…#9595zjffdu wants to merge 9 commits into
Conversation
SparkQA
commented
Nov 10, 2015
Test build #45516 has finished for PR 9595 at commit
|
mengxr
commented
Nov 10, 2015
cc @Lewuathe |
There was a problem hiding this comment.
Is it really necessary to mixin Logging trait here? HadoopFsRelation already does it.
SparkQA
commented
Nov 11, 2015
Test build #45593 has finished for PR 9595 at commit
|
zjffdu
commented
Dec 1, 2015
@Lewuathe Would you mind help review this ? Thanks |
There was a problem hiding this comment.
Is it necessary to change to under score? We can keep this.
import org.apache.spark.sql.{DataFrameReader, DataFrame, Row, SQLContext}
SparkQA
commented
Dec 1, 2015
Test build #46952 has finished for PR 9595 at commit
|
Lewuathe
commented
Dec 2, 2015
@zjffdu LGTM. Could you create another JIRA for supporting multiple input path on |
zjffdu
commented
Dec 2, 2015
Sure, create SPARK-12086 for that |
There was a problem hiding this comment.
chop down arguments and use 4-space indentation
mengxr
commented
Jan 19, 2016
@zjffdu Sorry for the delay! I made a pass and left some comments inline. You also need to rebase master to resolve conflicts. Please let me know whether you have time to update this PR. Btw, another follow-up work would be exposing options to format the output values. Now we use default format, which outputs 16 digits per double value. It might be too long for common use cases. Could you create a JIRA for this? Thanks! |
zjffdu
commented
Jan 20, 2016
Thanks @mengxr for review, will update the patch and create a followup jira. |
There was a problem hiding this comment.
This is bug of test code, I am verifying df rather than df2 so that the test passed
SparkQA
commented
Jan 20, 2016
Test build #49797 has finished for PR 9595 at commit
|
zjffdu
commented
Jan 20, 2016
It's weird that I pass the scala style check in my local box. |
There was a problem hiding this comment.
I didn't know we are checking the ordering of imports now. F should come before P. You can use Scala Import Organizer with IntelliJ to organize imports quickly.
zjffdu
commented
Jan 20, 2016
@mengxr any way to retrigger the build ? BTW what do you mean "exposing options to format the output values", is there a new feature of Spark for encoding double using compact way ? I may miss something here. |
mengxr
commented
Jan 20, 2016
test this please |
mengxr
commented
Jan 20, 2016
LIBSVM is a text format and hence we need to consider the cost of storing numerical values. In the current implementation, the output could be some text like |
mengxr
commented
Jan 20, 2016
test this please |
SparkQA
commented
Jan 20, 2016
Test build #49813 has finished for PR 9595 at commit
|
SparkQA
commented
Jan 20, 2016
Test build #49814 has finished for PR 9595 at commit
|
zjffdu
commented
Jan 20, 2016
Thanks for clarifying. In that case, we may lose precision when reading. Maybe make it for libsvm specific is better, anyway we can discuss it in the jira. |
There was a problem hiding this comment.
{ should come before l. Please try Scala Import Organizer:) This is what I got:
importjava.io.IOExceptionimportcom.google.common.base.Objectsimportorg.apache.hadoop.fs.{FileStatus, Path}
importorg.apache.hadoop.io.{NullWritable, Text}
importorg.apache.hadoop.mapreduce.{RecordWriter, TaskAttemptContext}
importorg.apache.hadoop.mapreduce.lib.output.TextOutputFormatimportorg.apache.spark.annotation.Sinceimportorg.apache.spark.mllib.linalg.{Vector, VectorUDT}
importorg.apache.spark.mllib.util.MLUtilsimportorg.apache.spark.rdd.RDDimportorg.apache.spark.sql.{DataFrame, DataFrameReader, Row, SQLContext}
importorg.apache.spark.sql.sources._importorg.apache.spark.sql.types._SparkQA
commented
Jan 20, 2016
Test build #49822 has finished for PR 9595 at commit
|
zjffdu
commented
Jan 21, 2016
test this please |
SparkQA
commented
Jan 21, 2016
Test build #49831 has finished for PR 9595 at commit
|
SparkQA
commented
Jan 21, 2016
Test build #49851 has finished for PR 9595 at commit
|
SparkQA
commented
Jan 21, 2016
Test build #49853 has finished for PR 9595 at commit
|
SparkQA
commented
Jan 21, 2016
Test build #49857 has finished for PR 9595 at commit
|
mengxr
commented
Jan 25, 2016
test this please |
SparkQA
commented
Jan 25, 2016
Test build #50007 has finished for PR 9595 at commit
|
zjffdu
commented
Jan 25, 2016
Thanks @mengxr. Not sure why the test fails. Will take a look at it when I have time. |
mengxr
commented
Jan 25, 2016
The failed test is irrelevant to this PR, which is tracked here: https://issues.apache.org/jira/browse/SPARK-10086. I will ask Jenkins to make another try. |
mengxr
commented
Jan 25, 2016
test this please |
SparkQA
commented
Jan 26, 2016
Test build #50032 has finished for PR 9595 at commit
|
mengxr
commented
Jan 26, 2016
Let's wait for #10909 first. |
mengxr
commented
Jan 26, 2016
test this please |
SparkQA
commented
Jan 26, 2016
Test build #50078 has finished for PR 9595 at commit
|
mengxr
commented
Jan 27, 2016
LGTM. Merged into master. Thanks! |
… Add LibSVMOutputWriter
The behavior of LibSVMRelation is not changed except adding LibSVMOutputWriter