Saiku Chinese Query (in view of a question: saiku executes mdx and reports an error in Chinese)

Someone asked me about saiku's Chinese Query: saiku runs English by default. Many people have entered Chinese in mysql, and it is no problem to query in SQL language. However, if you use the mdx query function of saiku, an error is returned. This is because mysql supports Chinese query by default. The saiku format is not good, especially the UTF-8 encoding format. Generally, gbk encoding may also work. So m appears.

Someone asked me about saiku's Chinese Query: saiku runs English by default. Many people have entered Chinese in mysql, and it is no problem to query in SQL language. However, if you use the mdx query function of saiku, an error is returned. This is because mysql supports Chinese query by default. The saiku format is not good, especially the UTF-8 encoding format. Generally, gbk encoding may also work. So m appears.

Someone asked me about saiku's Chinese Query:

By default, saiku runs in English. Many users enter Chinese Characters in mysql and use SQL to query data.

However, if you use the mdx query function of saiku, an error is returned.

This is because mysql supports Chinese query by default. The saiku format is not good, especially the UTF-8 encoding format. Generally, gbk encoding may also work.

Therefore, an error occurs during mdx execution. However, the SQL language that converts mdx into mysql can find the result.

Solution: Set the Chinese encoding for saiku. In the Startup File, add a-Dfile. encoding = UTF-8

Specify the encoding method. You can.

The statement is as follows:

Export CATALINA_OPTS = "-Xms256m-Xmx768m-XX: MaxPermSize = 256 m-Dfile. encoding = UTF-8-Dorg. apache. tomcat. util. buf. UDecoder. ALLOW_ENCODED_SLASH = true-Djava. awt. headless = true"