You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Corey Hemminger (JIRA)" <ji...@apache.org> on 2014/05/19 22:07:41 UTC

[jira] [Commented] (CASSANDRA-7266) Allow cqlsh shell ignore .cassandra permission errors and not fail to open the cqlsh shell.

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

Corey Hemminger commented on CASSANDRA-7266:
--------------------------------------------

CQLSH should work much like the bash shell where it can display an error about not being able to access users home directory but still let you into the shell. You could even add a warning to let the users know that cqlsh history won't be saved.

> Allow cqlsh shell ignore .cassandra permission errors and not fail to open the cqlsh shell.
> -------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7266
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7266
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Carolyn Jung
>            Priority: Minor
>
> There is an issue with home directories not working and this is causing users to not be able to execute cqlsh shell. CQLSH shell uses the .cassandra folder in the user's home directory for history and currently throws error and returns you to the prompt.  Below is the error:
> -bash-4.1$ cqlsh 
> Traceback (most recent call last): 
> File "/usr/bin/cqlsh", line 141, in <module> 
> os.mkdir(HISTORY_DIR) 
> OSError: [Errno 13] Permission denied: '/home/testuser/.cassandra'
> In this example, testuser does not have access to the home directory.
> Requested resolution is to allow a user to access the cqlsh shell even though the home directory is inaccessible.
> The current workaround is to gain access to the home directory.  This is not acceptable in all cases because of security policies of the organization.



--
This message was sent by Atlassian JIRA
(v6.2#6252)