[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

2019-06-26 Thread Yuki Morishita (JIRA)


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

Yuki Morishita commented on CASSANDRA-15182:


Hi [~gloCalHelp.com],

cqlsh is complaining when it is trying to output an error, since your original 
CQL syntax is wrong (you have to provide some values for columns not like 
',,,'.)

'Short' cql did not contain syntax error so it went through.

 

> 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] [Comment Edited] (CASSANDRA-11626) cqlsh fails and exits on non-ascii chars

2019-06-26 Thread gloCalHelp.com (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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

2019-06-26 Thread gloCalHelp.com (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Updated] (CASSANDRA-15185) Update quilt patches for 4.0

2019-06-26 Thread Michael Shuler (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-15185:
---
Status: Ready to Commit  (was: Review In Progress)

> Update quilt patches for 4.0
> 
>
> Key: CASSANDRA-15185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15185
> Project: Cassandra
>  Issue Type: Task
>  Components: Build, Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: High
> Attachments: 0001-Update-log-directory-patch-for-4.0-deb-package.patch
>
>
> {noformat}
> (trunk)mshuler@hana:~/git/cassandra$ dpkg-buildpackage -uc -us
> <...>
> dpkg-source: info: building cassandra in cassandra_4.0.dsc
>  debian/rules build
> QUILT_PATCHES=debian/patches \
> quilt --quiltrc /dev/null push -a || test $? = 2
> Applying patch cassandra_logdir_fix.diff
> patching file bin/cassandra
> Hunk #1 FAILED at 171.
> 1 out of 1 hunk FAILED -- rejects in file bin/cassandra
> patching file conf/cassandra-env.sh
> Patch cassandra_logdir_fix.diff does not apply (enforce with -f)
> make: *** [/usr/share/quilt/quilt.make:18: debian/stamp-patched] Error 1
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> {noformat}



--
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-15185) Update quilt patches for 4.0

2019-06-26 Thread Michael Shuler (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-15185:
---
Reviewers: Jon Haddad
   Status: Review In Progress  (was: Patch Available)

(got a +1 on slack for the patch)

> Update quilt patches for 4.0
> 
>
> Key: CASSANDRA-15185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15185
> Project: Cassandra
>  Issue Type: Task
>  Components: Build, Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: High
> Attachments: 0001-Update-log-directory-patch-for-4.0-deb-package.patch
>
>
> {noformat}
> (trunk)mshuler@hana:~/git/cassandra$ dpkg-buildpackage -uc -us
> <...>
> dpkg-source: info: building cassandra in cassandra_4.0.dsc
>  debian/rules build
> QUILT_PATCHES=debian/patches \
> quilt --quiltrc /dev/null push -a || test $? = 2
> Applying patch cassandra_logdir_fix.diff
> patching file bin/cassandra
> Hunk #1 FAILED at 171.
> 1 out of 1 hunk FAILED -- rejects in file bin/cassandra
> patching file conf/cassandra-env.sh
> Patch cassandra_logdir_fix.diff does not apply (enforce with -f)
> make: *** [/usr/share/quilt/quilt.make:18: debian/stamp-patched] Error 1
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> {noformat}



--
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-15185) Update quilt patches for 4.0

2019-06-26 Thread Michael Shuler (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-15185:
---
  Fix Version/s: 4.0
Source Control Link: 
https://github.com/apache/cassandra/commit/61b77ac2b01098776a1bea15a775701230028514
 Status: Resolved  (was: Ready to Commit)
 Resolution: Fixed

> Update quilt patches for 4.0
> 
>
> Key: CASSANDRA-15185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15185
> Project: Cassandra
>  Issue Type: Task
>  Components: Build, Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: High
> Fix For: 4.0
>
> Attachments: 0001-Update-log-directory-patch-for-4.0-deb-package.patch
>
>
> {noformat}
> (trunk)mshuler@hana:~/git/cassandra$ dpkg-buildpackage -uc -us
> <...>
> dpkg-source: info: building cassandra in cassandra_4.0.dsc
>  debian/rules build
> QUILT_PATCHES=debian/patches \
> quilt --quiltrc /dev/null push -a || test $? = 2
> Applying patch cassandra_logdir_fix.diff
> patching file bin/cassandra
> Hunk #1 FAILED at 171.
> 1 out of 1 hunk FAILED -- rejects in file bin/cassandra
> patching file conf/cassandra-env.sh
> Patch cassandra_logdir_fix.diff does not apply (enforce with -f)
> make: *** [/usr/share/quilt/quilt.make:18: debian/stamp-patched] Error 1
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> {noformat}



--
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



[cassandra] branch trunk updated: Update log directory patch for 4.0 deb package

2019-06-26 Thread mshuler
This is an automated email from the ASF dual-hosted git repository.

mshuler pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/trunk by this push:
 new 61b77ac  Update log directory patch for 4.0 deb package
61b77ac is described below

commit 61b77ac2b01098776a1bea15a775701230028514
Author: Michael Shuler 
AuthorDate: Wed Jun 26 14:30:39 2019 -0500

Update log directory patch for 4.0 deb package

Patch by Michael Shuler; Reviewed by Jon Haddad for CASSANDRA-15185
---
 debian/patches/cassandra_logdir_fix.diff | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/debian/patches/cassandra_logdir_fix.diff 
b/debian/patches/cassandra_logdir_fix.diff
index d75553c..8597331 100644
--- a/debian/patches/cassandra_logdir_fix.diff
+++ b/debian/patches/cassandra_logdir_fix.diff
@@ -1,14 +1,14 @@
 --- a/bin/cassandra
 +++ b/bin/cassandra
-@@ -171,7 +171,7 @@
- props="$3"
- class="$4"
- cassandra_parms="-Dlogback.configurationFile=logback.xml"
--cassandra_parms="$cassandra_parms -Dcassandra.logdir=$CASSANDRA_HOME/logs"
-+cassandra_parms="$cassandra_parms -Dcassandra.logdir=/var/log/cassandra"
- cassandra_parms="$cassandra_parms 
-Dcassandra.storagedir=$cassandra_storagedir"
+@@ -109,7 +109,7 @@
+ fi
+ 
+ if [ -z "$CASSANDRA_LOG_DIR" ]; then
+-  CASSANDRA_LOG_DIR=$CASSANDRA_HOME/logs
++  CASSANDRA_LOG_DIR=/var/log/cassandra
+ fi
  
- if [ "x$pidpath" != "x" ]; then
+ # Special-case path variables.
 --- a/conf/cassandra-env.sh
 +++ b/conf/cassandra-env.sh
 @@ -93,16 +93,16 @@


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15185) Update quilt patches for 4.0

2019-06-26 Thread Michael Shuler (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-15185:
---
Test and Documentation Plan: build deb package
 Status: Patch Available  (was: Open)

> Update quilt patches for 4.0
> 
>
> Key: CASSANDRA-15185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15185
> Project: Cassandra
>  Issue Type: Task
>  Components: Build, Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: High
> Attachments: 0001-Update-log-directory-patch-for-4.0-deb-package.patch
>
>
> {noformat}
> (trunk)mshuler@hana:~/git/cassandra$ dpkg-buildpackage -uc -us
> <...>
> dpkg-source: info: building cassandra in cassandra_4.0.dsc
>  debian/rules build
> QUILT_PATCHES=debian/patches \
> quilt --quiltrc /dev/null push -a || test $? = 2
> Applying patch cassandra_logdir_fix.diff
> patching file bin/cassandra
> Hunk #1 FAILED at 171.
> 1 out of 1 hunk FAILED -- rejects in file bin/cassandra
> patching file conf/cassandra-env.sh
> Patch cassandra_logdir_fix.diff does not apply (enforce with -f)
> make: *** [/usr/share/quilt/quilt.make:18: debian/stamp-patched] Error 1
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> {noformat}



--
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-15185) Update quilt patches for 4.0

2019-06-26 Thread Michael Shuler (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-15185:
---
Attachment: 0001-Update-log-directory-patch-for-4.0-deb-package.patch

> Update quilt patches for 4.0
> 
>
> Key: CASSANDRA-15185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15185
> Project: Cassandra
>  Issue Type: Task
>  Components: Build, Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: High
> Attachments: 0001-Update-log-directory-patch-for-4.0-deb-package.patch
>
>
> {noformat}
> (trunk)mshuler@hana:~/git/cassandra$ dpkg-buildpackage -uc -us
> <...>
> dpkg-source: info: building cassandra in cassandra_4.0.dsc
>  debian/rules build
> QUILT_PATCHES=debian/patches \
> quilt --quiltrc /dev/null push -a || test $? = 2
> Applying patch cassandra_logdir_fix.diff
> patching file bin/cassandra
> Hunk #1 FAILED at 171.
> 1 out of 1 hunk FAILED -- rejects in file bin/cassandra
> patching file conf/cassandra-env.sh
> Patch cassandra_logdir_fix.diff does not apply (enforce with -f)
> make: *** [/usr/share/quilt/quilt.make:18: debian/stamp-patched] Error 1
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> {noformat}



--
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-15185) Update quilt patches for 4.0

2019-06-26 Thread Michael Shuler (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-15185:
---
 Complexity: Normal
   Priority: High  (was: Normal)
Change Category: Quality Assurance
 Status: Open  (was: Triage Needed)

> Update quilt patches for 4.0
> 
>
> Key: CASSANDRA-15185
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15185
> Project: Cassandra
>  Issue Type: Task
>  Components: Build, Packaging
>Reporter: Michael Shuler
>Assignee: Michael Shuler
>Priority: High
>
> {noformat}
> (trunk)mshuler@hana:~/git/cassandra$ dpkg-buildpackage -uc -us
> <...>
> dpkg-source: info: building cassandra in cassandra_4.0.dsc
>  debian/rules build
> QUILT_PATCHES=debian/patches \
> quilt --quiltrc /dev/null push -a || test $? = 2
> Applying patch cassandra_logdir_fix.diff
> patching file bin/cassandra
> Hunk #1 FAILED at 171.
> 1 out of 1 hunk FAILED -- rejects in file bin/cassandra
> patching file conf/cassandra-env.sh
> Patch cassandra_logdir_fix.diff does not apply (enforce with -f)
> make: *** [/usr/share/quilt/quilt.make:18: debian/stamp-patched] Error 1
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
> {noformat}



--
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-15185) Update quilt patches for 4.0

2019-06-26 Thread Michael Shuler (JIRA)
Michael Shuler created CASSANDRA-15185:
--

 Summary: Update quilt patches for 4.0
 Key: CASSANDRA-15185
 URL: https://issues.apache.org/jira/browse/CASSANDRA-15185
 Project: Cassandra
  Issue Type: Task
  Components: Build, Packaging
Reporter: Michael Shuler
Assignee: Michael Shuler


{noformat}
(trunk)mshuler@hana:~/git/cassandra$ dpkg-buildpackage -uc -us
<...>
dpkg-source: info: building cassandra in cassandra_4.0.dsc
 debian/rules build
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch cassandra_logdir_fix.diff
patching file bin/cassandra
Hunk #1 FAILED at 171.
1 out of 1 hunk FAILED -- rejects in file bin/cassandra
patching file conf/cassandra-env.sh
Patch cassandra_logdir_fix.diff does not apply (enforce with -f)
make: *** [/usr/share/quilt/quilt.make:18: debian/stamp-patched] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
{noformat}



--
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-14466) Enable Direct I/O

