Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/1663#discussion_r15604802
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/util/MLUtils.scala ---
@@ -102,36 +100,14 @@ object MLUtils {
// Convenient methods for `loadLibSVMFile`.
- /**
- * Loads labeled data in the LIBSVM format into an RDD[LabeledPoint].
- * The LIBSVM format is a text-based format used by LIBSVM and LIBLINEAR.
- * Each line represents a labeled sparse feature vector using the
following format:
- * {{{label index1:value1 index2:value2 ...}}}
- * where the indices are one-based and in ascending order.
- * This method parses each line into a
[[org.apache.spark.mllib.regression.LabeledPoint]],
- * where the feature indices are converted to zero-based.
- *
- * @param sc Spark context
- * @param path file or directory path in any Hadoop-supported file
system URI
- * @param multiclass whether the input labels contain more than two
classes. If false, any label
- * with value greater than 0.5 will be mapped to 1.0,
or 0.0 otherwise. So it
- * works for both +1/-1 and 1/0 cases. If true, the
double value parsed directly
- * from the label string will be used as the label
value.
- * @param numFeatures number of features, which will be determined from
the input data if a
- * nonpositive value is given. This is useful when
the dataset is already split
- * into multiple files and you want to load them
separately, because some
- * features may not present in certain files, which
leads to inconsistent
- * feature dimensions.
- * @param minPartitions min number of partitions
- * @return labeled data stored as an RDD[LabeledPoint]
- */
- def loadLibSVMFile(
+ @deprecated("use method without multiclass argument, which no longer has
effect")
--- End diff --
minor: We can add the deprecated version to `@deprecated`, if you need to
update the PR for some other reasons.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
