[ 
https://issues.apache.org/jira/browse/HIVE-16558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ZhangBing Lin updated HIVE-16558:
---------------------------------
    Description: 
In QueryProfileImpl.jamon,We see the following settings:
<?xml version="1.0" encoding="UTF-8" ?>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>HiveServer2</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta name="description" content="">

    <link href="/static/css/bootstrap.min.css" rel="stylesheet">
    <link href="/static/css/bootstrap-theme.min.css" rel="stylesheet">
    <link href="/static/css/hive.css" rel="stylesheet">
  </head>
So we should set the response code to utf-8, which can avoid Chinese garbled or 
other languages garbled,Please check it!
     This patch can only solve Drilldown read data from the cache when the 
Chinese show abnormal, and can not solve the Explain plan from the database 
query Chinese garbled, because the Chinese stored in the database is garbled.
     If you want to solve this problem, you need to modify the database 
encoding format.
     I try to modify the mysql 'columns_v2' table field 'comment' encoding 
utf8,Is this okay?
    


  was:
In QueryProfileImpl.jamon,We see the following settings:
<?xml version="1.0" encoding="UTF-8" ?>
<html lang="en">
  <head>
    <meta charset="utf-8">
    <title>HiveServer2</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta name="description" content="">

    <link href="/static/css/bootstrap.min.css" rel="stylesheet">
    <link href="/static/css/bootstrap-theme.min.css" rel="stylesheet">
    <link href="/static/css/hive.css" rel="stylesheet">
  </head>
So we should set the response code to utf-8, which can avoid Chinese garbled or 
other languages garbled,Please check it!
     This patch can only solve Drilldown read data from the cache when the 
Chinese show abnormal, and can not solve the Explain plan from the database 
query Chinese garbled, because the Chinese stored in the database is garbled.
     If you want to solve this problem, you need to modify the database 
encoding format.
     For example, the use of metastore is mysql, the storage of Chinese 
comments on the table is latin1 coding, and mysql support for utf-8 is not very 
good, limit the length of 767 characters.



> In the hiveserver2.jsp page, when you click Drilldown to view the details of 
> the Closed Queries, the Chinese show garbled
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-16558
>                 URL: https://issues.apache.org/jira/browse/HIVE-16558
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: ZhangBing Lin
>            Assignee: ZhangBing Lin
>             Fix For: 3.0.0
>
>         Attachments: HIVE-16558.1.patch, HIVE-16558.2.patch
>
>
> In QueryProfileImpl.jamon,We see the following settings:
> <?xml version="1.0" encoding="UTF-8" ?>
> <html lang="en">
>   <head>
>     <meta charset="utf-8">
>     <title>HiveServer2</title>
>     <meta name="viewport" content="width=device-width, initial-scale=1.0">
>     <meta name="description" content="">
>     <link href="/static/css/bootstrap.min.css" rel="stylesheet">
>     <link href="/static/css/bootstrap-theme.min.css" rel="stylesheet">
>     <link href="/static/css/hive.css" rel="stylesheet">
>   </head>
> So we should set the response code to utf-8, which can avoid Chinese garbled 
> or other languages garbled,Please check it!
>      This patch can only solve Drilldown read data from the cache when the 
> Chinese show abnormal, and can not solve the Explain plan from the database 
> query Chinese garbled, because the Chinese stored in the database is garbled.
>      If you want to solve this problem, you need to modify the database 
> encoding format.
>      I try to modify the mysql 'columns_v2' table field 'comment' encoding 
> utf8,Is this okay?
>     



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to