[ https://issues.apache.org/jira/browse/SOLR-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-13888:
-------------------------------
Description:
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.
was:
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 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.
> 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 message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
|