-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-28945][SPARK-29037][CORE][SQL] Fix the issue that spark gives duplicate result and support concurrent file source write operations write to different partitions in the same table. #25863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
fd8a8b0
[SPARK-28945][SPARK-29037][CORE][SQL] Fix the issue that spark gives …
turboFei f2f330f
escape dynamicPartitionOverwrite in FileSourceWriteDesc
turboFei e75441e
fix invoke getFileStatus multi times
turboFei cb150c3
reduce invoke filestatus
turboFei cbe10f2
diy merge paths
turboFei b3ab0bb
report all confilicted info
turboFei fa66a5b
rebase master
turboFei 79d59bd
fix code
turboFei a348a40
fix style
turboFei 0433977
fix code
turboFei f45ca9b
fix code
turboFei File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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
32 changes: 32 additions & 0 deletions
32
core/src/main/scala/org/apache/spark/internal/io/FileSourceWriteDesc.scala
This file contains hidden or 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 |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| /* | ||
| * Licensed to the Apache Software Foundation (ASF) under one or more | ||
| * contributor license agreements. See the NOTICE file distributed with | ||
| * this work for additional information regarding copyright ownership. | ||
| * The ASF licenses this file to You under the Apache License, Version 2.0 | ||
| * (the "License"); you may not use this file except in compliance with | ||
| * the License. You may obtain a copy of the License at | ||
| * | ||
| * http://www.apache.org/licenses/LICENSE-2.0 | ||
| * | ||
| * Unless required by applicable law or agreed to in writing, software | ||
| * distributed under the License is distributed on an "AS IS" BASIS, | ||
| * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| * See the License for the specific language governing permissions and | ||
| * limitations under the License. | ||
| */ | ||
|
|
||
| package org.apache.spark.internal.io | ||
|
|
||
| /** | ||
| * A class to describe the properties for file source write operation. | ||
| * | ||
| * @param isInsertIntoHadoopFsRelation whether is a InsertIntoHadoopFsRelation operation | ||
| * @param dynamicPartitionOverwrite dynamic overwrite is enabled, the save mode is overwrite and | ||
| * not all partition keys are specified | ||
| * @param escapedStaticPartitionKVs static partition key and value pairs, which have been escaped | ||
| */ | ||
| class FileSourceWriteDesc( | ||
| val isInsertIntoHadoopFsRelation: Boolean = false, | ||
| val dynamicPartitionOverwrite: Boolean = false, | ||
| val escapedStaticPartitionKVs: Seq[(String, String)] = Seq.empty[(String, String)]) | ||
| extends Serializable |
This file contains hidden or 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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about logDebug? It produces a lot of logs in Jenkins.
@advancedxy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
about 15843 lines
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
15843 is a lot, however, it would be not that much inside one spark application.
One way to solve this, is to use an object level counter to only log the first warning log(or logs).
But I am not sure if that's worth it. Also, the head of logs may get rotated and discarded...
Or use logDebug is fine, but normally user won't set log level to DEBUG.
I am not sure which one is better. It's up to you then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure what that means. V2 task commit is non-atomic so isn't the same as v1. if task attempt 1 failed, task attempt 2 will call mergepaths into the same dir, so the set of files to commit in job commit may contain the output of both.