Skip to content
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

[SPARK-16439] [SQL] bring back the separator in SQL UI #15106

Closed
wants to merge 1 commit into from

Conversation

davies
Copy link
Contributor

@davies davies commented Sep 14, 2016

What changes were proposed in this pull request?

Currently, the SQL metrics looks like number of rows: 111111111111, it's very hard to read how large the number is. So a separator was added by #12425, but removed by #14142, because the separator is weird in some locales (for example, pl_PL), this PR will add that back, but always use "," as the separator, since the SQL UI are all in English.

How was this patch tested?

Existing tests.
metrics

@davies
Copy link
Contributor Author

davies commented Sep 14, 2016

cc @maver1ck @srowen

@SparkQA
Copy link

SparkQA commented Sep 15, 2016

Test build #65412 has finished for PR 15106 at commit 11a989e.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@srowen
Copy link
Member

srowen commented Sep 15, 2016

The question isn't the language of the UI, but of the host OS. I think this just causes the previous problem again, and that seems more important. I don't think we can make this change as is.

@maver1ck
Copy link
Contributor

I think this patch could actually work.
Number format is executed on the server side.
I did some tests and it looks good.

@davies
Copy link
Contributor Author

davies commented Sep 16, 2016

@srowen The previous problem is caused by using the default locale of host to format the numbers, that sounds perfect by caused some problems. So we fallback to only use English as the locale, it will works well everywhere.

@davies
Copy link
Contributor Author

davies commented Sep 19, 2016

@srowen Could you left an lgtm here?

@srowen
Copy link
Member

srowen commented Sep 19, 2016

If @maver1ck is OK with it I am, sure.

@maver1ck
Copy link
Contributor

LGTM.

@davies
Copy link
Contributor Author

davies commented Sep 19, 2016

Merging this into master and 2.0, thanks!

asfgit pushed a commit that referenced this pull request Sep 19, 2016
## What changes were proposed in this pull request?

Currently, the SQL metrics looks like `number of rows: 111111111111`, it's very hard to read how large the number is. So a separator was added by #12425, but removed by #14142, because the separator is weird in some locales (for example, pl_PL), this PR will add that back, but always use "," as the separator, since the SQL UI are all in English.

## How was this patch tested?

Existing tests.
![metrics](https://cloud.githubusercontent.com/assets/40902/14573908/21ad2f00-030d-11e6-9e2c-c544f30039ea.png)

Author: Davies Liu <davies@databricks.com>

Closes #15106 from davies/metric_sep.

(cherry picked from commit e063206)
Signed-off-by: Davies Liu <davies.liu@gmail.com>
@asfgit asfgit closed this in e063206 Sep 19, 2016
wgtmac pushed a commit to wgtmac/spark that referenced this pull request Sep 19, 2016
## What changes were proposed in this pull request?

Currently, the SQL metrics looks like `number of rows: 111111111111`, it's very hard to read how large the number is. So a separator was added by apache#12425, but removed by apache#14142, because the separator is weird in some locales (for example, pl_PL), this PR will add that back, but always use "," as the separator, since the SQL UI are all in English.

## How was this patch tested?

Existing tests.
![metrics](https://cloud.githubusercontent.com/assets/40902/14573908/21ad2f00-030d-11e6-9e2c-c544f30039ea.png)

Author: Davies Liu <davies@databricks.com>

Closes apache#15106 from davies/metric_sep.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants