Details
-
Bug
-
Status: Resolved
-
Low
-
Resolution: Fixed
-
None
-
$ cassandra -v
2.1.2MacOSX 10.9.5
$ brew info cassandra [14:15:41]
cassandra: stable 2.2.3 (bottled)
Eventually consistent, distributed key-value store
https://cassandra.apache.org
/usr/local/Cellar/cassandra/2.1.2 (3975 files, 92M) *
Built from source
From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/cassandra.rb
==> Caveats
To have launchd start cassandra at login:
ln -sfv /usr/local/opt/cassandra/*.plist ~/Library/LaunchAgents
Then to load cassandra now:
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.cassandra.plist$ cassandra -v 2.1.2 MacOSX 10.9.5 $ brew info cassandra [14:15:41] cassandra: stable 2.2.3 (bottled) Eventually consistent, distributed key-value store https://cassandra.apache.org /usr/local/Cellar/cassandra/2.1.2 (3975 files, 92M) * Built from source From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/cassandra.rb ==> Caveats To have launchd start cassandra at login: ln -sfv /usr/local/opt/cassandra/*.plist ~/Library/LaunchAgents Then to load cassandra now: launchctl load ~/Library/LaunchAgents/homebrew.mxcl.cassandra.plist
-
Low
Description
When I execute `cassandra -v` on the terminal the directory `cassandra.logdir_IS_UNDEFINED` is created in my CWD:
$ tree cassandra.logdir_IS_UNDEFINED cassandra.logdir_IS_UNDEFINED └── system.log 0 directories, 1 file
Expected: That no log file nor directory is created when I'm simply checking the version of Cassandra. Feels a bit ridiculous.
Additionals: Just double checking, is this a bundling issue that should be reported to Homebrew? Probably not, right?