Permalink
Show file tree
Hide file tree
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
[CARBONDATA-4190] Integrate Carbondata with Spark 3.1.1 version
Why is this PR needed? To integrate Carbondata with Spark3.1.1 What changes were proposed in this PR? Refactored code to add changes to support Spark 3.1.1 along with Spark 2.3 and 2.4 versions Changes: 1. Compile Related Changes 1. New Spark package in MV, Streaming and spark-integration. 2. API wise changes as per spark changes 2. Spark has moved to Proleptic Gregorian Calendar, due to which timestamp related changes in carbondata are also required. 3. Show segment by select command refactor 4. Few Lucene test cases ignored due to the deadlock in spark DAGSchedular, which does not allow it to work. 5. Alter rename: Parser enabled in Carbon and check for carbon 6. doExecuteColumnar() changes in CarbonDataSourceScan.scala 7. char/varchar changes from spark side. 8. Rule name changed in MV 9. In univocity parser, CSVParser version changed. 10. New Configs added in SparkTestQueryExecutor to keep some behaviour same as 2.3 and 2.4 Does this PR introduce any user interface change? No Is any new testcase added? No This closes #4141
- Loading branch information
1 parent
18665cc
commit 8ceb4fdd94a1d92a760a3c96d212fd521e9f3ccf
Showing
178 changed files
with
4,548 additions
and
1,650 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -210,4 +210,6 @@ | ||
BSD 2-Clause | ||
------------ | ||
|
||
com.github.luben:zstd-jni | ||
com.github.luben:zstd-jni | ||
|
||
com.github.paul-hammant:paranamer |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.