You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (Jira)" <ji...@apache.org> on 2021/02/08 00:39:00 UTC
[jira] [Comment Edited] (CASSANDRA-16429) cqlsh garbles column
names with Japanese characters
[ https://issues.apache.org/jira/browse/CASSANDRA-16429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280703#comment-17280703 ]
Jeremy Hanna edited comment on CASSANDRA-16429 at 2/8/21, 12:38 AM:
--------------------------------------------------------------------
Could this be related to the new code that exposes table schema directly to the drivers? CASSANDRA-14825
was (Author: jeromatron):
Could this be related to the new code that exposes table schema directly to the drivers?
> cqlsh garbles column names with Japanese characters
> ---------------------------------------------------
>
> Key: CASSANDRA-16429
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16429
> Project: Cassandra
> Issue Type: Bug
> Reporter: Yoshi Kimoto
> Priority: Normal
> Attachments: jptest.cql
>
>
> Tables created with Japanese character name columns are working well in C* 3.11.10 when doing a SELECT * in cqlsh but will show as garbled (shown as "?") in 4.0-beta4. DESCRIBE shows the column names correctly in both cases.
> Run the attached jptest.cql script in both envs with cqlsh -f. They will yield different results.
> My test env (MacOS 10.15.7):
> C* 3.11.10 with
> - OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_252-b09)
> - Python 2.7.16
> C* 4.0-beta4
> - OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.9.1+1)
> - Python 3.8.2
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org