[
https://issues.apache.org/jira/browse/CASSANDRA-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843777#action_12843777
]
Gary Dusbabek commented on CASSANDRA-625:
-----------------------------------------
That patch works. :)
Why not have CassandraDaemon and StorageService use the slf4j logger and still
call into log4j to make the settings changes? (Obviously these will be noops
when slf4j is not bound to log4j.) Or is this kind of mixing not allowed?
> Migrate to slf4j from log4j in cassandra code
> ---------------------------------------------
>
> Key: CASSANDRA-625
> URL: https://issues.apache.org/jira/browse/CASSANDRA-625
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: all
> Reporter: gabriele renzi
> Priority: Minor
> Fix For: 0.7
>
> Attachments: CASSANDRA-625-3.patch
>
>
> currently code generated from thrift uses slf4j while cassandra uses raw
> log4j.
> There are various level in which this can be changed:
> * simply switch log4j loggers with slf4j logger (done in patch)
> * replacing log4j-isms (e.g. string concatenation+isFooEnabled in all code
> paths) with slf4j-isms (marker string + additional arguments)
> * remove code that is already available for lsf4j (LogUtils.java, I believe
> is unnecessary)
> I am posting this as a reminder, I have a half baked patch locally but it
> needs more work
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
