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

David Smiley commented on SOLR-13888:
-------------------------------------

> It's not code, you cant veto it.

Mark: I believe you are being given notice that when your code appears, it's 
going to be vetoed.
Noble, Ishan:  I think it's premature to make such judgement unless you think 
that whatever it is, we wouldn't want it.  Lets have an open mind.

Any way, I'm looking forward to seeing what Mark comes up with.  I certainly 
hope it's up to snuff; we should all hope/want Mark to succeed in simplifying 
and speeding up Solr Cloud's internals.  I'm most concerned about what comes 
after a successful POC.  Even "successful POC" is kinda loaded because of 
course it'll have a bunch of disabled things that don't quite work yet.  What 
functionality was removed or what tests were ignored and how much effort would 
it be to get that re-instated.  Obviously this can't be answered now.

> 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

Reply via email to