[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user srowen commented on the issue: https://github.com/apache/spark/pull/14142 merged to master/2.0 --- 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,

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user srowen commented on the issue: https://github.com/apache/spark/pull/14142 Yes, no need to ping inside of a day or two. We will often leave it open at least that long in case anyone has comments. --- If your project is set up for it, you can reply to this email and have

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user maver1ck commented on the issue: https://github.com/apache/spark/pull/14142 Merging ? --- 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

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14142 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 project does not have this feature

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14142 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62163/ Test PASSed. ---

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/14142 **[Test build #62163 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62163/consoleFull)** for PR 14142 at commit

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/14142 **[Test build #62163 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62163/consoleFull)** for PR 14142 at commit

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user srowen commented on the issue: https://github.com/apache/spark/pull/14142 Jenkins test 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 this feature enabled and wishes

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user srowen commented on the issue: https://github.com/apache/spark/pull/14142 Jenkins add to whitelist --- 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

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user maver1ck commented on the issue: https://github.com/apache/spark/pull/14142 Can we test this ? --- 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,

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user srowen commented on the issue: https://github.com/apache/spark/pull/14142 LGTM. Actually all other instances of NumberFormat in the project omit grouping separators, for various reasons. --- If your project is set up for it, you can reply to this email and have your

[GitHub] spark issue #14142: [SPARK-16439] Fix number formatting in SQL UI

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14142 Can one of the admins verify this patch? --- 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