[
https://issues.apache.org/jira/browse/SOLR-14064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995475#comment-16995475
]
ASF subversion and git services commented on SOLR-14064:
--------------------------------------------------------
Commit a6e7c770c27f6467d8aa717d4b07c8682d09ebc8 in lucene-solr's branch
refs/heads/master from Robert Muir
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=a6e7c77 ]
SOLR-14064: remove some hadoop brain damage from build environment
Some permissions and build hacks were made on behalf of hadoop: hacks on
top of hacks. Now that the major problems such as classpath pollution and
hadoop test code are fixed, so we can remove hacks built on top of them.
> remove some hadoop brain-damage from build environment
> ------------------------------------------------------
>
> Key: SOLR-14064
> URL: https://issues.apache.org/jira/browse/SOLR-14064
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Robert Muir
> Priority: Major
> Attachments: SOLR-14064.patch
>
>
> Some permissions and build hacks were made on behalf of hadoop. These were
> most definitely hacks on top of hacks.
> The background is that the hadoop code is a true nightmare to deal with, if
> you want to sandbox code with SecurityManager.
> Now that [~krisden] has wrestled it (at least mostly?) to the ground, let's
> remove the hacks from solr security policy and lucene build that I added. We
> need to be strict: ensure things are really working (otherwise we get
> SecurityException). This also makes the configuration simpler.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
