[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/12520 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread srowen
Github user srowen commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214700491 Merged to master --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this featu

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214699059 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214699058 Merged build finished. Test PASSed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your projec

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214698894 **[Test build #56987 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56987/consoleFull)** for PR 12520 at commit [`12b5739`](https://g

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214668768 **[Test build #56987 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56987/consoleFull)** for PR 12520 at commit [`12b5739`](https://gi

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread srowen
Github user srowen commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214668567 Jenkins retest this please --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread srowen
Github user srowen commented on a diff in the pull request: https://github.com/apache/spark/pull/12520#discussion_r61047232 --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/PartitioningUtils.scala --- @@ -441,9 +441,9 @@ private[sql] object Partitioning

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-26 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214642154 **[Test build #2884 has finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2884/consoleFull)** for PR 12520 at commit [`12b5739`](https://

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-25 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214619179 **[Test build #2884 has started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2884/consoleFull)** for PR 12520 at commit [`12b5739`](https://g

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-25 Thread javawithjiva
Github user javawithjiva commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214618915 Thank you for helping me get my first pull request out. Thanks --- If your project is set up for it, you can reply to this email and have your reply appear on Git

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-25 Thread srowen
Github user srowen commented on a diff in the pull request: https://github.com/apache/spark/pull/12520#discussion_r60964326 --- Diff: sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/PartitioningUtils.scala --- @@ -441,7 +441,7 @@ private[sql] object Partitioning

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-25 Thread javawithjiva
Github user javawithjiva commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214300491 Updated --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-25 Thread srowen
Github user srowen commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-214276411 @javawithjiva if you update this accordingly I'll merge --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. I

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-21 Thread srowen
Github user srowen commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-212953102 Actually, from skimming the code base, I think you've almost got all instances where valueOf could be parseX. Go for a clean sweep and update the JIRA. I see the followi

[GitHub] spark pull request: [SPARK-14756][Core] Use parseLong instead of v...

2016-04-21 Thread javawithjiva
Github user javawithjiva commented on the pull request: https://github.com/apache/spark/pull/12520#issuecomment-212948656 @srowen or @rxin Can one of you merge? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your proj