+1 to release. When I read the first 40 pages of the ref guide thoroughly, I found these minor issue. I should be able to fix most of them . If I am not able to fix any I will reach out for help.
Page 3/4 : The Paths heading this sentence looks a bit off? - When running the various examples mentioned through out this tutorial (i.e., bin/solr -e techproducts) the solr.home will be a sub directory of example/ created for you automatically Maybe we can word it as : When running the various examples mentioned in this guide (ex. bin/solr -e techproducts) the solr.home will be the example/<example_name> directory (ex. example/techproducts) The ref guide mentions this `Lucene/Solr downloads have grown nearly ten times over the past three years, with a current run-rate of over 6,000 downloads a day` - Just curious when are these numbers from? Page 7, Page 18 : Should the heading be just "Start Solr with a Specific Bundled Example" instead of "Start Solr with a Specific Example Configuration" ? Screenshot on Page 10 doesn't have the techproducts core name in the URL. I guess it's from the collection1 days The last sentence on page 11 seems a bit off? "Here is a request further constraining the request to documents with a category of "software"." - Maybe - This request constrains documents with a category of "software". Page 12- "Deploy Solr to your application server." . We don't need to mention "to your application server" part anymore. Page 12 Point 3 - Should we rephrase "Feed Solr the document for which your users will search." - "Feed Solr documents..." ? Page 12 - "and the response is a structured document: mainly XML..." If you start the dih example, the new UI doesn't parse the "overview" tab correctly in any of the 5 cores as part of this example. Thats a Jira though The note on page 18, "run-in" should simply be "run in" For the create command on page 22: All the params have an example . Should we add the mandatory "-c" argument to them or let it be as it is? On Page 28, the logging point says "Logging explains the various logging levels available and how to invoke them." . Maybe it should be "The Logging page shows recent messages logged by this Solr node." (copied from the first line of the actual data) Page 36, "In example screenshot above" . the is missing. Page 37, Documents Screen : The screen allows.. This screen allows Did not know it could upload documents :) Page 39 - solrconfig.xml or your Schema : schema should be small caps On Fri, Apr 22, 2016 at 5:11 PM, Cassandra Targett <[email protected]> wrote: > Thanks all for your votes - the vote passed, and I'll start the > publication process this morning. > > In regard to the issues raised: > > The image split across pages was done to solve a problem with images > overlapping text. For context, please see the thread from the 5.3 > Guide (http://markmail.org/message/jnvg7avsbl4fwznv) and the PDF > Export Changelist > (https://cwiki.apache.org/confluence/display/solr/PDF+Export+Changelist) > for August 2015. > > Atlassian provides a rather minimal output tool in the form of the PDF > exporter, and in recent releases has not oriented many Confluence > features & fixes to our use case. For as long as we use Confluence, > the lack of control over the output of the PDF will be a persistent > problem. IMO, the word breaks at the end of lines is a much more > serious problem, and there is nothing we can do about that either. > However, all is not lost, I have some ideas for solutions that I hope > to be able to share soon. > > bq. Perhaps the feature of numbered images is not so stupid after all, > letting the software rearrange images as it see fit to avoid splitting > or huge open white spaces at the bottom of pages. > > Jan, I'm not sure I understand I understand your suggestion here? The > idea is that if the images were numbered they'd fit better on the > page? I'm confused how those relate to each other. > > On Fri, Apr 22, 2016 at 4:18 AM, Jan Høydahl <[email protected]> > wrote: > > +1 > > > > Agree with Tomás’ comments. Checked 5.3 refguide as well, and the image > > split across page break exists there too, but by coincidence most > > screenshots were in the middle of pages :) I think for 6.0 we got a worst > > possible placement :) Perhaps the feature of numbered images is not so > > stupid after all, letting the software rearrange images as it see fit to > > avoid splitting or huge open white spaces at the bottom of pages. But > > Confluence probably does not support that? > > > > -- > > Jan Høydahl, search solution architect > > Cominvent AS - www.cominvent.com > > > > 22. apr. 2016 kl. 03.00 skrev Tomás Fernández Löbbe < > [email protected]>: > > > > +1 > > > > Not a blocker, but looks like many times images are broken into 2 pages > > (happens for example for many of the admin UI screenshot, but also with > > smaller images like in the Spatial Filers section). Is there a way to > > prevent this in Confluence? > > Also, we should try to prevent pasting extremely long examples, some > example > > outputs take ~3 pages > > > > On Thu, Apr 21, 2016 at 1:34 PM, Joel Bernstein <[email protected]> > wrote: > >> > >> +1 > >> > >> Joel Bernstein > >> http://joelsolr.blogspot.com/ > >> > >> On Thu, Apr 21, 2016 at 3:53 PM, Cassandra Targett < > [email protected]> > >> wrote: > >>> > >>> Reminder to VOTE on this thread so we can get the Ref Guide released. > >>> > >>> Thanks, > >>> Cassandra > >>> > >>> On Mon, Apr 18, 2016 at 6:13 PM, Steve Rowe <[email protected]> wrote: > >>> > +1 > >>> > > >>> > -- > >>> > Steve > >>> > www.lucidworks.com > >>> > > >>> >> On Apr 18, 2016, at 5:59 PM, Cassandra Targett <[email protected] > > > >>> >> wrote: > >>> >> > >>> >> Please VOTE to release the Apache Solr Ref Guide for 6.0: > >>> >> > >>> >> > https://dist.apache.org/repos/dist/dev/lucene/solr/ref-guide/apache-solr-ref-guide-6.0-RC2/ > >>> >> > >>> >> $ cat apache-solr-ref-guide-6.0.pdf.sha1 > >>> >> 9073530b89148ce3f641a42e38249bd1fbb25136 > >>> >> apache-solr-ref-guide-6.0.pdf > >>> >> > >>> >> Here's my +1. > >>> >> > >>> >> * Note, RC1 was skipped because there were a few other issues to be > >>> >> fixed right after I'd committed it. > >>> >> > >>> >> Thanks, > >>> >> Cassandra > >>> >> > >>> >> > --------------------------------------------------------------------- > >>> >> To unsubscribe, e-mail: [email protected] > >>> >> For additional commands, e-mail: [email protected] > >>> >> > >>> > > >>> > > >>> > --------------------------------------------------------------------- > >>> > To unsubscribe, e-mail: [email protected] > >>> > For additional commands, e-mail: [email protected] > >>> > > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Regards, Varun Thacker
