[
https://issues.apache.org/jira/browse/SOLR-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069064#comment-14069064
]
Mark Miller commented on SOLR-6260:
-----------------------------------
bq. I'll remove my -1 if we can at least implement back compat with existing
solrconfigs. It should be trivial.
Of course we would handle back compat where it makes sense. That's an absurd
condition.
In any case, if you want to -1 over a vote that shows Solr developers want this
change, be my guest. We will see how long that works out for you.
bq. Further, if you're worried about attracting new committers,
I think the current culture of push back is worse than combating those that
foster the pushback. I plan on continuing to push very hard for change in our
obstructionist culture - one that I've played my part in at times too. It's
necessary. Being aggressive is necessary. I can find a variety of issues that
Tomas has filed that have a quick wet blanket thrown on them. We have done
everything we can to push him away rather than pull him in from where I am
standing.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
