You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by bu...@apache.org on 2011/08/08 17:13:06 UTC
svn commit: r794004 [3/3] - in
/websites/staging/lucene/trunk/content/lucene: ./ core/ solr/
Modified: websites/staging/lucene/trunk/content/lucene/solr/tutorial.html
==============================================================================
--- websites/staging/lucene/trunk/content/lucene/solr/tutorial.html (original)
+++ websites/staging/lucene/trunk/content/lucene/solr/tutorial.html Mon Aug 8 15:13:06 2011
@@ -497,6 +497,46 @@ Explore the <a href="http://wiki.apache.
more details about Solr's many
<a href="features.html">features</a>.</p>
<p>Have Fun, and we'll see you on the Solr mailing lists!</p></div>
+
+ <div><h1 id="solr_news">Solr News</h1>
+<h2 id="28_july_2011_-_warning_index_corruption_and_crashes_in_apache_lucene_core__apache_solr_with_java_7">28 July 2011 - WARNING: Index corruption and crashes in Apache Lucene Core / Apache Solr with Java 7</h2>
+<p>Oracle released <a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Java 7</a> today.
+Unfortunately it contains hotspot compiler optimizations, which miscompile some loops.
+This can affect code of several Apache projects. Sometimes JVMs only crash, but in several cases,
+results calculated can be incorrect, leading to bugs in applications
+(see Hotspot bugs <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7070134">7070134</a>,
+<a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7044738">7044738</a>,
+<a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7068051">7068051</a>).
+<strong>Apache Lucene Core</strong> and <strong>Apache Solr</strong> are two Apache projects,
+which are affected by these bugs, namely all versions released until today.
+Solr users with the default configuration will have
+Java crashing with <code>SIGSEGV</code> as soon as they start to index documents, as one
+affected part is the well-known Porter stemmer
+(see <a href="https://issues.apache.org/jira/browse/LUCENE-3335">LUCENE-3335</a>).
+Other loops in Lucene may be miscompiled, too, leading to index corruption
+(especially on Lucene trunk with pulsing codec; other loops may be
+affected, too - <a href="https://issues.apache.org/jira/browse/LUCENE-3346">LUCENE-3346</a>).
+These problems were detected only 5 days before the official Java 7 release,
+so Oracle had no time to fix those bugs, affecting also many more applications.
+In response to our questions, they proposed to include the fixes into service
+release u2 (eventually into service release u1, see
+<a href="http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2011-July/005971.html">this mail</a>).
+<strong>This means you cannot use Apache Lucene/Solr with Java 7 releases before Update 2!</strong>
+If you do, please don't open bug reports, it is not the committers' fault!
+At least disable loop optimizations using the <code>-XX:-UseLoopPredicate</code> JVM option
+to not risk index corruptions.
+<em>Please note:</em> Also Java 6 users are affected, if they use one of those
+JVM options, which are <strong>not</strong> enabled by default: <code>-XX:+OptimizeStringConcat</code>
+or <code>-XX:+AggressiveOpts</code>.
+It is strongly recommended not to use any hotspot optimization switches in any Java
+version without extensive testing!
+In case you upgrade to Java 7, remember that you may have to reindex, as the unicode
+version shipped with Java 7 changed and tokenization behaves differently
+(e.g. lowercasing). For more information, read <code>JRE_VERSION_MIGRATION.txt</code>
+in your distribution package!</p></div>
+
+ <div><h2 id="the_apache_software_foundation">The Apache Software Foundation</h2>
+<p>The <a href="http://www.apache.org">Apache Software Foundation</a> provides support for the Apache community of open-source software projects. The Apache projects are defined by collaborative consensus based processes, an open, pragmatic software license and a desire to create high quality software that leads the way in its field. Apache Lucene, Apache Solr, Apache PyLucene, Apache Open Relevance Project and their respective logos are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p></div>
</div>
<div id="sidebar">
@@ -537,6 +577,11 @@ more details about Solr's many
<h1>Latest JIRA</h1>
<div class="status-item">
<a class="bug" href="
+ https://issues.apache.org/jira/browse/SOLR-2654?focusedCommentId=13080968#comment-13080968">RE: [SOLR-2654] <lockType/> not used consistently in all places Directory objects are instantiated</a><br/>
+
+ <p>Yeesh - much more difficult to get this right than I expected. I may just go back to only closing...</p>
+
+ <a class="bug" href="
https://issues.apache.org/jira/browse/SOLR-2654?focusedCommentId=13080687#comment-13080687">RE: [SOLR-2654] <lockType/> not used consistently in all places Directory objects are instantiated</a><br/>
<p>So I removed the close directories hack for tests and realized that I need the solution I proposed above regardless...</p>
@@ -571,51 +616,30 @@ more details about Solr's many
</table>
-
- <a class="bug" href="
- https://issues.apache.org/jira/browse/SOLR-2654?focusedCommentId=13080664#comment-13080664">RE: [SOLR-2654] <lockType/> not used consistently in all places Directory objects are instantiated</a><br/>
-
- <p>so we can remove the closeDirectories() hack in SolrTestCaseJ4?</p>
- <br/>
- <br/>
-
- <table>
-
- <tr>
- <td>Author:</td>
- <td><a
- href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rcmuir">Robert Muir</a>
- (<a href="https://issues.apache.org/jira/browse/SOLR-2654">SOLR-2654</a>)</td>
- </tr>
-
-
-
- </table>
-
</div></div>
<div id="dev-mail">
<h1>Latest Dev</h1>
<div class="status-item">
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3cCAAHmpkg9jrb96UEATwaSbP+CULY2ZPHMcnDQrHmardr+-hXCrw@mail.gmail.com%3e">Re: [VOTE]: Accept Kuromoji code donation to Apache Lucene</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c2017944810.16645.1312813707315.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-2654) <lockType/> not used consistently in all places Directory objects are instantiated</a></h4>
<hr>
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c1934488272.31281312809355610.JavaMail.hudson@aegis%3e">[JENKINS] Lucene-Solr-tests-only-3.x - Build # 10082 - Failure</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c485501116.16643.1312813707244.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (LUCENE-3298) FST has hard limit max size of 2.1 GB</a></h4>
<hr>
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c83F112F7-2573-4557-AC1B-C1595D610727@apache.org%3e">Re: [VOTE]: Accept Kuromoji code donation to Apache Lucene</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c394646490.16631.1312813467194.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Updated] (LUCENE-3357) Unit and integration test cases for the new Similarities</a></h4>
<hr>
</div>
</div>
<div id="solr-user-mail">
<h1>Latest Solr User</h1>
<div class="status-item">
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3c1312804620557-3235341.post@n3.nabble.com%3e">Multiplexing TokenFilter for multi-language?</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3cCABCJ++JpY3S0KG+USqvyZSk+tpwTLX+N1fY8UXGh=LHNDsHYcw@mail.gmail.com%3e">PositionIncrement gap and multi-valued fields.</a></h4>
<hr>
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3cCAM0cPW7dxRipV3hcJU-mvGU9LbJhbiA_rY1K-=-B3KQEf3YHAA@mail.gmail.com%3e">Re: strip html from data</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3c8F0D0142CA7ECC4287A9EC1BD8CB880C17C72DB2D5@USLVDCMBVP01.ingramcontent.com%3e">RE: how to enable MMapDirectory in solr 1.4?</a></h4>
<hr>
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3cCAFAd71XSa5+9yQF+JCBcE2qC0rkX36DG7Srz9uxbdbyF0yeKMg@mail.gmail.com%3e">how to enable MMapDirectory in solr 1.4?</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3c1312804620557-3235341.post@n3.nabble.com%3e">Multiplexing TokenFilter for multi-language?</a></h4>
<hr>
</div>
</div>
Modified: websites/staging/lucene/trunk/content/lucene/whoweare.html
==============================================================================
--- websites/staging/lucene/trunk/content/lucene/whoweare.html (original)
+++ websites/staging/lucene/trunk/content/lucene/whoweare.html Mon Aug 8 15:13:06 2011
@@ -244,6 +244,186 @@
<li><em>Karl Wettin</em> (kalle@...) </li>
</ul>
<p>Note that the email addresses above end with @apache.org. </p></div>
+
+ <div><h1 id="news">News</h1>
+<h2 id="28_july_2011_-_warning_index_corruption_and_crashes_in_apache_lucene_core__apache_solr_with_java_7">28 July 2011 - WARNING: Index corruption and crashes in Apache Lucene Core / Apache Solr with Java 7</h2>
+<p>Oracle released <a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Java 7</a> today.
+Unfortunately it contains hotspot compiler optimizations, which miscompile some loops.
+This can affect code of several Apache projects. Sometimes JVMs only crash, but in several cases,
+results calculated can be incorrect, leading to bugs in applications
+(see Hotspot bugs <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7070134">7070134</a>,
+<a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7044738">7044738</a>,
+<a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7068051">7068051</a>).
+<strong>Apache Lucene Core</strong> and <strong>Apache Solr</strong> are two Apache projects,
+which are affected by these bugs, namely all versions released until today.
+Solr users with the default configuration will have
+Java crashing with <code>SIGSEGV</code> as soon as they start to index documents, as one
+affected part is the well-known Porter stemmer
+(see <a href="https://issues.apache.org/jira/browse/LUCENE-3335">LUCENE-3335</a>).
+Other loops in Lucene may be miscompiled, too, leading to index corruption
+(especially on Lucene trunk with pulsing codec; other loops may be
+affected, too - <a href="https://issues.apache.org/jira/browse/LUCENE-3346">LUCENE-3346</a>).
+These problems were detected only 5 days before the official Java 7 release,
+so Oracle had no time to fix those bugs, affecting also many more applications.
+In response to our questions, they proposed to include the fixes into service
+release u2 (eventually into service release u1, see
+<a href="http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2011-July/005971.html">this mail</a>).
+<strong>This means you cannot use Apache Lucene/Solr with Java 7 releases before Update 2!</strong>
+If you do, please don't open bug reports, it is not the committers' fault!
+At least disable loop optimizations using the <code>-XX:-UseLoopPredicate</code> JVM option
+to not risk index corruptions.
+<em>Please note:</em> Also Java 6 users are affected, if they use one of those
+JVM options, which are <strong>not</strong> enabled by default: <code>-XX:+OptimizeStringConcat</code>
+or <code>-XX:+AggressiveOpts</code>.
+It is strongly recommended not to use any hotspot optimization switches in any Java
+version without extensive testing!
+In case you upgrade to Java 7, remember that you may have to reindex, as the unicode
+version shipped with Java 7 changed and tokenization behaves differently
+(e.g. lowercasing). For more information, read <code>JRE_VERSION_MIGRATION.txt</code>
+in your distribution package!</p>
+<h2 id="1_july_2011_-_lucene_core_33_and_solr_33_available">1 July 2011 - Lucene Core 3.3 and Solr 3.3 Available</h2>
+<p>The Lucene PMC is pleased to announce the availability of Apache Lucene 3.3 and Apache Solr 3.3.</p>
+<p>Lucene can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/java/">http://www.apache.org/dyn/closer.cgi/lucene/java/</a> and Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a>
+Highlights of the Lucene release include:</p>
+<ul>
+<li>The spellchecker module now includes suggest/auto-complete functionality,
+ with three implementations: Jaspell, Ternary Trie, and Finite State.</li>
+<li>Support for merging results from multiple shards, for both "normal"
+ search results (TopDocs.merge) as well as grouped results using the
+ grouping module (SearchGroup.merge, TopGroups.merge).</li>
+<li>An optimized implementation of KStem, a less aggressive stemmer
+ for English</li>
+<li>Single-pass grouping implementation based on block document indexing.</li>
+<li>Improvements to MMapDirectory (now also the default implementation
+ returned by FSDirectory.open on 64-bit Linux).</li>
+<li>NRTManager simplifies handling near-real-time search with multiple
+ search threads, allowing the application to control which indexing
+ changes must be visible to which search requests.</li>
+<li>TwoPhaseCommitTool facilitates performing a multi-resource
+ two-phased commit, including IndexWriter.</li>
+<li>The default merge policy, TieredMergePolicy, has a new method
+ (set/getReclaimDeletesWeight) to control how aggressively it
+ targets segments with deletions, and is now more aggressive than
+ before by default.</li>
+<li>PKIndexSplitter tool splits an index by a mid-point term.</li>
+</ul>
+<p>Highlights of the Solr release include:</p>
+<ul>
+<li>Grouping / Field Collapsing</li>
+<li>A new, automaton-based suggest/autocomplete implementation offering an
+ order of magnitude smaller RAM consumption.</li>
+<li>KStemFilterFactory, an optimized implementation of a less aggressive
+ stemmer for English.</li>
+<li>Solr defaults to a new, more efficient merge policy (TieredMergePolicy).
+ See <a href="http://s.apache.org/merging">http://s.apache.org/merging</a> for more information.</li>
+<li>Important bugfixes, including extremely high RAM usage in spellchecking.</li>
+<li>Bugfixes and improvements from Apache Lucene 3.3</li>
+</ul>
+<h2 id="4_june_2011_-_lucene_core_32_and_solr_32_available">4 June 2011 - Lucene Core 3.2 and Solr 3.2 Available</h2>
+<p>The Lucene PMC is pleased to announce the availability of Apache Lucene 3.2 and Apache Solr 3.2.</p>
+<p>Lucene can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/java/">http://www.apache.org/dyn/closer.cgi/lucene/java/</a> and Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a>
+Highlights of the Lucene release include:</p>
+<ul>
+<li>A new grouping module, under lucene/contrib/grouping, enables
+ search results to be grouped by a single-valued indexed field</li>
+<li>A new IndexUpgrader tool fully converts an old index to the
+ current format.</li>
+<li>A new Directory implementation, NRTCachingDirectory, caches small
+ segments in RAM, to reduce the I/O load for applications with fast
+ NRT reopen rates.</li>
+<li>A new Collector implementation, CachingCollector, is able to
+ gather search hits (document IDs and optionally also scores) and
+ then replay them. This is useful for Collectors that require two
+ or more passes to produce results.</li>
+<li>Index a document block using IndexWriter's new addDocuments or
+ updateDocuments methods. These experimental APIs ensure that the
+ block of documents will forever remain contiguous in the index,
+ enabling interesting future features like grouping and joins.</li>
+<li>A new default merge policy, TieredMergePolicy, which is more
+ efficient due to being able to merge non-contiguous segments.
+ See <a href="http://s.apache.org/merging">http://s.apache.org/merging</a> for details.</li>
+<li>NumericField is now returned correctly when you load a stored
+ document (previously you received a normal Field back, with the
+ numeric value converted string).</li>
+<li>Deleted terms are now applied during flushing to the newly flushed
+ segment, which is more efficient than having to later initialize a
+ reader for that segment.</li>
+</ul>
+<p>Highlights of the Solr release include:</p>
+<ul>
+<li>Ability to specify overwrite and commitWithin as request parameters when
+ using the JSON update format.</li>
+<li>TermQParserPlugin, useful when generating filter queries from terms
+ returned from field faceting or the terms component.</li>
+<li>DebugComponent now supports using a NamedList to model Explanation objects
+ in its responses instead of Explanation.toString.</li>
+<li>Improvements to the UIMA and Carrot2 integrations.</li>
+<li>Highlighting performance improvements. </li>
+<li>A test-framework jar for easy testing of Solr extensions.</li>
+<li>Bugfixes and improvements from Apache Lucene 3.2. </li>
+</ul>
+<h2 id="31_march_2011_-_lucene_core_31_and_solr_31_available">31 March 2011 - Lucene Core 3.1 and Solr 3.1 Available</h2>
+<p>The Lucene PMC is pleased to announce the availability of Apache Lucene 3.1 and Apache Solr 3.1.
+The version number for Solr 3.1 was chosen to reflect the merge of
+development with Lucene, which is currently also on 3.1. Going
+forward, we expect the Solr version to be the same as the Lucene
+version. Solr 3.1 contains Lucene 3.1 and is the release after Solr 1.4.1.</p>
+<p>Lucene can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/java/">http://www.apache.org/dyn/closer.cgi/lucene/java/</a> and Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a>
+Highlights of the Lucene release include:</p>
+<ul>
+<li>Numerous performance improvements: faster exact PhraseQuery; merging
+favors segments with deletions; primary key lookup is faster;
+IndexWriter.addIndexes(Directory[]) uses file copy instead of
+merging; various Directory performance improvements; compound file
+is dynamically turned off for large segments; fully deleted segments
+are dropped on commit; faster snowball analyzers (in contrib);
+ConcurrentMergeScheduler is more careful about setting priority of
+merge threads.</li>
+<li>ReusableAnalyzerBase makes it easier to reuse TokenStreams
+correctly.</li>
+<li>Improved Analysis capabilities: Improved Unicode support, including
+Unicode 4, more friendly term handling (CharTermAttribute), easier
+object reuse and better support for protected words in lossy token
+filters (e.g. stemmers).</li>
+<li>ConstantScoreQuery now allows directly wrapping a Query.</li>
+<li>IndexWriter is now configured with a new separate builder API,
+IndexWriterConfig. You can now control IndexWriter's previously
+fixed internal thread limit by calling setMaxThreadStates.</li>
+<li>IndexWriter.getReader is replaced by IndexReader.open(IndexWriter).
+In addition you can now specify whether deletes should be resolved
+when you open an NRT reader.</li>
+<li>MultiSearcher is deprecated; ParallelMultiSearcher has been
+absorbed directly into IndexSearcher.</li>
+<li>On 64bit Windows and Solaris JVMs, MMapDirectory is now the
+default implementation (returned by FSDirectory.open).
+MMapDirectory also enables unmapping if the JVM supports it.</li>
+<li>New TotalHitCountCollector just counts total number of hits.</li>
+<li>ReaderFinishedListener API enables external caches to evict entries
+once a segment is finished.</li>
+</ul>
+<p>Highlights of the Solr release include:</p>
+<ul>
+<li>Numeric range facets (similar to date faceting).</li>
+<li>New spatial search, including spatial filtering, boosting and sorting capabilities.</li>
+<li>Example Velocity driven search UI at http://localhost:8983/solr/browse</li>
+<li>A new termvector-based highlighter</li>
+<li>Extend dismax (edismax) query parser which addresses some
+missing features in the dismax query parser along with some
+extensions.</li>
+<li>Several more components now support distributed mode:
+TermsComponent, SpellCheckComponent.</li>
+<li>A new Auto Suggest component.</li>
+<li>Ability to sort by functions.</li>
+<li>JSON document indexing.</li>
+<li>CSV response format.</li>
+<li>Apache UIMA integration for metadata extraction.</li>
+<li>Leverages Lucene 3.1 and it's inherent optimizations and bug fixes
+as well as new analysis capabilities.</li>
+<li>Numerous improvements, bug fixes, and optimizations.</li>
+</ul></div>
+
+ <div><h2 id="the_apache_software_foundation">The Apache Software Foundation</h2>
+<p>The <a href="http://www.apache.org">Apache Software Foundation</a> provides support for the Apache community of open-source software projects. The Apache projects are defined by collaborative consensus based processes, an open, pragmatic software license and a desire to create high quality software that leads the way in its field. Apache Lucene, Apache Solr, Apache PyLucene, Apache Open Relevance Project and their respective logos are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p></div>
</div>
<div id="sidebar">
@@ -281,13 +461,13 @@
<div id="dev-mail">
<h1>Latest Dev</h1>
<div class="status-item">
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3cCAAHmpkg9jrb96UEATwaSbP+CULY2ZPHMcnDQrHmardr+-hXCrw@mail.gmail.com%3e">Re: [VOTE]: Accept Kuromoji code donation to Apache Lucene</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c2017944810.16645.1312813707315.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-2654) <lockType/> not used consistently in all places Directory objects are instantiated</a></h4>
<hr>
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c1934488272.31281312809355610.JavaMail.hudson@aegis%3e">[JENKINS] Lucene-Solr-tests-only-3.x - Build # 10082 - Failure</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c485501116.16643.1312813707244.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (LUCENE-3298) FST has hard limit max size of 2.1 GB</a></h4>
<hr>
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c83F112F7-2573-4557-AC1B-C1595D610727@apache.org%3e">Re: [VOTE]: Accept Kuromoji code donation to Apache Lucene</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201108.mbox/%3c394646490.16631.1312813467194.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Updated] (LUCENE-3357) Unit and integration test cases for the new Similarities</a></h4>
<hr>
</div>
</div>
@@ -307,13 +487,13 @@
<div id="solr-user-mail">
<h1>Latest Solr User</h1>
<div class="status-item">
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3c1312804620557-3235341.post@n3.nabble.com%3e">Multiplexing TokenFilter for multi-language?</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3cCABCJ++JpY3S0KG+USqvyZSk+tpwTLX+N1fY8UXGh=LHNDsHYcw@mail.gmail.com%3e">PositionIncrement gap and multi-valued fields.</a></h4>
<hr>
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3cCAM0cPW7dxRipV3hcJU-mvGU9LbJhbiA_rY1K-=-B3KQEf3YHAA@mail.gmail.com%3e">Re: strip html from data</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3c8F0D0142CA7ECC4287A9EC1BD8CB880C17C72DB2D5@USLVDCMBVP01.ingramcontent.com%3e">RE: how to enable MMapDirectory in solr 1.4?</a></h4>
<hr>
- <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3cCAFAd71XSa5+9yQF+JCBcE2qC0rkX36DG7Srz9uxbdbyF0yeKMg@mail.gmail.com%3e">how to enable MMapDirectory in solr 1.4?</a></h4>
+ <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201108.mbox/%3c1312804620557-3235341.post@n3.nabble.com%3e">Multiplexing TokenFilter for multi-language?</a></h4>
<hr>
</div>
</div>