2019-06-26 Thread Mulugeta Mammo (JIRA)


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

Mulugeta Mammo commented on CASSANDRA-14466:


[~snazy] The previous PR was several commits behind. Have created a new PR with 
no conflicts here: [https://github.com/apache/cassandra/pull/329]. Thanks!

> Enable Direct I/O 
> --
>
> Key: CASSANDRA-14466
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14466
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Legacy/Local Write-Read Paths
>Reporter: Mulugeta Mammo
>Assignee: Mulugeta Mammo
>Priority: Normal
>
> Hi,
> JDK 10 introduced a new API for Direct IO that enables applications to bypass 
> the file system cache and potentially improve performance. Details of this 
> feature can be found at [https://bugs.openjdk.java.net/browse/JDK-8164900].
> This patch uses the JDK 10 API to enable Direct IO for the Cassandra read 
> path. By default, we have disabled this feature; but it can be enabled using 
> a  new configuration parameter, enable_direct_io_for_read_path. We have 
> conducted a Cassandra read-only stress test and measured a throughput gain of 
> up to 60% on flash drives.
> The patch requires JDK 10 Cassandra Support - 
> https://issues.apache.org/jira/browse/CASSANDRA-9608 
> Please review the patch and let us know your feedback.
> Thanks,
> [^direct_io.patch]
>  



--
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



[cassandra] branch trunk updated: ninja fix merge error

2019-06-26 Thread clohfink
This is an automated email from the ASF dual-hosted git repository.

clohfink pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/trunk by this push:
 new ebe45c8  ninja fix merge error
ebe45c8 is described below

commit ebe45c8f9121aa614512a7101d3ee87ca1e2db16
Author: Chris Lohfink 
AuthorDate: Wed Jun 26 11:19:47 2019 -0500

ninja fix merge error
---
 src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java 
b/src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java
index 4fcc41a..abcdf87 100644
--- a/src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java
+++ b/src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java
@@ -34,7 +34,7 @@ public final class SystemViewsKeyspace extends VirtualKeyspace
 .add(new SSTableTasksTable(NAME))
 .add(new ThreadPoolsTable(NAME))
 .add(new InternodeOutboundTable(NAME))
-.add(new InternodeOutboundTable(NAME))
+.add(new InternodeInboundTable(NAME))
 .addAll(TableMetricTables.getAll(NAME))
 .build());
 }


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Comment Edited] (CASSANDRA-14670) Table Metrics Virtual Table

