Uh oh!
There was an error while loading. Please reload this page.
[SPARK-6048] SparkConf should not translate deprecated configs on set - #4799
[SPARK-6048] SparkConf should not translate deprecated configs on set#4799andrewor14 wants to merge 6 commits into
Conversation
SparkQA
commented
Feb 27, 2015
Test build #28029 has started for PR 4799 at commit
|
andrewor14
commented
Feb 27, 2015
cc @vanzin who originally wrote this code |
SparkQA
commented
Feb 27, 2015
Test build #28029 has finished for PR 4799 at commit
|
AmplabJenkins
commented
Feb 27, 2015
Test FAILed. |
pwendell
commented
Feb 27, 2015
@vanzin does this look okay to you? I commented on the JIRA, but my main goal is to find a surgical patch here that can unblock the release, so just rewinding the change seems the safest. |
SparkQA
commented
Feb 27, 2015
Test build #28037 has started for PR 4799 at commit
|
SparkQA
commented
Feb 27, 2015
Test build #28037 has finished for PR 4799 at commit
|
AmplabJenkins
commented
Feb 27, 2015
Test PASSed. |
SparkQA
commented
Feb 28, 2015
Test build #28104 has started for PR 4799 at commit
|
vanzin
commented
Feb 28, 2015
Given the discussion on the bug it looks ok, but it's missing the documentation that explains the behavior. |
SparkQA
commented
Feb 28, 2015
Test build #28104 has finished for PR 4799 at commit
|
AmplabJenkins
commented
Feb 28, 2015
Test PASSed. |
pwendell
commented
Mar 1, 2015
I agree @andrewor14 can you add documentation about deprecated configs? I would extend what's there now: |
SparkQA
commented
Mar 1, 2015
Test build #28143 has started for PR 4799 at commit
|
SparkQA
commented
Mar 1, 2015
Test build #28143 has finished for PR 4799 at commit
|
AmplabJenkins
commented
Mar 1, 2015
Test PASSed. |
There was a problem hiding this comment.
This will log it on the executors, which seems weird since all other configuration warnings are logged at the driver or submission client. Can we just log this warning on the driver side? Or just don't log a deprecation warning always?
There was a problem hiding this comment.
Is your proposal to not log this warning, or log it on the driver side?
There was a problem hiding this comment.
Log it on the driver side during validation, or at some earlier point. I just think having it here isn't super useufl.
SparkQA
commented
Mar 2, 2015
Test build #28178 has started for PR 4799 at commit
|
SparkQA
commented
Mar 2, 2015
Test build #28178 has finished for PR 4799 at commit
|
AmplabJenkins
commented
Mar 2, 2015
Test PASSed. |
There was a problem hiding this comment.
Since you're doing this only once during the app's lifetime (this method is only called from SparkContext AFAICT), you could simplify the code that tracks whether warns have been printed in DeprecatedConfig. But ok to not do it if you want to limit the scope of the change.
There was a problem hiding this comment.
yeah let's revamp this whole thing after the release
vanzin
commented
Mar 2, 2015
LGTM, left just minor comments. |
pwendell
commented
Mar 3, 2015
Okay - thanks everyone for helping with this. I'll pull it in. |
There are multiple issues with translating on set outlined in the JIRA. This PR reverts the translation logic added to `SparkConf`. In the future, after the 1.3.0 release we will figure out a way to reorganize the internal structure more elegantly. For now, let's preserve the existing semantics of `SparkConf` since it's a public interface. Unfortunately this means duplicating some code for now, but this is all internal and we can always clean it up later. Author: Andrew Or <andrew@databricks.com> Closes#4799 from andrewor14/conf-set-translate and squashes the following commits: 11c525b [Andrew Or] Move warning to driver 10e77b5 [Andrew Or] Add documentation for deprecation precedence a369cb1 [Andrew Or] Merge branch 'master' of github.com:apache/spark into conf-set-translate c26a9e3 [Andrew Or] Revert all translate logic in SparkConf fef6c9c [Andrew Or] Restore deprecation logic for spark.executor.userClassPathFirst 94b4dfa [Andrew Or] Translate on get, not set (cherry picked from commit 258d154) Signed-off-by: Patrick Wendell <patrick@databricks.com>
There are multiple issues with translating on set outlined in the JIRA.
This PR reverts the translation logic added to
SparkConf. In the future, after the 1.3.0 release we will figure out a way to reorganize the internal structure more elegantly. For now, let's preserve the existing semantics ofSparkConfsince it's a public interface. Unfortunately this means duplicating some code for now, but this is all internal and we can always clean it up later.