[
https://issues.apache.org/jira/browse/SOLR-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16966267#comment-16966267
]
Andrzej Bialecki commented on SOLR-13888:
-----------------------------------------
I couldn’t care less about the name. What I’m most interested in is the code -
let the code speak for itself, even if it’s called “Solr UnFuBar-ed”:)
My concern though is that this cleanup or redesign, or whatever Mark wants to
call it, is a monumental task bringing monumental changes, and IMHO the sooner
it becomes public (in the sense that the community can at least follow Mark’s
work) the better, even if it’s still incomplete. Progress, not perfection.
So I would urge you Mark to continue this much needed work, but doing it
piece-wise and in public, and not through a single massive code dump - it will
increase the likelihood of this work being better understood and accepted.
> SolrCloud 2
> -----------
>
> Key: SOLR-13888
> URL: https://issues.apache.org/jira/browse/SOLR-13888
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Major
>
> As devs discuss dropping the SolrCloud name on the dev list, here is an issue
> titled SolrCloud 2.
> A couple times now I've pulled on the sweater thread that is our broken
> tests. It leads to one place - SolrCloud is sick and devs are adding spotty
> code on top of it at a rate that will lead to the system falling in on
> itself. As it is, it's a very slow, very inefficient, very unreliable, very
> buggy system.
> This is not why I am here. This is the opposite of why I am here.
> So please, let's stop. We can't build on that thing as it is.
>
> I need some time, I lost a lot of work at one point, the scope has expanded
> since I realized how problematic some things really are, but I have an
> alternative path that is not so duct tape and straw. As the building climbs,
> that foundation is going to kill us all.
>
> This i not about an architecture change - the architecture is fine. The
> implementation is broken and getting worse.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
