[
https://issues.apache.org/jira/browse/SOLR-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965715#comment-16965715
]
Mark Miller commented on SOLR-13888:
------------------------------------
If we have a new release, you guys can document and name and do whatever you'd
like, I really could care less.
This issue is about addressing SolrCloud and it's integration onto Solr before
it. I'm calling it SolrCloud 2 - I think it's the right name, it's the name of
my work, if my work is used, that's it.
When that work is Solr, I don't care what you want to call it. My starburst
branch wasn't going to rename Solr either.
Anyway, I started gaining real insight into Solr and SolrCloud when I dived
into my starburst branch effort about 2 years ago now or maybe a little more or
less.
I got the system into a shape that I could actually peak in. Kind of like
washing a spot off the window covered in soot.
I spent a lot of time working towards addressing the seemingly unlimited number
of issues I found. Frustrated with the community and SolrCloud, I was doing
this on my branch without regard for regular Solr. I changed jobs and abandoned
that stuff. Even lost most of it unknown to me.
Anyway, since, I keep tugging at the same threads. A couple times walked the
same paths.
There is only one conclusion for me - I cant be associated with this anymore,
not unless we make a huge effort to address this.
> 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
