[jira] [Commented] (CASSANDRA-15200) Can a new adding node store other keyspaces' data and add permission of one more machine failure for a replicator 2's keyspace in the new even number nodes'
[ https://issues.apache.org/jira/browse/CASSANDRA-15200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878928#comment-16878928 ] gloCalHelp.com commented on CASSANDRA-15200: Dear sir Jeff, sorry ask here, I had thoughjt this is a very important function for cassandra, and I have maked this as an improvement. Anyway, where is the fast reply place for questions on cassandra? > Can a new adding node store other keyspaces' data and add permission of > one more machine failure for a replicator 2's keyspace in the new even number > nodes' DC? > -- > > Key: CASSANDRA-15200 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15200 > Project: Cassandra > Issue Type: Improvement >Reporter: gloCalHelp.com >Priority: Normal > > Question on adding a new node, replicator and how many machine failes? > Can a new adding node store other keyspaces' data and add permission of > one more machine failure for a replicator 2's keyspace in the new even number > nodes' DC? > Cassandra's designing of adding a new node for only a keyspace is > quite good for a high load keyspace and token allocation. But I have > aquestions: > 1st, if the high load keyspace has a replicator of only 2, and > original cluster has only 3 datanodes, if adding a new node to form a 4 > datanodes for this keyspace, then there will permit how many machine failes > for this 2 replicator keyspace's 4 data nodes center? > 2nd, on cassandra's official web, there is a line of : To use this > approach, the new node must be started with the JVM option > -Dcassandra.allocate_tokens_for_keyspace=, where is the > keyspace from which the algorithm can find the load information to optimize > token assignment for. > Does this mean that a new adding node can only store a keyspace's data? > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15200) Can a new adding node store other keyspaces' data and add permission of one more machine failure for a replicator 2's keyspace in the new even number nodes' DC
gloCalHelp.com created CASSANDRA-15200: -- Summary: Can a new adding node store other keyspaces' data and add permission of one more machine failure for a replicator 2's keyspace in the new even number nodes' DC? Key: CASSANDRA-15200 URL: https://issues.apache.org/jira/browse/CASSANDRA-15200 Project: Cassandra Issue Type: Improvement Reporter: gloCalHelp.com Question on adding a new node, replicator and how many machine failes? Can a new adding node store other keyspaces' data and add permission of one more machine failure for a replicator 2's keyspace in the new even number nodes' DC? Cassandra's designing of adding a new node for only a keyspace is quite good for a high load keyspace and token allocation. But I have aquestions: 1st, if the high load keyspace has a replicator of only 2, and original cluster has only 3 datanodes, if adding a new node to form a 4 datanodes for this keyspace, then there will permit how many machine failes for this 2 replicator keyspace's 4 data nodes center? 2nd, on cassandra's official web, there is a line of : To use this approach, the new node must be started with the JVM option -Dcassandra.allocate_tokens_for_keyspace=, where is the keyspace from which the algorithm can find the load information to optimize token assignment for. Does this mean that a new adding node can only store a keyspace's data? -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15197) a view's building status is still unknown after several days past.
gloCalHelp.com created CASSANDRA-15197:
--
Summary: a view's building status is still unknown after several
days past.
Key: CASSANDRA-15197
URL: https://issues.apache.org/jira/browse/CASSANDRA-15197
Project: Cassandra
Issue Type: Bug
Reporter: gloCalHelp.com
a view's building status is still unknown after several days past, the view and
base table's sql is on https://issues.apache.org/jira/browse/CASSANDRA-15187 .
the unknown message are:
hygl_jcsj.MView_lastInsert_GPS4 has not finished building; node status is below.
Host Info
/192.168.136.162 UNKNOWN
/192.168.136.161 UNKNOWN
/192.168.136.160 UNKNOWN
h2. *{color:#FF}cassandra's non nature orderby view still cann't get the
newest rows by limit query, is there any better way to get some newest
rows?{color}*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15182) cqlsh syntax error output fails with UnicodeEncodeError
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gloCalHelp.com updated CASSANDRA-15182:
---
Resolution: Fixed
Status: Resolved (was: Open)
put a default num for a non value decimal column, then solve the problem.
> cqlsh syntax error output fails with UnicodeEncodeError
> ---
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
> Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x
>
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15192) Why a added new node stop an old node to start?
gloCalHelp.com created CASSANDRA-15192:
--
Summary: Why a added new node stop an old node to start?
Key: CASSANDRA-15192
URL: https://issues.apache.org/jira/browse/CASSANDRA-15192
Project: Cassandra
Issue Type: Bug
Components: Cluster/Membership
Reporter: gloCalHelp.com
Attachments: StrangeNoErrorStopLogs.zip
I have a running 3 datanodes with cassandra3.11.3 with a keyspace having a
table over 10millions row in Centos6.9, after I added a node in win10 with
cassandra3.11.4 for a whole night, this afternoon, one of the old 3 nodes can
not start, and I use "nodetool decommission" on the new node and "nodetool
removenode (new node's uuid)", but one of the 3 old node can not start with an
no error system.log and debug.log as the attachment.
Finally, I setting the failing old node's start JVM_OPTS to have
{{-Dcassandra.reset_bootstrap_progress=true and it become
live.[^StrangeNoErrorStopLogs.zip]}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15189) Cassandra3.11.3, an "insert same primary keys" doesn't report a error but work as update.
gloCalHelp.com created CASSANDRA-15189:
--
Summary: Cassandra3.11.3, an "insert same primary keys" doesn't
report a error but work as update.
Key: CASSANDRA-15189
URL: https://issues.apache.org/jira/browse/CASSANDRA-15189
Project: Cassandra
Issue Type: Bug
Reporter: gloCalHelp.com
Cassandra3.11.3, an "insert same primary keys" doesn't report a error but work
as update.
At the below, the 1st "-e", insert a row.
the 2nd "-e" also insert a row with only the last column's value being changed
to 375,
The 2nd sql successfully executed as a update, checked by the 3rd "-e"
bash-4.1$ bin/cqlsh hadoop6 -u dba -p *** --debug -e "INSERT INTO
HYGL_JCSJ.hyjg_ods_yy_gps_novar3
(clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
VALUES ('黑A00888D','2019-06-25
09:57:19',0,-20,'',-20,-20,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
,796.0,2205,746,'null','null','null',0,'379');"
Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
bash-4.1$ bin/cqlsh hadoop6 -u dba -p *** --debug -e "INSERT INTO
HYGL_JCSJ.hyjg_ods_yy_gps_novar3
(clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
VALUES ('黑A00888D','2019-06-25
09:57:19',0,-20,'',-20,-20,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
,796.0,2205,746,'null','null','null',0,'375');"
Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
bash-4.1$ bin/cqlsh hadoop4 -u dba -p *** --debug -e "select * from
HYGL_JCSJ.hyjg_ods_yy_gps_novar3 where clcph='黑A00888D' and dwsj='2019-06-25
09:57:19';"Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
clcph | dwsj | bc | blbs | cjbzh | ckryid |
clid | clmc | ddfx | ddrq | ddsj | dlzbs | dwrq
| dwsk | fcsxh | fwj | gd | gdjd | gdwd | jd | jsdlc | jszjl | jxzjl
| kxbs | sfaxlxs | sfcs | sjgxsj | sjid | sjlx | sjlyxt | sjsfzh | sjwtid |
sjxm | sjzlfj | sssd | szzdid | szzdmc | szzdxh | wd | xlbm | xlid | xlmc |
xslc | xxfssj | xxjssj | xxrksj | xzzdid | xzzdmc | xzzdxh | yxfx | yygpsxxjlid
| yyzt
---+-++--+---++--+--+--+-+--+---+--+--+---+-++---+--+--+---+---+---+--+-+--++--+--++++--++--++++--+--+--+--+--+++++++--+-+--
黑A00888D | 2019-06-25 01:57:19.00+ | 0 | -20 | | -20 | -20
| 379-7038 | 1434 | 2019-06-24 16:00:00.00+ | null | null | null |
null | null | 275 | 0 | 126723690 | 45726990 | null | 796.0 | 2205 | 746 |
null | null | null | null | null | null | null | null | null | null
| null | 0 | null | null | null | null | null | null | 375 | null |
null | null | null | null | null | null | null | null | null
(1 rows)
bash-4.1$
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15182) cqlsh syntax error output fails with UnicodeEncodeError
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875354#comment-16875354
]
gloCalHelp.com commented on CASSANDRA-15182:
so this issue has close, how to close it?
> cqlsh syntax error output fails with UnicodeEncodeError
> ---
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
> Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x
>
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15182) cqlsh syntax error output fails with UnicodeEncodeError
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875353#comment-16875353
]
gloCalHelp.com commented on CASSANDRA-15182:
Hi, Yuki SenSei, AriGaTou GouZaiMaSu, you are right, the "" is the
problem, because these columns are decimal without a value, so I let them
blank as traditional DB. Now I put a default value of -20 for these blank
decimal , it works now:
bash-4.1$ bin/cqlsh hadoop6 -u -p --debug --encoding utf-8 -e "INSERT INTO
HYGL_JCSJ.hyjg_ods_yy_gps_novar3
(clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
VALUES ('8516178','2019-06-25
09:57:19',0,-20,'',-20,-20,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
,796.0,2205,746,'null','null','null',0,'379');"
But I find a bug for Cassandra3.11.3, an insert same primary keys doesn't
report a error but work as update.
> cqlsh syntax error output fails with UnicodeEncodeError
> ---
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
> Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x
>
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15187) Cann't table and materialized view's timestamp column order by function well?
[
https://issues.apache.org/jira/browse/CASSANDRA-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874747#comment-16874747
]
gloCalHelp.com commented on CASSANDRA-15187:
For helping a new comer, I got answer from genius Elliott on 1st and 3rd
questions:
Turning on tracing can get you a general idea of what's running, though.
For runtime variables.. it depends, but JMX can probably get most of it.
> Cann't table and materialized view's timestamp column order by function well?
> --
>
> Key: CASSANDRA-15187
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15187
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: gloCalHelp.com
>Priority: Normal
>
> Cann't table and materialized view's timestamp column order by function well?
> I am using cassandra3.11.3 on centos6.9 with python2.7.13, when I create a
> table as below:
> CREATE TABLE hygl_jcsj.hyjg_ods_yy_gps_novar4 (
> clcph text,
> dwsj timestamp,
> bc decimal,
> blbs decimal,
> cjbzh text,
> ckryid decimal,
> clid decimal,
> clmc text,
> ddfx decimal,
> ddrq timestamp,
> ddsj text,
> dlzbs decimal,
> dwrq timestamp,
> dwsk text,
> fcsxh decimal,
> fwj decimal,
> gd decimal,
> gdjd decimal,
> gdwd decimal,
> jd decimal,
> jsdlc decimal,
> jszjl decimal,
> jxzjl decimal,
> kxbs decimal,
> sfaxlxs decimal,
> sfcs decimal,
> sjgxsj timestamp,
> sjid text,
> sjlx decimal,
> sjlyxt decimal,
> sjsfzh text,
> sjwtid text,
> sjxm text,
> sjzlfj decimal,
> sssd decimal,
> szzdid decimal,
> szzdmc text,
> szzdxh decimal,
> wd decimal,
> xlbm text,
> xlid decimal,
> xlmc text,
> xslc decimal,
> xxfssj timestamp,
> xxjssj timestamp,
> xxrksj timestamp,
> xzzdid decimal,
> xzzdmc text,
> xzzdxh decimal,
> yxfx decimal,
> yygpsxxjlid decimal,
> yyzt decimal,
> PRIMARY KEY (clcph, dwsj)
> ) WITH CLUSTERING ORDER BY (dwsj ASC)
> AND bloom_filter_fp_chance = 0.01
> AND caching = \{'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = 'GPS数据'
> AND compaction = \{'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = \{'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.0
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 360
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> the column dwsj is order by nature order of ASC, but when I use cqlsh -e
> "select clcph,dwsj from hygl_jcsj.hyjg_ods_yy_gps_novar4 limit 18",
> the result is:
> | clcph \| dwsj| | | | |
> |-+-| | | | |
> | a85161782800835 \| 2019-06-27 11:39:42.00+| | | | |
> | a85161785390963 \| 2019-06-27 13:06:54.00+
[jira] [Commented] (CASSANDRA-15187) Cann't table and materialized view's timestamp column order by function well?
[
https://issues.apache.org/jira/browse/CASSANDRA-15187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874678#comment-16874678
]
gloCalHelp.com commented on CASSANDRA-15187:
But isn't there a method to get total data's ordered list from all partitions?
And by the way, would someone can teach me these 3 questions:
1, is there a command or utility to check a running query's execution status?
2, is a materialized view's data all link to the base table? otherwise, why the
view's creating method is finished so quick?
3, how can I check a running cassandra's runtime variables?
> Cann't table and materialized view's timestamp column order by function well?
> --
>
> Key: CASSANDRA-15187
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15187
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: gloCalHelp.com
>Priority: Normal
>
> Cann't table and materialized view's timestamp column order by function well?
> I am using cassandra3.11.3 on centos6.9 with python2.7.13, when I create a
> table as below:
> CREATE TABLE hygl_jcsj.hyjg_ods_yy_gps_novar4 (
> clcph text,
> dwsj timestamp,
> bc decimal,
> blbs decimal,
> cjbzh text,
> ckryid decimal,
> clid decimal,
> clmc text,
> ddfx decimal,
> ddrq timestamp,
> ddsj text,
> dlzbs decimal,
> dwrq timestamp,
> dwsk text,
> fcsxh decimal,
> fwj decimal,
> gd decimal,
> gdjd decimal,
> gdwd decimal,
> jd decimal,
> jsdlc decimal,
> jszjl decimal,
> jxzjl decimal,
> kxbs decimal,
> sfaxlxs decimal,
> sfcs decimal,
> sjgxsj timestamp,
> sjid text,
> sjlx decimal,
> sjlyxt decimal,
> sjsfzh text,
> sjwtid text,
> sjxm text,
> sjzlfj decimal,
> sssd decimal,
> szzdid decimal,
> szzdmc text,
> szzdxh decimal,
> wd decimal,
> xlbm text,
> xlid decimal,
> xlmc text,
> xslc decimal,
> xxfssj timestamp,
> xxjssj timestamp,
> xxrksj timestamp,
> xzzdid decimal,
> xzzdmc text,
> xzzdxh decimal,
> yxfx decimal,
> yygpsxxjlid decimal,
> yyzt decimal,
> PRIMARY KEY (clcph, dwsj)
> ) WITH CLUSTERING ORDER BY (dwsj ASC)
> AND bloom_filter_fp_chance = 0.01
> AND caching = \{'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = 'GPS数据'
> AND compaction = \{'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = \{'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.0
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 360
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> the column dwsj is order by nature order of ASC, but when I use cqlsh -e
> "select clcph,dwsj from hygl_jcsj.hyjg_ods_yy_gps_novar4 limit 18",
> the result is:
> | clcph \| dwsj| | | | |
>
[jira] [Created] (CASSANDRA-15187) Cann't table and materialized view's timestamp column order by function well?
gloCalHelp.com created CASSANDRA-15187:
--
Summary: Cann't table and materialized view's timestamp column
order by function well?
Key: CASSANDRA-15187
URL: https://issues.apache.org/jira/browse/CASSANDRA-15187
Project: Cassandra
Issue Type: Bug
Components: CQL/Syntax
Reporter: gloCalHelp.com
Cann't table and materialized view's timestamp column order by function well?
I am using cassandra3.11.3 on centos6.9 with python2.7.13, when I create a
table as below:
CREATE TABLE hygl_jcsj.hyjg_ods_yy_gps_novar4 (
clcph text,
dwsj timestamp,
bc decimal,
blbs decimal,
cjbzh text,
ckryid decimal,
clid decimal,
clmc text,
ddfx decimal,
ddrq timestamp,
ddsj text,
dlzbs decimal,
dwrq timestamp,
dwsk text,
fcsxh decimal,
fwj decimal,
gd decimal,
gdjd decimal,
gdwd decimal,
jd decimal,
jsdlc decimal,
jszjl decimal,
jxzjl decimal,
kxbs decimal,
sfaxlxs decimal,
sfcs decimal,
sjgxsj timestamp,
sjid text,
sjlx decimal,
sjlyxt decimal,
sjsfzh text,
sjwtid text,
sjxm text,
sjzlfj decimal,
sssd decimal,
szzdid decimal,
szzdmc text,
szzdxh decimal,
wd decimal,
xlbm text,
xlid decimal,
xlmc text,
xslc decimal,
xxfssj timestamp,
xxjssj timestamp,
xxrksj timestamp,
xzzdid decimal,
xzzdmc text,
xzzdxh decimal,
yxfx decimal,
yygpsxxjlid decimal,
yyzt decimal,
PRIMARY KEY (clcph, dwsj)
) WITH CLUSTERING ORDER BY (dwsj ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = \{'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = 'GPS数据'
AND compaction = \{'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = \{'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.0
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 360
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
the column dwsj is order by nature order of ASC, but when I use cqlsh -e
"select clcph,dwsj from hygl_jcsj.hyjg_ods_yy_gps_novar4 limit 18",
the result is:
| clcph \| dwsj| | | | |
|-+-| | | | |
| a85161782800835 \| 2019-06-27 11:39:42.00+| | | | |
| a85161785390963 \| 2019-06-27 13:06:54.00+| | | | |
| a8516178847003 \| 2019-06-25 10:51:18.00+| | | | |
| a8516178847003 \| 2019-06-27 10:06:56.00+| | | | |
| a85161785095735 \| 2019-06-27 12:55:55.00+| | | | |
| a85161783068534 \| 2019-06-27 11:48:24.00+| | | | |
| a8516178475869 \| 2019-06-25 10:51:18.00+| | | | |
| a8516178475869 \| 2019-06-27 09:53:04.00+| | | | |
| a85161781283975 \| 2019-06-27 10:23:22.00+| | | | |
| a8516178463883 \| 2019-06-25 10:51:18.00+| | | | |
| a8516178463883 \| 2019-06-27 09:52:35.00+| | | | |
| a85161781409966 \| 2019-06-27 10:28:02.00+| | | | |
| a85161782554262 \| 2019-06-27 11:31:15.00+0
[jira] [Commented] (CASSANDRA-11626) cqlsh fails and exits on non-ascii chars
[
https://issues.apache.org/jira/browse/CASSANDRA-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874618#comment-16874618
]
gloCalHelp.com commented on CASSANDRA-11626:
I have found the solution on csdn net, in order to thanks author and for the
new coming newbie, put the link here:
[https://blog.csdn.net/l1028386804/article/details/78976807] , the 1st method
is ok on Centos6.9 with python2.7
> cqlsh fails and exits on non-ascii chars
>
>
> Key: CASSANDRA-11626
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11626
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
>Reporter: Robert Stupp
>Assignee: Tyler Hobbs
>Priority: Low
> Labels: cqlsh
> Fix For: 2.2.7, 3.0.7, 3.7
>
>
> Just seen on cqlsh on current trunk:
> To repro, copy {{ä}} (german umlaut) to cqlsh and press return.
> cqlsh errors out and immediately exits.
> {code}
> $ bin/cqlsh
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.1.13-SNAPSHOT | CQL spec 3.2.1 | Native protocol
> v3]
> Use HELP for help.
> cqlsh> ä
> Invalid syntax at line 1, char 1
> Traceback (most recent call last):
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2636, in
>
> main(*read_options(sys.argv[1:], os.environ))
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2625, in main
> shell.cmdloop()
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 1114, in
> cmdloop
> if self.onecmd(self.statement.getvalue()):
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 1139, in onecmd
> self.printerr(' %s' % statementline)
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2314, in
> printerr
> self.writeresult(text, color, newline=newline, out=sys.stderr)
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2303, in
> writeresult
> out.write(self.applycolor(str(text), color) + ('\n' if newline else ''))
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position
> 2: ordinal not in range(128)
> $
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-11626) cqlsh fails and exits on non-ascii chars
[
https://issues.apache.org/jira/browse/CASSANDRA-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873742#comment-16873742
]
gloCalHelp.com edited comment on CASSANDRA-11626 at 6/27/19 1:23 AM:
-
I am using cqlsh 5.0.1 now with cassandra 3.11.3, and also has the error as
below,
@[~pauloricardomg] what are your steps to solve these decode errors? I cann't
find in the above.
command: bin/cqlsh hadoop4 -u **-p **--encoding utf8 -e "select * from
HYGL_JCSJ.hyjg_ods_yy_gps_novar3 where clcph='黑A00888D' and
dwsj='2019-06-2509:57:19';"
Error::1:'ascii' codec can't decode byte 0xe9 in position 60: ordinal
not in range(128)
was (Author: glocalhelp.com):
I am using cqlsh 5.0.1 now with cassandra 3.11.3, and also has the error as
below,
what are your steps to solve these decode errors? I cann't find in the above.
command: bin/cqlsh hadoop4 -u **-p **--encoding utf8 -e "select * from
HYGL_JCSJ.hyjg_ods_yy_gps_novar3 where clcph='黑A00888D' and
dwsj='2019-06-2509:57:19';"
Error::1:'ascii' codec can't decode byte 0xe9 in position 60: ordinal
not in range(128)
> cqlsh fails and exits on non-ascii chars
>
>
> Key: CASSANDRA-11626
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11626
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
>Reporter: Robert Stupp
>Assignee: Tyler Hobbs
>Priority: Low
> Labels: cqlsh
> Fix For: 2.2.7, 3.0.7, 3.7
>
>
> Just seen on cqlsh on current trunk:
> To repro, copy {{ä}} (german umlaut) to cqlsh and press return.
> cqlsh errors out and immediately exits.
> {code}
> $ bin/cqlsh
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.1.13-SNAPSHOT | CQL spec 3.2.1 | Native protocol
> v3]
> Use HELP for help.
> cqlsh> ä
> Invalid syntax at line 1, char 1
> Traceback (most recent call last):
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2636, in
>
> main(*read_options(sys.argv[1:], os.environ))
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2625, in main
> shell.cmdloop()
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 1114, in
> cmdloop
> if self.onecmd(self.statement.getvalue()):
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 1139, in onecmd
> self.printerr(' %s' % statementline)
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2314, in
> printerr
> self.writeresult(text, color, newline=newline, out=sys.stderr)
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2303, in
> writeresult
> out.write(self.applycolor(str(text), color) + ('\n' if newline else ''))
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position
> 2: ordinal not in range(128)
> $
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-11626) cqlsh fails and exits on non-ascii chars
[
https://issues.apache.org/jira/browse/CASSANDRA-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873742#comment-16873742
]
gloCalHelp.com commented on CASSANDRA-11626:
I am using cqlsh 5.0.1 now with cassandra 3.11.3, and also has the error as
below,
what are your steps to solve these decode errors? I cann't find in the above.
command: bin/cqlsh hadoop4 -u **-p **--encoding utf8 -e "select * from
HYGL_JCSJ.hyjg_ods_yy_gps_novar3 where clcph='黑A00888D' and
dwsj='2019-06-2509:57:19';"
Error::1:'ascii' codec can't decode byte 0xe9 in position 60: ordinal
not in range(128)
> cqlsh fails and exits on non-ascii chars
>
>
> Key: CASSANDRA-11626
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11626
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
>Reporter: Robert Stupp
>Assignee: Tyler Hobbs
>Priority: Low
> Labels: cqlsh
> Fix For: 2.2.7, 3.0.7, 3.7
>
>
> Just seen on cqlsh on current trunk:
> To repro, copy {{ä}} (german umlaut) to cqlsh and press return.
> cqlsh errors out and immediately exits.
> {code}
> $ bin/cqlsh
> Connected to Test Cluster at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.1.13-SNAPSHOT | CQL spec 3.2.1 | Native protocol
> v3]
> Use HELP for help.
> cqlsh> ä
> Invalid syntax at line 1, char 1
> Traceback (most recent call last):
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2636, in
>
> main(*read_options(sys.argv[1:], os.environ))
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2625, in main
> shell.cmdloop()
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 1114, in
> cmdloop
> if self.onecmd(self.statement.getvalue()):
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 1139, in onecmd
> self.printerr(' %s' % statementline)
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2314, in
> printerr
> self.writeresult(text, color, newline=newline, out=sys.stderr)
> File "/Users/snazy/devel/cassandra/trunk/bin/cqlsh.py", line 2303, in
> writeresult
> out.write(self.applycolor(str(text), color) + ('\n' if newline else ''))
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position
> 2: ordinal not in range(128)
> $
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15183) Not Return Any Error When Insert A Lacking Decimal Value
[ https://issues.apache.org/jira/browse/CASSANDRA-15183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873180#comment-16873180 ] gloCalHelp.com commented on CASSANDRA-15183: Sorry, the reproduce steps are as below: 1, extract the apache-cassandra-3.11.3-bin.tar.gz on Centos6.9 with python2.7 installed.(although I am running a 3 datanodes with password authentication, a single node would be the same to reproduce the error, wounldn't it?) 2, in the bash, use cqlsh -f to run the attachments file of "inHadoopTablehygl_jcsj.hyjg_ods_yy_gps_novar3.sql" 3, use cqlsh -e to the insert sql in file of "long and problem insert.sql" . the error would reproduce as shown before.[^InsertLongSQLWithErrorDecode.zip] But I can succeed in inserting a short sql, which is only insert the above SQL's front 3 columns . > Not Return Any Error When Insert A Lacking Decimal Value > > > Key: CASSANDRA-15183 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15183 > Project: Cassandra > Issue Type: Bug > Components: CQL/Syntax >Reporter: gloCalHelp.com >Priority: Normal > Attachments: InsertLongSQLWithErrorDecode.zip > > > when using cqlsh as the first command in the attachment, no any error message > return or report in syste.log or debug.log. > !NotReturnAnyErrorWhenInsertALackingDecimalValue.GIF! > Not Return Any Error When Insert A Lacking Decimal Value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15183) Not Return Any Error When Insert A Lacking Decimal Value
[ https://issues.apache.org/jira/browse/CASSANDRA-15183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gloCalHelp.com updated CASSANDRA-15183: --- Attachment: InsertLongSQLWithErrorDecode.zip > Not Return Any Error When Insert A Lacking Decimal Value > > > Key: CASSANDRA-15183 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15183 > Project: Cassandra > Issue Type: Bug > Components: CQL/Syntax >Reporter: gloCalHelp.com >Priority: Normal > Attachments: InsertLongSQLWithErrorDecode.zip > > > when using cqlsh as the first command in the attachment, no any error message > return or report in syste.log or debug.log. > !NotReturnAnyErrorWhenInsertALackingDecimalValue.GIF! > Not Return Any Error When Insert A Lacking Decimal Value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-10948) CQLSH error when trying to insert non-ascii statement
[
https://issues.apache.org/jira/browse/CASSANDRA-10948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873132#comment-16873132
]
gloCalHelp.com commented on CASSANDRA-10948:
Dear Sir Paulo Motta,
I cann't find this issue's solution steps, would you like to tell me the
solution steps?
By the way, this method seems just only solving client query of select?
doesn't it?
and I have found other issue on insert query, which has submitted in
https://issues.apache.org/jira/browse/CASSANDRA-15182?filter=-2
> CQLSH error when trying to insert non-ascii statement
> -
>
> Key: CASSANDRA-10948
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10948
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
>Reporter: Matthieu Nantern
>Assignee: Matthieu Nantern
>Priority: Low
> Labels: lhf
> Fix For: 2.2.5, 3.0.3, 3.3
>
> Attachments: patch_CASSANDRA-10948
>
>
> We recently upgraded Cassandra to v2.2.4 with CQLSH 5.0.1 and we are now
> unable to import some CQL file (with French character like 'ê'). It was
> working on v2.0.12.
> The issue:
> {noformat}
> Using CQL driver: '/OPT/cassandra/dsc-cassandra-2.2.4/bin/../lib/cassandra-driver-internal-only-3.0.0-6af642d.zip/cassandra-driver-3.0.0-6af642d/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Traceback (most recent call last):
> File "/OPT/cassandra/dsc-cassandra/bin/cqlsh.py", line 1110, in onecmd
> self.handle_statement(st, statementtext)
> File "/OPT/cassandra/dsc-cassandra/bin/cqlsh.py", line 1135, in
> handle_statement
> readline.add_history(new_hist)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xea' in position
> 7192: ordinal not in range(128)
> {noformat}
> The issue was corrected by changing line 1135 of cqlsh.py (but I don't know
> if it's the correct way to do it):
> readline.add_history(new_hist) ->
> readline.add_history(new_hist.encode('utf8'))
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60:
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872865#comment-16872865
]
gloCalHelp.com edited comment on CASSANDRA-15182 at 6/26/19 2:03 AM:
-
Thanks Sir Michael, because the report error position is not correct, and
I don't know how to santize the insert sql, but the shorter one with a Chinese
character can be successfully inserted as below:
INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3 (clcph,dwsj,bc) VALUES
('黑A00888D','2019-06-25 09:57:19',0);", and my LANG environment is really this:
bash-4.1$ echo $LANG
en_US.UTF-8
Is there anyone who can tell me how to make cqlsh report the correct
position of wrong sql except using --debug variable?
was (Author: glocalhelp.com):
Thanks Sir Michael, because the report error position is not correct, and
I don't know how to santize the insert sql, but the shorter one with a Chinese
character can be successfully inserted as below:
INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3 (clcph,dwsj,bc) VALUES
('黑A00888D','2019-06-25 09:57:19',0);"
Is there anyone who can tell me how to make cqlsh report the correct
position of wrong sql except using --debug variable?
> cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input,
> errors, True):1:'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60: ordi
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872865#comment-16872865
]
gloCalHelp.com commented on CASSANDRA-15182:
Thanks Sir Michael, because the report error position is not correct, and
I don't know how to santize the insert sql, but the shorter one with a Chinese
character can be successfully inserted as below:
INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3 (clcph,dwsj,bc) VALUES
('黑A00888D','2019-06-25 09:57:19',0);"
Is there anyone who can tell me how to make cqlsh report the correct
position of wrong sql except using --debug variable?
> cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input,
> errors, True):1:'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15183) Not Return Any Error When Insert A Lacking Decimal Value
gloCalHelp.com created CASSANDRA-15183: -- Summary: Not Return Any Error When Insert A Lacking Decimal Value Key: CASSANDRA-15183 URL: https://issues.apache.org/jira/browse/CASSANDRA-15183 Project: Cassandra Issue Type: Bug Components: CQL/Syntax Reporter: gloCalHelp.com when using cqlsh as the first command in the attachment, no any error message return or report in syste.log or debug.log. !NotReturnAnyErrorWhenInsertALackingDecimalValue.GIF! Not Return Any Error When Insert A Lacking Decimal Value. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60: ordina
gloCalHelp.com created CASSANDRA-15182:
--
Summary: cqlsh utf_8.py, line 16, in decode return
codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode
character u'\u9ed1' in position 60: ordinal not in range(128)
Key: CASSANDRA-15182
URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
Project: Cassandra
Issue Type: Bug
Components: CQL/Interpreter
Reporter: gloCalHelp.com
I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
when I run this cql command: bin/cqlsh hadoop4 -u dba -p LinJiaXin858 --debug
-e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
(clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
VALUES
('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
,796.0,2205,746,'null','null','null',0,'379');"
I get the error message as below:
Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
Traceback (most recent call last):
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
self.handle_statement(st, statementtext)
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in perform_statement
success, future = self.perform_simple_statement(stmt)
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
perform_simple_statement
self.printerr(unicode(err.__class__.__name__) + u": " +
err.message.decode(encoding='utf-8'))
File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in position
60: ordinal not in range(128)
this issue seems different with the select command issue on
https://issues.apache.org/jira/browse/CASSANDRA-10875
and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py , can
anyone hurry up to teach me?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
