You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Robert Muir (Jira)" <ji...@apache.org> on 2019/12/13 08:57:00 UTC
[jira] [Resolved] (SOLR-14064) remove some hadoop brain-damage from
build environment
[ https://issues.apache.org/jira/browse/SOLR-14064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir resolved SOLR-14064.
--------------------------------
Fix Version/s: 8.5
Assignee: Robert Muir
Resolution: Fixed
Thanks Kevin!
> 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
> Assignee: Robert Muir
> Priority: Major
> Fix For: 8.5
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org