You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (Created) (JIRA)" <ji...@apache.org> on 2012/03/05 06:45:00 UTC
[jira] [Created] (CASSANDRA-3998) CLI: NUL character for data not
visible
CLI: NUL character for data not visible
---------------------------------------
Key: CASSANDRA-3998
URL: https://issues.apache.org/jira/browse/CASSANDRA-3998
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.8
Reporter: Tyler Hobbs
When using UTF8Type or AsciiType, if a column name or value is only 0x00 bytes, the CLI will not show any indication that data is there. Here's an example where the column value is "0x00":
{noformat}
[default@Foo] get Foo2['key'];
=> (column=a, value=, timestamp=1330925963085434)
{noformat}
I'm not sure what the best solution is, but the current behavior is deceptive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3998) CLI: NUL character for data not
visible
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222438#comment-13222438 ]
Jonathan Ellis commented on CASSANDRA-3998:
-------------------------------------------
Maybe we should turn those into unicode code point notation of some sort. Note that at least in cqlsh we have the inverse problem when inputting non-ascii charactess.
Here's postgresql's solution: (http://www.postgresql.org/docs/9.0/static/sql-syntax-lexical.html)
bq. A variant of quoted identifiers allows including escaped Unicode characters identified by their code points. This variant starts with U& (upper or lower case U followed by ampersand) immediately before the opening double quote, without any spaces in between, for example U&"foo". (Note that this creates an ambiguity with the operator &. Use spaces around the operator to avoid this problem.) Inside the quotes, Unicode characters can be specified in escaped form by writing a backslash followed by the four-digit hexadecimal code point number or alternatively a backslash followed by a plus sign followed by a six-digit hexadecimal code point number. For example, the identifier "data" could be written as {{U&"d\0061t\+000061"}}. The following less trivial example writes the Russian word "slon" (elephant) in Cyrillic letters: {{U&"\0441\043B\043E\043D"}}.
> CLI: NUL character for data not visible
> ---------------------------------------
>
> Key: CASSANDRA-3998
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3998
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.8
> Reporter: Tyler Hobbs
>
> When using UTF8Type or AsciiType, if a column name or value is only 0x00 bytes, the CLI will not show any indication that data is there. Here's an example where the column value is "0x00":
> {noformat}
> [default@Foo] get Foo2['key'];
> => (column=a, value=, timestamp=1330925963085434)
> {noformat}
> I'm not sure what the best solution is, but the current behavior is deceptive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira