[Yanel-commits] rev 50115 - public/yanel/trunk/src/realms/yanel-website/content

memo at wyona.com memo at wyona.com
Wed Jun 2 13:12:07 CEST 2010


Author: memo
Date: 2010-06-02 13:12:06 +0200 (Wed, 02 Jun 2010)
New Revision: 50115

Modified:
   public/yanel/trunk/src/realms/yanel-website/content/858861d0-8592-11dd-ad8b-0800200c9a66
Log:
made implementation details a bit more precise

Modified: public/yanel/trunk/src/realms/yanel-website/content/858861d0-8592-11dd-ad8b-0800200c9a66
===================================================================
--- public/yanel/trunk/src/realms/yanel-website/content/858861d0-8592-11dd-ad8b-0800200c9a66	2010-06-02 08:44:49 UTC (rev 50114)
+++ public/yanel/trunk/src/realms/yanel-website/content/858861d0-8592-11dd-ad8b-0800200c9a66	2010-06-02 11:12:06 UTC (rev 50115)
@@ -118,6 +118,6 @@
 <p>With the current implementation, it is not possible to search in fulltext mode and properties simultaneously, but it is possible to configure different searches via different resource-configs, e.g. one for each.</p>
 <h2>Custom parser</h2>
 <p>You can easily write your own (Tika) parser. The best way to do this is to copy an existing parser (e.g. org.apache.tika.parser.xml.DcXMLParser), and modify it according to your needs, and configure Tika to use your custom parser (in tika-config.xml). Also see the <a href="http://tika.apache.org/">Tika documentation</a>.</p>
-<p>Caveat: With the current Yarep implementation, only metadata fields "title", "keywords" and "description" will be indexed, and they will be indexed as fulltext!</p>
+<p>Caveat: With the current Yarep implementation, only metadata fields "org.apache.tika.metadata.Metadata.TITLE", "org.apache.tika.metadata.Metadata.KEYWORDS" and "org.apache.tika.metadata.Metadata.DESCRIPTION" will be indexed, and they will be indexed as fulltext!</p>
 </body>
 </html>
\ No newline at end of file



More information about the Yanel-commits mailing list