[
https://issues.apache.org/jira/browse/SOLR-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048221#comment-18048221
]
David Smiley commented on SOLR-14361:
-------------------------------------
Sorry but vote is a veto, -1 to SIP-6. I've expressed my reservations
previously, albeit not specifically referencing SIP-6 but to the idea. Perhaps
before investing in implementing a SIP, a notification message would be prudent.
A strength of Solr is its configurability. I believe SIP-6 significantly tears
down that configurability. Today, a user can add CORS and a manner of other
things merely be editing configuration files. I was such a user with that
exact use-case once. Even the web.xml is standard so benefits from broad
industry knowledge / compatibility. And I've made adjustments to jetty
configuration files before.
> SIP-6 Solr should own the bootstrap process
> -------------------------------------------
>
> Key: SOLR-14361
> URL: https://issues.apache.org/jira/browse/SOLR-14361
> Project: Solr
> Issue Type: New Feature
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This is the JIRA corresponding to
> [SIP-6|https://cwiki.apache.org/confluence/display/SOLR/SIP-6+Solr+should+own+the+bootstrap+process].
> The overall design and planning will happen on the Confluence page.
> Consept and architecture discussions can happen in the dev@ mail thread
> linked from the SIP.
> This Jira will act as an umbrella/parent issue to track development and will
> not have much activity until the SIP is finalized and approved.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
