[CARBONDATA-479] Guarantee consistency for keyword LOCAL and file path in data loading command

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Lionx
• Created: 01/Dec/16 14:22
• Updated: 16/Jan/17 17:39

Description

In CarbonSqlParser.scala,
protected lazy val loadDataNew: Parser[LogicalPlan] =
LOAD ~> DATA ~> opt(LOCAL) ~> INPATH ~> stringLit ~ opt(OVERWRITE) ~
(INTO _{> TABLE ~> (ident <} ".").? ~ ident) ~
(OPTIONS _{> "(" ~> repsep(loadOptions, ",") <} ")").? <~ opt(";") ^^ {
case filePath ~ isOverwrite ~ table ~ optionsList =>
val (databaseNameOp, tableName) = table match

{ case databaseName ~ tableName => (databaseName, tableName.toLowerCase()) }

if (optionsList.isDefined)

{ validateOptions(optionsList) }

val optionsMap = optionsList.getOrElse(List.empty[(String, String)]).toMap
LoadTable(databaseNameOp, tableName, filePath, Seq(), optionsMap,
isOverwrite.isDefined)
}

It seems that using Keyword LOCAL impacts noting. Loading data from hdfs or file just depends on the path.