Hi Cassandra,
Thanks for putting together this list. I don't think the solution for
SOLR-5495 needs any mention in the Ref Guide as it's internal
hardening of replication / recovery scenarios. However, SOLR-5468
should be mentioned as it is a new parameter that can be passed in
update requests. I'm not sure of a good place to put it though?
Basically, it is an optional feature that can be activated by passing
the min_rf=# in an UpdateRequest to request Solr to return the
achieved replication factor for the request. For instance, if a client
passed min_rf=2 and a shard has 3 replicas, but two of the replicas
are down, then the server will return rf=1. This indicates to the
client application that the collection health is degraded and gives
the client an option of taking some additional action, such as saving
a list of documents that were added during the degraded state. Thus,
this feature is related to replication in SolrCloud.
Also, I'm happy to help out with any of the ManagedResource
refactoring work if we take that on in this release.
Tim
On Mon, Jun 23, 2014 at 10:23 AM, Cassandra Targett
casstarg...@gmail.com wrote:
The vote for Lucene/Solr 4.9 is underway and we need to get the Solr Ref
Guide updated for the new release.
I went through the CHANGES.txt for Solr on Friday and updated the TODO list
found at
https://cwiki.apache.org/confluence/display/solr/Internal+-+TODO+List. I
notice that many of the new features or changes in 4.9 haven't been
documented in the Ref Guide yet. We need some volunteers to work on updating
the guide before we can make a Ref Guide release candidate for 4.9.
If you look at the TODO list, you'll see lots of stuff from earlier releases
that haven't made it into the guide yet either. If we want users to be able
to use the work we've done for each release, and if we want the Ref Guide to
be a definitive source of Solr information, we have to add content on new
features and keep content up to date as things change.
Please take a few moments and see if there is anything you can add or
change. If you need help with wording or don't know where something should
go, speak up and I'll try to help.
Cassandra
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
