VenuReddy2103 opened a new pull request #3745:
URL: https://github.com/apache/carbondata/pull/3745
### Why is this PR needed?
Data load with partition columns fail with InvalidLoadOptionException when
load option `header` is set to `true`.
**Callstack:**
`2020-05-05 21:49:35 AUDIT audit:97 - {"time":"5 May, 2020 9:49:35 PM
IST","username":"root1","opName":"LOAD
DATA","opId":"199081091980878","opStatus":"FAILED","opTime":"1734
ms","table":"default.source","extraInfo":{"Exception":"org.apache.carbondata.common.exceptions.sql.InvalidLoadOptionException","Message":"When
'header' option is true, 'fileheader' option is not required."}}
Exception in thread "main"
org.apache.carbondata.common.exceptions.sql.InvalidLoadOptionException: When
'header' option is true, 'fileheader' option is not required.
at
org.apache.carbondata.processing.loading.model.CarbonLoadModelBuilder.build(CarbonLoadModelBuilder.java:203)
at
org.apache.carbondata.processing.loading.model.CarbonLoadModelBuilder.build(CarbonLoadModelBuilder.java:126)
at
org.apache.spark.sql.execution.datasources.SparkCarbonTableFormat.prepareWrite(SparkCarbonTableFormat.scala:132)
at
org.apache.spark.sql.execution.datasources.FileFormatWriter$.write(FileFormatWriter.scala:103)
at
org.apache.spark.sql.execution.command.management.CarbonInsertIntoHadoopFsRelationCommand.run(CarbonInsertIntoHadoopFsRelationCommand.scala:160)
at
org.apache.spark.sql.execution.command.DataWritingCommandExec.sideEffectResult$lzycompute(commands.scala:104)
at
org.apache.spark.sql.execution.command.DataWritingCommandExec.sideEffectResult(commands.scala:102)`
### What changes were proposed in this PR?
In `SparkCarbonTableFormat.prepareWrite()` method after adding the
`fileheader` option with header columns, to `optionsFinal`, need to set
`header` option to `false`.
### Does this PR introduce any user interface change?
- No
### Is any new testcase added?
- No
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
