lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-3488) Create a Collections API for SolrCloud
Date Thu, 12 Jul 2012 23:55:35 GMT


Mark Miller commented on SOLR-3488:

Commit improved tests and reload command in a moment.

Another thing we will need before too long is a way to get a response I think? Right now,
the client can't learn of the success or failure of the command. It's just int he Overseers

To get notified, I suppose the call would have to block and then get a result from the overseer.

I suppose that could be done by something like: create a new emphemeral node for each job
- client watches the node - when overseer is done, it sets the result as data on the node
- client gets a watch notify and reads the result? Then how to clean up? Not sure about the
idea overall, brainstorming ... don't see a simple way to have the over seer do the work in
an async fashion and have the client easily get the results of that.
> Create a Collections API for SolrCloud
> --------------------------------------
>                 Key: SOLR-3488
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.0
>         Attachments: SOLR-3488.patch, SOLR-3488.patch, SOLR-3488.patch, SOLR-3488_2.patch

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message