This is an automated email from the ASF dual-hosted git repository.
qiangcai pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/carbondata.git
The following commit(s) were added to refs/heads/master by this push:
new 5e4f16c [CARBONDATA-3820] CDC update as new segment use target
table's sort_scope
5e4f16c is described below
commit 5e4f16c34b2692c60bf1b714167f9ca3f5836968
Author: ajantha-bhat <[email protected]>
AuthorDate: Wed Aug 26 13:00:25 2020 +0530
[CARBONDATA-3820] CDC update as new segment use target table's sort_scope
Why is this PR needed?
Originally when CDC is developed, it was using target table sort_scope for
new segment added but
What changes were proposed in this PR?
CDC update as new segment should use target table sort_scope
Does this PR introduce any user interface change?
No
Is any new testcase added?
No (verified manually the flows)
This closes #3901
---
.../execution/command/mutation/merge/CarbonMergeDataSetCommand.scala | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/integration/spark/src/main/scala/org/apache/spark/sql/execution/command/mutation/merge/CarbonMergeDataSetCommand.scala
b/integration/spark/src/main/scala/org/apache/spark/sql/execution/command/mutation/merge/CarbonMergeDataSetCommand.scala
index 5e75c56..2afdb1a 100644
---
a/integration/spark/src/main/scala/org/apache/spark/sql/execution/command/mutation/merge/CarbonMergeDataSetCommand.scala
+++
b/integration/spark/src/main/scala/org/apache/spark/sql/execution/command/mutation/merge/CarbonMergeDataSetCommand.scala
@@ -219,7 +219,7 @@ case class CarbonMergeDataSetCommand(
val dataFrame = loadDF.select(tableCols.map(col): _*)
CarbonInsertIntoCommand(databaseNameOp = Some(carbonTable.getDatabaseName),
tableName = carbonTable.getTableName,
- options = Map("fileheader" -> header, "sort_scope" -> "no_sort"),
+ options = Map("fileheader" -> header),
isOverwriteTable = false,
dataFrame.queryExecution.logical,
carbonTable.getTableInfo,