2019-06-26 Thread Chris Lohfink (JIRA)


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

Chris Lohfink edited comment on CASSANDRA-14670 at 6/26/19 4:18 PM:


Made recommended changes and Jon took another quick look.

Thanks, committed as 
[07ff9e57344f1d837e4aef3cbca26b953745bcd7|https://github.com/apache/cassandra/commit/07ff9e57344f1d837e4aef3cbca26b953745bcd7].


was (Author: cnlwsu):
Made recommended changes and Jon took another quick look.

Thanks, committed as 
[07ff9e57344f1d837e4aef3cbca26b953745bcd7|[https://github.com/apache/cassandra/commit/07ff9e57344f1d837e4aef3cbca26b953745bcd7]].

> Table Metrics Virtual Table
> ---
>
> Key: CASSANDRA-14670
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14670
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/CQL, Legacy/Observability
>Reporter: Chris Lohfink
>Assignee: Chris Lohfink
>Priority: Low
>  Labels: pull-request-available, virtual-tables
> Fix For: 4.0.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Different than CASSANDRA-14572 whose goal is to expose all metrics. This is 
> to expose a few hand tailored tables that are particularly useful in 
> debugging slow Cassandra instances (in my experience). These are useful in 
> finding out which table it is that is having issues if you see a node 
> performing poorly in general. This can kinda be figured out with cfstats 
> sorting and some clever bash-foo but its been a bit of a operational UX pain 
> for me personally for awhile.
> examples:
> {code}
> cqlsh> select * from system_views.max_partition_size limit 5;
>  max_partition_size | keyspace_name | table_name
> +---+
>  126934 |system | size_estimates
>9887 | system_schema |columns
>9887 | system_schema | tables
>6866 |system |  local
> 258 | keyspace1 |  standard1
> (5 rows)
> cqlsh> select * from system_views.local_reads limit 5 ;
>  count | keyspace_name | table_name  | 99th  | max   | median  | 
> per_second
> ---+---+-+---+---+-+
> 23 |system |   local | 186563160 | 186563160 | 1629722 |  
>   3.56101
> 22 | system_schema |  tables |   4055269 |   4055269 |  454826 |  
>   3.72452
> 14 | system_schema | columns |   1131752 |   1131752 |  545791 |  
>   2.37015
> 14 | system_schema | dropped_columns |126934 |126934 |   88148 |  
>   2.37015
> 14 | system_schema | indexes |219342 |219342 |  152321 |  
>   2.37015
> (5 rows)
> cqlsh> select * from system_views.coordinator_reads limit 5;
>  count | keyspace_name | table_name | 99th | max | median | per_second
> ---+---++--+-++
>  2 |system |  local |0 |   0 |  0 |   0.005324
>  1 |   system_auth |  roles |0 |   0 |  0 |   0.002662
>  0 | basic |   wide |0 |   0 |  0 |  0
>  0 | basic |  wide3 |0 |   0 |  0 |  0
>  0 | keyspace1 |   counter1 |0 |   0 |  0 |  0
> (5 rows)
> {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-14670) Table Metrics Virtual Table

2019-06-26 Thread Chris Lohfink (JIRA)


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

Chris Lohfink commented on CASSANDRA-14670:
---

Made recommended changes and Jon took another quick look.

Thanks, committed as 
[07ff9e57344f1d837e4aef3cbca26b953745bcd7|[https://github.com/apache/cassandra/commit/07ff9e57344f1d837e4aef3cbca26b953745bcd7]].

> Table Metrics Virtual Table
> ---
>
> Key: CASSANDRA-14670
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14670
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/CQL, Legacy/Observability
>Reporter: Chris Lohfink
>Assignee: Chris Lohfink
>Priority: Low
>  Labels: pull-request-available, virtual-tables
> Fix For: 4.0.x
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Different than CASSANDRA-14572 whose goal is to expose all metrics. This is 
> to expose a few hand tailored tables that are particularly useful in 
> debugging slow Cassandra instances (in my experience). These are useful in 
> finding out which table it is that is having issues if you see a node 
> performing poorly in general. This can kinda be figured out with cfstats 
> sorting and some clever bash-foo but its been a bit of a operational UX pain 
> for me personally for awhile.
> examples:
> {code}
> cqlsh> select * from system_views.max_partition_size limit 5;
>  max_partition_size | keyspace_name | table_name
> +---+
>  126934 |system | size_estimates
>9887 | system_schema |columns
>9887 | system_schema | tables
>6866 |system |  local
> 258 | keyspace1 |  standard1
> (5 rows)
> cqlsh> select * from system_views.local_reads limit 5 ;
>  count | keyspace_name | table_name  | 99th  | max   | median  | 
> per_second
> ---+---+-+---+---+-+
> 23 |system |   local | 186563160 | 186563160 | 1629722 |  
>   3.56101
> 22 | system_schema |  tables |   4055269 |   4055269 |  454826 |  
>   3.72452
> 14 | system_schema | columns |   1131752 |   1131752 |  545791 |  
>   2.37015
> 14 | system_schema | dropped_columns |126934 |126934 |   88148 |  
>   2.37015
> 14 | system_schema | indexes |219342 |219342 |  152321 |  
>   2.37015
> (5 rows)
> cqlsh> select * from system_views.coordinator_reads limit 5;
>  count | keyspace_name | table_name | 99th | max | median | per_second
> ---+---++--+-++
>  2 |system |  local |0 |   0 |  0 |   0.005324
>  1 |   system_auth |  roles |0 |   0 |  0 |   0.002662
>  0 | basic |   wide |0 |   0 |  0 |  0
>  0 | basic |  wide3 |0 |   0 |  0 |  0
>  0 | keyspace1 |   counter1 |0 |   0 |  0 |  0
> (5 rows)
> {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



[cassandra] branch trunk updated: Add Table Metrics Virtual Table Patch by Chris Lohfink; Reviewed by Jon Haddad for CASSANDRA-14670

2019-06-26 Thread clohfink
This is an automated email from the ASF dual-hosted git repository.

clohfink pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git


The following commit(s) were added to refs/heads/trunk by this push:
 new 07ff9e5  Add Table Metrics Virtual Table Patch by Chris Lohfink; 
Reviewed by Jon Haddad for CASSANDRA-14670
07ff9e5 is described below

commit 07ff9e57344f1d837e4aef3cbca26b953745bcd7
Author: Chris Lohfink 
AuthorDate: Fri Jun 7 16:27:01 2019 -0500

Add Table Metrics Virtual Table
Patch by Chris Lohfink; Reviewed by Jon Haddad for CASSANDRA-14670
---
 .../cassandra/db/virtual/SystemViewsKeyspace.java  |  17 ++-
 .../cassandra/db/virtual/TableMetricTables.java| 169 +
 2 files changed, 179 insertions(+), 7 deletions(-)

diff --git a/src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java 
b/src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java
index fa1ddae..4fcc41a 100644
--- a/src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java
+++ b/src/java/org/apache/cassandra/db/virtual/SystemViewsKeyspace.java
@@ -27,12 +27,15 @@ public final class SystemViewsKeyspace extends 
VirtualKeyspace
 
 private SystemViewsKeyspace()
 {
-super(NAME, ImmutableList.of(new CachesTable(NAME),
- new ClientsTable(NAME),
- new SettingsTable(NAME),
- new SSTableTasksTable(NAME),
- new ThreadPoolsTable(NAME),
- new InternodeOutboundTable(NAME),
- new InternodeInboundTable(NAME)));
+super(NAME, new ImmutableList.Builder()
+.add(new CachesTable(NAME))
+.add(new ClientsTable(NAME))
+.add(new SettingsTable(NAME))
+.add(new SSTableTasksTable(NAME))
+.add(new ThreadPoolsTable(NAME))
+.add(new InternodeOutboundTable(NAME))
+.add(new InternodeOutboundTable(NAME))
+.addAll(TableMetricTables.getAll(NAME))
+.build());
 }
 }
diff --git a/src/java/org/apache/cassandra/db/virtual/TableMetricTables.java 
b/src/java/org/apache/cassandra/db/virtual/TableMetricTables.java
new file mode 100644
index 000..acae2d0
--- /dev/null
+++ b/src/java/org/apache/cassandra/db/virtual/TableMetricTables.java
@@ -0,0 +1,169 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.cassandra.db.virtual;
+
+import java.util.Collection;
+import java.util.function.Function;
+
+import com.google.common.base.Preconditions;
+import com.google.common.collect.ImmutableList;
+
+import com.codahale.metrics.Counter;
+import com.codahale.metrics.Counting;
+import com.codahale.metrics.Gauge;
+import com.codahale.metrics.Histogram;
+import com.codahale.metrics.Metered;
+import com.codahale.metrics.Metric;
+import com.codahale.metrics.Sampling;
+import com.codahale.metrics.Snapshot;
+import com.codahale.metrics.Timer;
+import org.apache.cassandra.db.ColumnFamilyStore;
+import org.apache.cassandra.db.Keyspace;
+import org.apache.cassandra.db.marshal.AbstractType;
+import org.apache.cassandra.db.marshal.CompositeType;
+import org.apache.cassandra.db.marshal.DoubleType;
+import org.apache.cassandra.db.marshal.Int32Type;
+import org.apache.cassandra.db.marshal.LongType;
+import org.apache.cassandra.db.marshal.ReversedType;
+import org.apache.cassandra.db.marshal.UTF8Type;
+import org.apache.cassandra.dht.IPartitioner;
+import org.apache.cassandra.dht.LocalPartitioner;
+import org.apache.cassandra.metrics.TableMetrics;
+import org.apache.cassandra.schema.TableMetadata;
+
+/**
+ * Contains multiple the Table Metric virtual tables. This is not a direct 
wrapper over the Metrics like with JMX but a
+ * view to the metrics so that the underlying mechanism can change but still 
give same appearance (like nodetool).
+ */
+public class TableMetricTables
+{
+private final static String KEYSPACE_NAME = "keyspace_name";
+private final static String TABLE_NAME = "table_name";
+

[jira] [Commented] (CASSANDRA-15013) Message Flusher queue can grow unbounded, potentially running JVM out of memory

2019-06-26 Thread Benedict (JIRA)


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

Benedict commented on CASSANDRA-15013:
--

Thanks [~sumanth.pasupuleti].  I think this is very close to commit.

I've pushed a small number of extra suggestions 
[here|https://github.com/belliottsmith/cassandra/tree/15013-suggestions].  
Mostly just minor stylistic simplifications, as well as a modification to of 
back pressure deployed to simply the number of connections currently 
experiencing back pressure, since it's not entirely clear how an operator would 
meaningfully interpret the number of times it was independently applied (since 
it would be applied more often for small messages than large ones)

Let me know what you think, and we can hopefully see about merging this soon.

> Message Flusher queue can grow unbounded, potentially running JVM out of 
> memory
> ---
>
> Key: CASSANDRA-15013
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15013
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Client
>Reporter: Sumanth Pasupuleti
>Assignee: Sumanth Pasupuleti
>Priority: Normal
>  Labels: pull-request-available
> Fix For: 4.0, 3.0.x, 3.11.x
>
> Attachments: BlockedEpollEventLoopFromHeapDump.png, 
> BlockedEpollEventLoopFromThreadDump.png, RequestExecutorQueueFull.png, heap 
> dump showing each ImmediateFlusher taking upto 600MB.png
>
>
> This is a follow-up ticket out of CASSANDRA-14855, to make the Flusher queue 
> bounded, since, in the current state, items get added to the queue without 
> any checks on queue size, nor with any checks on netty outbound buffer to 
> check the isWritable state.
> We are seeing this issue hit our production 3.0 clusters quite often.



--
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-15176) Fix PagingState deserialization when the state was serialized using protocol version different from current session's

2019-06-26 Thread Aleksey Yeschenko (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-15176:
--
  Fix Version/s: 4.0
 3.11.5
 3.0.19
Source Control Link: 
[dad82fbd30c8b87c4c9fa02abc6796ba8c2bf99a|https://github.com/apache/cassandra/commit/dad82fbd30c8b87c4c9fa02abc6796ba8c2bf99a]
  Since Version: 3.0.0
 Status: Resolved  (was: Ready to Commit)
 Resolution: Fixed

Cheers, committed to 3.0 as 
[dad82fbd30c8b87c4c9fa02abc6796ba8c2bf99a|https://github.com/apache/cassandra/commit/dad82fbd30c8b87c4c9fa02abc6796ba8c2bf99a]
 and merged with 3.11 and trunk.

> Fix PagingState deserialization when the state was serialized using protocol 
> version different from current session's
> -
>
> Key: CASSANDRA-15176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15176
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Client
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Fix For: 3.0.19, 3.11.5, 4.0
>
>
> 3.0 and native protocol V4 introduced a change to how {{PagingState}} is 
> serialized. Unfortunately that can break requests during upgrades: since 
> paging states are opaque, it's possible for a client to receive a paging 
> state encoded as V3 on a 2.1 node, and then send it to a 3.0 node on a V4 
> session. The version of the current session will be used to deserialize the 
> paging state, instead of the actual version used to serialize it, and the 
> request will fail.
> This is obviously sub-optimal, but also avoidable. This JIRA fixes one half 
> of the problem: 3.0 failing to deserialize 'mislabeled' paging states. We can 
> do this by inspecting the byte buffer to verify if it's been indeed 
> serialized with the protocol version used by the session, and if not, use the 
> other method of deserialization.
> It should be noted that we list this as a 'known limitation' somewhere, but 
> really this is an upgrade-blocking bug for some users of C*.



--
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



[cassandra] 01/01: Merge branch 'cassandra-3.11' into trunk

2019-06-26 Thread aleksey
This is an automated email from the ASF dual-hosted git repository.

aleksey pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git

commit 3261b23a789f595414f5e2d11545c87b97c44e32
Merge: 225fa86 5514696
Author: Aleksey Yeshchenko 
AuthorDate: Wed Jun 26 15:30:41 2019 +0100

Merge branch 'cassandra-3.11' into trunk

 CHANGES.txt|   3 +
 .../apache/cassandra/io/util/DataOutputBuffer.java |  13 +
 .../cassandra/service/pager/PagingState.java   | 284 -
 test/unit/org/apache/cassandra/Util.java   |   7 +-
 .../apache/cassandra/service/QueryPagerTest.java   |  35 +--
 .../cassandra/service/pager/PagingStateTest.java   |  42 ++-
 6 files changed, 295 insertions(+), 89 deletions(-)

diff --cc CHANGES.txt
index 6435d03,e2aa652..de8d648
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -366,8 -3,13 +366,11 @@@
   * Fixed nodetool cfstats printing index name twice (CASSANDRA-14903)
   * Add flag to disable SASI indexes, and warnings on creation 
(CASSANDRA-14866)
  Merged from 3.0:
+  * Handle paging states serialized with a different version than the 
session's (CASSANDRA-15176)
+  * Throw IOE instead of asserting on unsupporter peer versions 
(CASSANDRA-15066)
+  * Update token metadata when handling MOVING/REMOVING_TOKEN events 
(CASSANDRA-15120)
   * Add ability to customize cassandra log directory using $CASSANDRA_LOG_DIR 
(CASSANDRA-15090)
 - * Skip cells with illegal column names when reading legacy sstables 
(CASSANDRA-15086)
   * Fix assorted gossip races and add related runtime checks (CASSANDRA-15059)
 - * Fix mixed mode partition range scans with limit (CASSANDRA-15072)
   * cassandra-stress works with frozen collections: list and set 
(CASSANDRA-14907)
   * Fix handling FS errors on writing and reading flat files - LogTransaction 
and hints (CASSANDRA-15053)
   * Avoid double closing the iterator to avoid overcounting the number of 
requests (CASSANDRA-15058)
diff --cc src/java/org/apache/cassandra/service/pager/PagingState.java
index f036f96,9b7eccf..8df2366
--- a/src/java/org/apache/cassandra/service/pager/PagingState.java
+++ b/src/java/org/apache/cassandra/service/pager/PagingState.java
@@@ -21,23 -21,30 +21,31 @@@ import java.io.IOException
  import java.nio.ByteBuffer;
  import java.util.*;
  
- import org.apache.cassandra.schema.TableMetadata;
+ import com.google.common.annotations.VisibleForTesting;
+ import com.google.common.primitives.Ints;
+ 
 -import org.apache.cassandra.config.CFMetaData;
  import org.apache.cassandra.db.Clustering;
 -import org.apache.cassandra.db.LegacyLayout;
 +import org.apache.cassandra.db.CompactTables;
- import org.apache.cassandra.db.TypeSizes;
  import org.apache.cassandra.db.marshal.AbstractType;
  import org.apache.cassandra.db.marshal.BytesType;
 +import org.apache.cassandra.db.marshal.CompositeType;
  import org.apache.cassandra.db.rows.Cell;
  import org.apache.cassandra.db.rows.Row;
  import org.apache.cassandra.io.util.DataInputBuffer;
  import org.apache.cassandra.io.util.DataOutputBuffer;
  import org.apache.cassandra.io.util.DataOutputBufferFixed;
  import org.apache.cassandra.net.MessagingService;
- import org.apache.cassandra.transport.ProtocolVersion;
++import org.apache.cassandra.schema.TableMetadata;
  import org.apache.cassandra.transport.ProtocolException;
- import org.apache.cassandra.utils.ByteBufferUtil;
+ import org.apache.cassandra.transport.ProtocolVersion;
+ 
+ import static org.apache.cassandra.db.TypeSizes.sizeof;
+ import static org.apache.cassandra.db.TypeSizes.sizeofUnsignedVInt;
+ import static org.apache.cassandra.utils.ByteBufferUtil.*;
+ import static 
org.apache.cassandra.utils.vint.VIntCoding.computeUnsignedVIntSize;
+ import static org.apache.cassandra.utils.vint.VIntCoding.getUnsignedVInt;
  
+ @SuppressWarnings("WeakerAccess")
  public class PagingState
  {
  public final ByteBuffer partitionKey;  // Can be null for single 
partition queries.
@@@ -217,7 -360,7 +361,7 @@@
  // If the last returned row has no cell, this means in 
2.1/2.2 terms that we stopped on the row
  // marker. Note that this shouldn't happen if the table 
is COMPACT.
  assert !metadata.isCompactTable();
- mark = encodeCellName(metadata, row.clustering(), 
ByteBufferUtil.EMPTY_BYTE_BUFFER, null);
 -mark = LegacyLayout.encodeCellName(metadata, 
row.clustering(), EMPTY_BYTE_BUFFER, null);
++mark = encodeCellName(metadata, row.clustering(), 
EMPTY_BYTE_BUFFER, null);
  }
  else
  {
@@@ -244,80 -387,6 +388,80 @@@
   : Clustering.serializer.deserialize(mark, 
MessagingService.VERSION_30, makeClusteringTypes(metadata));
  }
  
 +// Old (pre-3.0) encoding of cells. We need that for the protocol v3 
as that is how things where encoded
 +private static 

[cassandra] branch cassandra-3.11 updated (033b30f -> 5514696)

2019-06-26 Thread aleksey
This is an automated email from the ASF dual-hosted git repository.

aleksey pushed a change to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git.


from 033b30f  Merge branch 'cassandra-3.0' into cassandra-3.11
 add dad82fb  Handle paging states serialized with a different version than 
the session's
 add 5514696  Merge branch 'cassandra-3.0' into cassandra-3.11

No new revisions were added by this update.

Summary of changes:
 CHANGES.txt|   1 +
 .../apache/cassandra/io/util/DataOutputBuffer.java |  13 +
 .../cassandra/service/pager/PagingState.java   | 280 -
 .../apache/cassandra/utils/vint/VIntCoding.java|  41 +++
 test/unit/org/apache/cassandra/Util.java   |   8 +-
 .../apache/cassandra/service/QueryPagerTest.java   |  35 +--
 .../cassandra/service/pager/PagingStateTest.java   |  42 +++-
 7 files changed, 332 insertions(+), 88 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[cassandra] branch trunk updated (225fa86 -> 3261b23)

2019-06-26 Thread aleksey
This is an automated email from the ASF dual-hosted git repository.

aleksey pushed a change to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git.


from 225fa86  Fix flaky unit test AuditLoggerTest
 add dad82fb  Handle paging states serialized with a different version than 
the session's
 add 5514696  Merge branch 'cassandra-3.0' into cassandra-3.11
 new 3261b23  Merge branch 'cassandra-3.11' into trunk

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 CHANGES.txt|   3 +
 .../apache/cassandra/io/util/DataOutputBuffer.java |  13 +
 .../cassandra/service/pager/PagingState.java   | 284 -
 test/unit/org/apache/cassandra/Util.java   |   7 +-
 .../apache/cassandra/service/QueryPagerTest.java   |  35 +--
 .../cassandra/service/pager/PagingStateTest.java   |  42 ++-
 6 files changed, 295 insertions(+), 89 deletions(-)


-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[cassandra] branch cassandra-3.0 updated (47dfb66 -> dad82fb)

2019-06-26 Thread aleksey
This is an automated email from the ASF dual-hosted git repository.

aleksey pushed a change to branch cassandra-3.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git.


from 47dfb66  Throw IOE instead of asserting on unsupporter peer versions
 add dad82fb  Handle paging states serialized with a different version than 
the session's

No new revisions were added by this update.

Summary of changes:
 CHANGES.txt|   1 +
 .../apache/cassandra/io/util/DataOutputBuffer.java |  13 +
 .../cassandra/service/pager/PagingState.java   | 285 -
 .../apache/cassandra/utils/vint/VIntCoding.java|  41 +++
 .../apache/cassandra/service/QueryPagerTest.java   |  35 +--
 .../cassandra/service/pager/PagingStateTest.java   |  72 --
 6 files changed, 347 insertions(+), 100 deletions(-)


-
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

2019-06-26 Thread Michael Shuler (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-15183:
---
Status: Triage Needed  (was: Awaiting Feedback)

> 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-15176) Fix PagingState deserialization when the state was serialized using protocol version different from current session's

2019-06-26 Thread Sam Tunnicliffe (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Tunnicliffe updated CASSANDRA-15176:

Status: Ready to Commit  (was: Review In Progress)

+1

> Fix PagingState deserialization when the state was serialized using protocol 
> version different from current session's
> -
>
> Key: CASSANDRA-15176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15176
> Project: Cassandra
>  Issue Type: Bug
>  Components: Messaging/Client
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
>
> 3.0 and native protocol V4 introduced a change to how {{PagingState}} is 
> serialized. Unfortunately that can break requests during upgrades: since 
> paging states are opaque, it's possible for a client to receive a paging 
> state encoded as V3 on a 2.1 node, and then send it to a 3.0 node on a V4 
> session. The version of the current session will be used to deserialize the 
> paging state, instead of the actual version used to serialize it, and the 
> request will fail.
> This is obviously sub-optimal, but also avoidable. This JIRA fixes one half 
> of the problem: 3.0 failing to deserialize 'mislabeled' paging states. We can 
> do this by inspecting the byte buffer to verify if it's been indeed 
> serialized with the protocol version used by the session, and if not, use the 
> other method of deserialization.
> It should be noted that we list this as a 'known limitation' somewhere, but 
> really this is an upgrade-blocking bug for some users of C*.



--
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

2019-06-26 Thread gloCalHelp.com (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-15183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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

2019-06-26 Thread gloCalHelp.com (JIRA)


 [ 
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

2019-06-26 Thread gloCalHelp.com (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-10948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Updated] (CASSANDRA-15184) Milliseconds are lost when importing with COPY FRΟΜ and an alternative DATETIMEFORMAT

2019-06-26 Thread Neophytos Demetriou (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neophytos Demetriou updated CASSANDRA-15184:

Summary: Milliseconds are lost when importing with COPY FRΟΜ and an 
alternative DATETIMEFORMAT  (was: Milliseconds are lost when importing with 
COPY FRΟΜ and an alternative DATATIMEFORMAT)

> Milliseconds are lost when importing with COPY FRΟΜ and an alternative 
> DATETIMEFORMAT
> -
>
> Key: CASSANDRA-15184
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15184
> Project: Cassandra
>  Issue Type: Bug
>  Components: Legacy/Tools
>Reporter: Neophytos Demetriou
>Priority: Normal
> Attachments: temptable.csv, temptable2.csv
>
>
> With a table created as follows:
>  
> {code:java}
> CREATE TABLE rc.temptable(id bigint, recorded_on timestamp, primary 
> key(id));{code}
>  
> The following does not work - milliseconds are lost - temptable2.csv is 
> attached:
>  
> {code:java}
> COPY rc.temptable(id,recorded_on) FROM 'temptable2.csv' WITH ERRFILE = 
> 'temptable.err' AND HEADER = TRUE AND BOOLSTYLE = '1,0' AND DATETIMEFORMAT = 
> '%Y-%m-%dT%H:%M:%S.%fZ'{code}
>  
> We have tried with various files/formats and, in essence, we are forced to 
> use the default cassandra format or milliseconds are lost. For instance, 
> using temptable.csv (attached) and the following command (no cqlshrc and no 
> CQLSH_DEFAULT_TIMESTAMP_FORMAT is defined) works fine:
> {code:java}
> COPY rc.temptable(id,recorded_on) FROM 'temptable.csv' WITH ERRFILE = 
> 'temptable.err' AND HEADER = TRUE AND BOOLSTYLE = '1,0'{code}
> This is with: cqlsh 5.0.1, Cassandra 3.11.4, CQL spec 3.4.4, Native protocol 
> v4.



--
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-15184) Milliseconds are lost when importing with COPY FRΟΜ and an alternative DATATIMEFORMAT

2019-06-26 Thread Neophytos Demetriou (JIRA)
Neophytos Demetriou created CASSANDRA-15184:
---

 Summary: Milliseconds are lost when importing with COPY FRΟΜ and 
an alternative DATATIMEFORMAT
 Key: CASSANDRA-15184
 URL: https://issues.apache.org/jira/browse/CASSANDRA-15184
 Project: Cassandra
  Issue Type: Bug
  Components: Legacy/Tools
Reporter: Neophytos Demetriou
 Attachments: temptable.csv, temptable2.csv

With a table created as follows:

 
{code:java}
CREATE TABLE rc.temptable(id bigint, recorded_on timestamp, primary 
key(id));{code}
 

The following does not work - milliseconds are lost - temptable2.csv is 
attached:

 
{code:java}
COPY rc.temptable(id,recorded_on) FROM 'temptable2.csv' WITH ERRFILE = 
'temptable.err' AND HEADER = TRUE AND BOOLSTYLE = '1,0' AND DATETIMEFORMAT = 
'%Y-%m-%dT%H:%M:%S.%fZ'{code}
 

We have tried with various files/formats and, in essence, we are forced to use 
the default cassandra format or milliseconds are lost. For instance, using 
temptable.csv (attached) and the following command (no cqlshrc and no 
CQLSH_DEFAULT_TIMESTAMP_FORMAT is defined) works fine:
{code:java}
COPY rc.temptable(id,recorded_on) FROM 'temptable.csv' WITH ERRFILE = 
'temptable.err' AND HEADER = TRUE AND BOOLSTYLE = '1,0'{code}
This is with: cqlsh 5.0.1, Cassandra 3.11.4, CQL spec 3.4.4, Native protocol v4.



--
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