[SQL][DOC] Minor document fix in HadoopFsRelationProvider

Jacky Li · rxin · commit 972d8900a1e2 · 2015-07-19T23:19:17.000-07:00
Catch this while reading the code Author: Jacky Li <lee.unreal@gmail.com> Author: Jacky Li <jackylk@users.noreply.github.com> Closes apache#7524 from jackylk/patch-11 and squashes the following commits: b679011 [Jacky Li] fix doc e10e211 [Jacky Li] [SQL] Minor document fix in HadoopFsRelationProvider
diff --git a/sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala b/sql/core/src/main/scala/org/apache/spark/sql/sources/interfaces.scala
@@ -75,7 +75,7 @@ trait RelationProvider {
  * A new instance of this class with be instantiated each time a DDL call is made.
  *
  * The difference between a [[RelationProvider]] and a [[SchemaRelationProvider]] is that
- * users need to provide a schema when using a SchemaRelationProvider.
+ * users need to provide a schema when using a [[SchemaRelationProvider]].
  * A relation provider can inherits both [[RelationProvider]] and [[SchemaRelationProvider]]
  * if it can support both schema inference and user-specified schemas.
  *
@@ -111,7 +111,7 @@ trait SchemaRelationProvider {
  *
  * The difference between a [[RelationProvider]] and a [[HadoopFsRelationProvider]] is
  * that users need to provide a schema and a (possibly empty) list of partition columns when
- * using a SchemaRelationProvider. A relation provider can inherits both [[RelationProvider]],
+ * using a [[HadoopFsRelationProvider]]. A relation provider can inherits both [[RelationProvider]],
  * and [[HadoopFsRelationProvider]] if it can support schema inference, user-specified
  * schemas, and accessing partitioned relations.
  *

Original file line number	Diff line number	Diff line change
`@@ -75,7 +75,7 @@ trait RelationProvider {`
`75`	`75`	`* A new instance of this class with be instantiated each time a DDL call is made.`
`76`	`76`	`*`
`77`	`77`	`* The difference between a [[RelationProvider]] and a [[SchemaRelationProvider]] is that`
`78`		`- * users need to provide a schema when using a SchemaRelationProvider.`
	`78`	`+ * users need to provide a schema when using a [[SchemaRelationProvider]].`
`79`	`79`	`* A relation provider can inherits both [[RelationProvider]] and [[SchemaRelationProvider]]`
`80`	`80`	`* if it can support both schema inference and user-specified schemas.`
`81`	`81`	`*`
`@@ -111,7 +111,7 @@ trait SchemaRelationProvider {`
`111`	`111`	`*`
`112`	`112`	`* The difference between a [[RelationProvider]] and a [[HadoopFsRelationProvider]] is`
`113`	`113`	`* that users need to provide a schema and a (possibly empty) list of partition columns when`
`114`		`- * using a SchemaRelationProvider. A relation provider can inherits both [[RelationProvider]],`
	`114`	`+ * using a [[HadoopFsRelationProvider]]. A relation provider can inherits both [[RelationProvider]],`
`115`	`115`	`* and [[HadoopFsRelationProvider]] if it can support schema inference, user-specified`
`116`	`116`	`* schemas, and accessing partitioned relations.`
`117`	`117`	`*`