[
https://issues.apache.org/jira/browse/CASSANDRA-15660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077660#comment-17077660
]
Dinesh Joshi edited comment on CASSANDRA-15660 at 4/7/20, 11:47 PM:
--------------------------------------------------------------------
[~jasonstack] thanks, I was looking at only the patch that [~mck] posted! My
bad.
shellcheck turned up a few issues. It may be worth addressing them:
{code:shell}
In ./bin/cqlsh line 28:
PARAMS=()
^-- SC2039: In POSIX sh, arrays are undefined.
In ./bin/cqlsh line 45:
PARAMS+=("$1")
^----^ SC2039: In POSIX sh, += is undefined.
^----^ SC2039: In POSIX sh, arrays are undefined.
In ./bin/cqlsh line 75:
exec "$interpreter" "$($interpreter -c "import os;
print(os.path.dirname(os.path.realpath('$0')))")/cqlsh.py" "${@:2}"
^----^ SC2039: In POSIX sh, string
indexing is undefined.
In ./bin/cqlsh line 84:
run_if_supported_version "$USER_SPECIFIED_PYTHON" "${PARAMS[@]}"
^----------^ SC2039: In
POSIX sh, array references are undefined.
In ./bin/cqlsh line 88:
run_if_supported_version "$interpreter" "${PARAMS[@]}"
^----------^ SC2039: In POSIX
sh, array references are undefined.
{code}
was (Author: djoshi3):
[~jasonstack] thanks, I was looking at only the patch that [~mck] posted! My
bad.
> Unable to specify -e/--execute flag in cqlsh
> --------------------------------------------
>
> Key: CASSANDRA-15660
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15660
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
> Reporter: Stefan Miklosovic
> Assignee: ZhaoYang
> Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0-alpha
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> From mailing list:
> [https://lists.apache.org/thread.html/r377099b632c62b641e4feef5b738084fc5369b0c7157fae867853597%40%3Cdev.cassandra.apache.org%3E]
> The bug looks like this:
> {code:java}
> $ /usr/bin/cqlsh -e 'describe keyspaces' -u cassandra -p cassandra 127.0.0.1
> Usage: cqlsh.py [options] [host [port]]cqlsh.py: error: '127.0.0.1' is not a
> valid port number.
> {code}
> This is working in 3.x releases just fine but fails on 4.
> The workaround for 4.x code as of today is to put these statements into file
> and use "-f" flag.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
