- Taschenbuch: 328 Seiten
- Verlag: Packt Publishing (25. Januar 2013)
- Sprache: Englisch
- ISBN-10: 1782161325
- ISBN-13: 978-1782161325
- Größe und/oder Gewicht: 19 x 1,9 x 23,5 cm
- Durchschnittliche Kundenbewertung: 2 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 362.240 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Apache Solr 4 Cookbook (Englisch) Taschenbuch – 25. Januar 2013
|Neu ab||Gebraucht ab|
Kunden, die diesen Artikel angesehen haben, haben auch angesehen
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Über den Autor und weitere Mitwirkende
Rafal Kuc is a born team leader and software developer. Currently working as a Consultant and a Software Engineer at Sematext Inc, where he concentrates on open source technologies such as Apache Lucene and Solr, ElasticSearch, and Hadoop stack. He has more than 10 years of experience in various software branches, from banking software to e-commerce products. He is mainly focused on Java, but open to every tool and programming language that will make the achievement of his goal easier and faster. Rafal is also one of the founders of the solr.pl site, where he tries to share his knowledge and help people with their problems with Solr and Lucene. He is also a speaker for various conferences around the world such as Lucene Eurocon, Berlin Buzzwords, and ApacheCon.
Rafal began his journey with Lucene in 2002 and it wasn't love at first sight. When he came back to Lucene later in 2003, he revised his thoughts about the framework and saw the potential in search technologies. Then Solr came and that was it. From then on, Rafal has concentrated on search technologies and data analysis. Right now Lucene, Solr, and ElasticSearch are his main points of interest.
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
Die hilfreichsten Kundenrezensionen auf Amazon.com
The book's layout, it's non-nonsense "do this, do that" style and the section at the end of each recipe, explaining what you just did are all great elements.
However, where this book suffers is in its attention to detail. While the author states clearly that it was based on Solr 4.0, many of the examples are either incorrect, incomplete or obsolete.
For example, using default="NEW" is discouraged in Solr 4, in favor of UUIDUpdateProcessorFactory.
Another example involves setting UTF-8 URI Encoding for Tomcat, which is an overhang from Solr 3 and no longer required in Solr 4.
The above examples are inconvenient. Some omissions are more serious. For example, in the section describing auto-generation of UUIDs for uploaded documents, while the description for setting up a UUID RequestProcessorChain is pretty straightforward, the documentation leaves out the key fact that requestHandler for /extract/update in solrconfig.xml needs to be told to invoke the uuid requestProcessor chain. Without this, the auto-generator will never be called and documents will fail upload with NULL unique keys.
Another bugbear is that spaces between words in fixed space font are often dropped. If the word looks long, chances are you're missing a space. (Note: This was on my Kindle Edition book. May not be the case in print.) This makes some commands fail.
These are just a few examples.
I wish I could recommend the book more highly but its many, many errors and omissions make this impossible. If the book goes through another round of proofreading and errata correction, it could be a solid 4-star.
Also the kindle reader on mac is awkward to use. basic stuff like scrolling and font sizing do not work well.
For got to mention Its really hard to use the sample code. Its hard to figure out what code sample "task" maps to a particular recipe in the book. Finally never ever use spaces in file or directory names. It make using the code much harder