I'd love to make this stuff easier (SOLR-5507). Stalled on how to make
a transition work. Just starting a new codebase using Angular would be
great, but could easily become a stalled effort, and easily make things
worse than they are now (two code bases to understand, rather than
one).
If
At least three JIRAS relate:
SOLR-4316, SOLR-4388, SOLR-5466
It seems to me, that if SOLR-5466 got done (don't see why it'd be hard)
we'd have enough to make this work, particularly adding/deleting
collections _and_ adding cores on specific nodes to specific shards.
In fact, we don't even need
On Mar 1, 2014, at 10:16 AM, Erick Erickson erickerick...@gmail.com wrote:
Thoughts?
+1!
Unfortunately, I can’t be of much help currently :(
- Mark
http://about.me/markrmiller
-
To unsubscribe, e-mail:
I like the ideas. Big +1 on all three issues. I can help with
SOLR-5466 -- it's already on my plate. I am comfortable writing
Javascript but I'd need help with HTML/CSS. Let's get to the UI part
once we're done with the APIs.
We should discourage reading such internal structures directly from
ZK.
i think the rest was long enough (: sometimes i need an additional kick in the
butt .. erm i mean, motivation! =]
will give it another try in the upcoming next week. at least get a initial
collection handling done, we can still think about additional steps how to
handle things differently
