You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by GitBox <gi...@apache.org> on 2020/11/03 13:32:54 UTC

[GitHub] [ambari] akiyamaneko opened a new pull request #3252: [AMBARI-25579] Historical configuration parameters display garbled characters

akiyamaneko opened a new pull request #3252:
URL: https://github.com/apache/ambari/pull/3252


   ## What changes were proposed in this pull request?
   + Ambari has some tables that explicitly specify the encoding type of the field as UTF-8([Ambari-DDL-MySQL-CREATE.sql#L973](https://github.com/apache/ambari/tree/branch-2.7/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L973) and [Ambari-DDL-MySQL-CREATE.sql#L993](https://github.com/apache/ambari/tree/branch-2.7/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L993)),  However, the mysql URL in `/etc/ambari-server/conf/ambari.properties` does not specify a character set, which would cause the encoding methods of MySQL and Ambari-server to be inconsistent.
   + The `note` field in the `serviceconfig` table of mysql preferably also supports non-ASCII characters.
   ## How was this patch tested?
   munual test result shows like this:
   ![ambari serviceconfig in mysql shows illegal-fixed](https://user-images.githubusercontent.com/52202080/97853865-aa24ad00-1d33-11eb-8551-70dd9de39c5f.png)
   ![ambari serviceconfig in web page shows illegal-fixed](https://user-images.githubusercontent.com/52202080/97853878-ad1f9d80-1d33-11eb-85cc-ca553b4db8e5.png)
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org