lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-13888) SolrCloud 2
Date Wed, 06 Nov 2019 03:51:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968057#comment-16968057
] 

Mark Miller commented on SOLR-13888:
------------------------------------

{quote}, I’m suggesting that we improve the architecture by separating different concerns
to different modules. 
{quote}
Like I said, "So I'm happy if you do modules, lots of good things to do"

There are a million things to do that will improve the project, that will make it easier to
do good things with the project. If you want to add them as suggestions to that doc for example,
that's great.

Here, I am very focused on what is necessary and useful for this problem. That's where I'm
just shirking modules. If you want to talk to me about modules in a module JIRA, maybe I have
some interesting thing to say, here I don't think it applies. And I could be wrong, I'm just
voicing my  thoughts.

My focus is very narrow. Fix the problem. Do it in a way that allows a future. That future
is then up to people with more investment in that side than me.

> 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
>         Attachments: solrscreen.png
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org


Mime
View raw message