You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2016/02/18 20:01:21 UTC
[jira] [Commented] (CASSANDRA-11033) Prevent logging in sandboxed
state
[ https://issues.apache.org/jira/browse/CASSANDRA-11033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152859#comment-15152859 ]
Tyler Hobbs commented on CASSANDRA-11033:
-----------------------------------------
+1 on the code changes, but can you also do a CI run on a trunk version of the branch before committing?
> Prevent logging in sandboxed state
> ----------------------------------
>
> Key: CASSANDRA-11033
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11033
> Project: Cassandra
> Issue Type: Bug
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
> Fix For: 3.0.x
>
>
> logback will re-read its configuration file regularly. So it is possible that logback tries to reload the configuration while we log from a sandboxed UDF, which will fail due to the restricted access privileges for UDFs. UDAs are also affected as these use UDFs.
> /cc [~doanduyhai]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)