[
https://issues.apache.org/jira/browse/CASSANDRA-16429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-16429:
----------------------------------
Fix Version/s: 4.0-beta5
Since Version: 4.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/f32475a839e01e4eea3989871d293d70e8a360d7
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed into trunk as [f32475a839e01e4eea3989871d293d70e8a360d7
|https://github.com/apache/cassandra/commit/f32475a839e01e4eea3989871d293d70e8a360d7]
> 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-beta5, 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]
