spark git commit: [SPARK-20229][SQL] add semanticHash to QueryPlan

2017-04-09 Thread wenchen
Repository: spark Updated Branches: refs/heads/master 1a0bc4165 -> 3d7f201f2 [SPARK-20229][SQL] add semanticHash to QueryPlan ## What changes were proposed in this pull request? Like `Expression`, `QueryPlan` should also have a `semanticHash` method, then we can put plans to a hash map and

spark git commit: [SPARK-20270][SQL] na.fill should not change the values in long or integer when the default value is in double

2017-04-09 Thread dbtsai
Repository: spark Updated Branches: refs/heads/master 7bfa05e0a -> 1a0bc4165 [SPARK-20270][SQL] na.fill should not change the values in long or integer when the default value is in double ## What changes were proposed in this pull request? This bug was partially addressed in SPARK-18555

spark git commit: [SPARK-20264][SQL] asm should be non-test dependency in sql/core

2017-04-09 Thread lixiao
Repository: spark Updated Branches: refs/heads/branch-2.1 43a7fcad5 -> 1a73046b4 [SPARK-20264][SQL] asm should be non-test dependency in sql/core ## What changes were proposed in this pull request? sq/core module currently declares asm as a test scope dependency. Transitively it should

spark git commit: [SPARK-20264][SQL] asm should be non-test dependency in sql/core

2017-04-09 Thread lixiao
Repository: spark Updated Branches: refs/heads/master 7a63f5e82 -> 7bfa05e0a [SPARK-20264][SQL] asm should be non-test dependency in sql/core ## What changes were proposed in this pull request? sq/core module currently declares asm as a test scope dependency. Transitively it should actually

spark git commit: [SPARK-20253][SQL] Remove unnecessary nullchecks of a return value from Spark runtime routines in generated Java code

2017-04-09 Thread wenchen
Repository: spark Updated Branches: refs/heads/master 261eaf514 -> 7a63f5e82 [SPARK-20253][SQL] Remove unnecessary nullchecks of a return value from Spark runtime routines in generated Java code ## What changes were proposed in this pull request? This PR elminates unnecessary nullchecks of

spark git commit: [SPARK-20260][MLLIB] String interpolation required for error message

2017-04-09 Thread srowen
Repository: spark Updated Branches: refs/heads/branch-2.1 658b35885 -> 43a7fcad5 [SPARK-20260][MLLIB] String interpolation required for error message ## What changes were proposed in this pull request? This error message doesn't get properly formatted because of a missing `s`. Currently the

spark git commit: [SPARK-20260][MLLIB] String interpolation required for error message

2017-04-09 Thread srowen
Repository: spark Updated Branches: refs/heads/master 1f0de3c1c -> 261eaf514 [SPARK-20260][MLLIB] String interpolation required for error message ## What changes were proposed in this pull request? This error message doesn't get properly formatted because of a missing `s`. Currently the

spark git commit: [SPARK-19991][CORE][YARN] FileSegmentManagedBuffer performance improvement

2017-04-09 Thread srowen
Repository: spark Updated Branches: refs/heads/master 34fc48fb5 -> 1f0de3c1c [SPARK-19991][CORE][YARN] FileSegmentManagedBuffer performance improvement ## What changes were proposed in this pull request? Avoid `NoSuchElementException` every time `ConfigProvider.get(val, default)` falls back

spark git commit: [MINOR] Issue: Change "slice" vs "partition" in exception messages (and code?)

2017-04-09 Thread srowen
Repository: spark Updated Branches: refs/heads/master e1afc4dcc -> 34fc48fb5 [MINOR] Issue: Change "slice" vs "partition" in exception messages (and code?) ## What changes were proposed in this pull request? Came across the term "slice" when running some spark scala code. Consequently, a