cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5826) Fix trigger directory detection code
Date Fri, 02 Aug 2013 17:53:49 GMT

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

Jonathan Ellis commented on CASSANDRA-5826:
-------------------------------------------

What is the Right Thing to do here?

I kind of like the original idea of locating lib/ and making triggers/ be a sibling of that
by convention.

"Any directory named triggers on the classpath" makes me nervous.

What would a Real Java Programmer do here [~zznate]?
                
> 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
>
>
> 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

Mime
View raw message