You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Vijay (JIRA)" <ji...@apache.org> on 2013/08/05 22:20:47 UTC

[jira] [Updated] (CASSANDRA-5826) Fix trigger directory detection code

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

Vijay updated CASSANDRA-5826:
-----------------------------

    Attachment: 0001-handle-trigger-non-existance.patch

Hi Brandon, Attached, handles un reachable trigger directory.
                
> Fix trigger directory detection code
> ------------------------------------
>
>                 Key: CASSANDRA-5826
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5826
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0 beta 2
>         Environment: OS X
>            Reporter: Aleksey Yeschenko
>            Assignee: Vijay
>              Labels: triggers
>             Fix For: 2.0 rc1
>
>         Attachments: 0001-5826.patch, 0001-handle-trigger-non-existance.patch
>
>
> At least when building from source, Cassandra determines the trigger directory wrong. C* calculates the trigger directory as 'build/triggers' instead of 'triggers'.
> FBUtilities.cassandraHomeDir() is to blame, and should be replaced with something more robust.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira