[ 
https://issues.apache.org/jira/browse/CASSANDRA-16429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288643#comment-17288643
 ] 

Yifan Cai commented on CASSANDRA-16429:
---------------------------------------

Starting commit

CI Results (pending):
|| Branch || Source || Circle CI || Jenkins ||
|trunk|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-16429-trunk-C3A7A246-F5BF-4A45-9CDF-2D455ADEF39A]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-16429-trunk-C3A7A246-F5BF-4A45-9CDF-2D455ADEF39A]|[build|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/393/pipeline]|


> Fix incorrect encoding for strings can be UTF8
> ----------------------------------------------
>
>                 Key: CASSANDRA-16429
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16429
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL/Interpreter
>            Reporter: Yoshi Kimoto
>            Assignee: Yifan Cai
>            Priority: Normal
>             Fix For: 4.0-beta
>
>         Attachments: jptest.cql
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to