[
https://issues.apache.org/jira/browse/SOLR-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068645#comment-14068645
]
Mark Miller commented on SOLR-6260:
-----------------------------------
There is nothing person in anything I wrote. Feel free to pull out what you
think is and I'll correct it.
Reasonable people can disagree, and the same culture that had Lucene locked up
for years in the mid 2000's can lock up Solr here.
We need a couple things:
* To transition to a SolrCloud first world where everything is sensible and not
"because of history baggage".
* To encourage and develop new contributors.
Pushing back on this simple issue and issues like it is part of an overall
culture that hurts both those things.
When I joined, I wanted to fix crap like this too. I was slowly beaten down
over time until I just accepted that a lot of our code was crap. I stopped even
trying to fix it. I won't be part of beating that out of a new generation of
committers. This needs to be fixed. The benefits are bigger than you understand
IMO. And the benefits of not doing it, are super minor. Solr needs to worry
about the future, not the past.
> Rename DirectUpdateHandler2
> ---------------------------
>
> Key: SOLR-6260
> URL: https://issues.apache.org/jira/browse/SOLR-6260
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 5.0
> Reporter: Tomás Fernández Löbbe
> Priority: Minor
> Attachments: SOLR-6260.patch, SOLR-6260.patch
>
>
> "DirectUpdateHandler" was removed, I think in Solr 4. DirectUpdateHandler2
> should be renamed, at least remove that "2". I don't know really what
> "direct" means here. Maybe it could be renamed to "DefaultUpdateHandler", or
> "UpdateHandlerDefaultImpl", or other good suggestions
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
