[
https://issues.apache.org/jira/browse/CASSANDRA-16429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287115#comment-17287115
]
Aleksey Yeschenko commented on CASSANDRA-16429:
-----------------------------------------------
As others have said here, I don't believe we have a choice here, unfortunately.
Of course there were people relying on lack of enforcement here. Sad to see the
partial revert, but I'm on board with keeping compatibility. The lesson here is
that we need more validation of user inputs instead of implicit convention.
> 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: 10m
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
