[ 
https://issues.apache.org/jira/browse/SOLR-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268352#comment-14268352
 ] 

Erick Erickson commented on SOLR-6925:
--------------------------------------

I had three non-reproducible test failures that I want to look at some more, 
but they're things that are failing currently I think.

[~steffkes] I left changes in the javascript code (e.g. SOLR-5446 and 
SOLR-5456) on the theory that I didn't know enough about javascript to risk 
changing them and the back-end code is gone anyway so I don't think leaving 
those changes alone is a problem. Just FYI in case you're interested.

[~anshumg] I assumed on the dev list that "next thursday" as a target for 5.0 
RC0 was the 15th, correct?

If I can satisfy myself that the test failures don't have anything to do with 
this patch, I'll commit tomorrow sometime (or perhaps tonight even).

> Back out all changes having to do with SOLR-5287
> ------------------------------------------------
>
>                 Key: SOLR-6925
>                 URL: https://issues.apache.org/jira/browse/SOLR-6925
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.0, Trunk
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Blocker
>         Attachments: SOLR-6925.patch
>
>
> Should have something today/tomorrow. The history here is that I had this 
> bright idea to edit files directly from the admin UI, especially schema.xml 
> and solrxconifg.xml. Brilliant I sez to myself... except it's a significant 
> security hole and I'm really glad that was pointed out before we released it 
> in 4x.
> So we pulled it completely from 4.x and made it something in 5.x (then trunk) 
> that you could enable (disabled by default) if you wanted to live dangerously 
> and "we'd deal with it later". Well it's later.
> Given all the work for managed schemas and the like in the interim, I think 
> this is cruft that should be removed completely from current trunk and 5x.
> Marking it as a blocker so we don't release 5x with this in it or we'll have 
> back-compat issues. Should have a fix in very quickly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to