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 2012/01/31 18:41:30 UTC

svn commit: r803662 - /websites/staging/lucene/trunk/content/core/index.html

Author: buildbot
Date: Tue Jan 31 17:41:30 2012
New Revision: 803662

Log:
Staging update by buildbot for lucene

Modified:
    websites/staging/lucene/trunk/content/core/index.html

Modified: websites/staging/lucene/trunk/content/core/index.html
==============================================================================
--- websites/staging/lucene/trunk/content/core/index.html (original)
+++ websites/staging/lucene/trunk/content/core/index.html Tue Jan 31 17:41:30 2012
@@ -319,102 +319,6 @@ in your distribution package!</p></div>
       <p>DirectoryReader is final and has only static factory methods. It is not possible to subclass it in any way.</p>
 
 <p>The...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-1812">[LUCENE-1812] Static index pruning by in-document term frequency (Carmel pruning)</a><br/>
-      <p>This module provides tools to produce a subset of input indexes by removing postings data for those terms where their...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3716">[LUCENE-3716] Discussion topic: Move all Commit/Version&amp;Reopen stuff from abstract IR to DirectoryReader</a><br/>
-      <p>When implementing the parent issue, I noticed a lot of other stuff in IndexReader thats only implemented in DirectoryReader/SegmentReader and...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3736">[LUCENE-3736] ParallelReader is now atomic, add convenience methods to wrap CompositeReaders in either &quot;slow atomic&quot; or &quot;fast composite&quot; way</a><br/>
-      <p>ParallelReader is now atomic. We should add a sugar wrapper method to allow synchronized composite readers (with same segment sizes)...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3733">[LUCENE-3733] Remaining TODOs of LUCENE-2858: Finalize AtomicReader/CompositeReader API</a><br/>
-      <p>This issue will handle the remaining issues in the commit last night (<a href="https://issues.apache.org/jira/browse/LUCENE-2858" title="Separate SegmentReaders (and other atomic readers) from composite IndexReaders"><del>LUCENE-2858</del></a>). A new branch will be...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-2858">[LUCENE-2858] Separate SegmentReaders (and other atomic readers) from composite IndexReaders</a><br/>
-      <p>With current trunk, whenever you open an IndexReader on a directory you get back a DirectoryReader which is a composite...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3396">[LUCENE-3396] Make TokenStream Reuse Mandatory for Analyzers</a><br/>
-      <p>In <a href="https://issues.apache.org/jira/browse/LUCENE-2309" title="Fully decouple IndexWriter from analyzers"><del>LUCENE-2309</del></a> it became clear that we&apos;d benefit a lot from Analyzer having to return reusable TokenStreams.  This is a...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3721">[LUCENE-3721] CharFilters not being invoked in Solr</a><br/>
-      <p><br/>
-On Solr trunk, <b>all</b> CharFilters have been non-functional since <a href="https://issues.apache.org/jira/browse/LUCENE-3396" title="Make TokenStream Reuse Mandatory for Analyzers"><del>LUCENE-3396</del></a> was committed in r1175297 on 25 Sept 2011, until Yonik&apos;s...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3732">[LUCENE-3732] overview.html needs help</a><br/>
-      <p>When you open javadocs, this is the very first thing you see (index.html).</p>
-
-<p>It has a bunch of sample code...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3728">[LUCENE-3728] better handling of files inside/outside CFS by codec</a><br/>
-      <p>Since norms and deletes were moved under Codec (<a href="https://issues.apache.org/jira/browse/LUCENE-3606" title="Make IndexReader really read-only in Lucene 4.0"><del>LUCENE-3606</del></a>, <a href="https://issues.apache.org/jira/browse/LUCENE-3661" title="move deletes under codec"><del>LUCENE-3661</del></a>),<br/>
-we never really properly addressed the issue...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3729">[LUCENE-3729] Allow using FST to hold terms data in DocValues.BYTES_*_SORTED</a><br/>
-      
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3730">[LUCENE-3730] Improved Kuromoji search mode segmentation/decompounding</a><br/>
-      <p>Kuromoji has a segmentation mode for search that uses a heuristic to promote additional segmentation of long candidate tokens to...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3725">[LUCENE-3725] Add optional packing to FST building</a><br/>
-      <p>The FSTs produced by Builder can be further shrunk if you are willing<br/>
-to spend highish transient RAM to do...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3731">[LUCENE-3731] Create a analysis/uima module for UIMA based tokenizers/analyzers</a><br/>
-      <p>As discussed in <a href="https://issues.apache.org/jira/browse/SOLR-3013" title="Add UIMA based tokenizers / filters that can be used in the schema.xml">SOLR-3013</a> the UIMA Tokenizers/Analyzer should be refactored out in a separate module (modules/analysis/uima) as they can be...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3726">[LUCENE-3726] Default KuromojiAnalyzer to use search mode</a><br/>
-      <p>Kuromoji supports an option to segment text in a way more suitable for search,<br/>
-by preventing long compound nouns as...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3719">[LUCENE-3719] FVH: slow performance on very large queries</a><br/>
-      <p>The change from HashSet to ArrayList for flatQueries in <a href="https://issues.apache.org/jira/browse/LUCENE-3019" title="FVH: uncontrollable color tags"><del>LUCENE-3019</del></a> resulted in very significant slowdown in some of our e-discovery...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3727">[LUCENE-3727] fix assertions/checks that use File.length() to use getFilePointer()</a><br/>
-      <p>This came up on this thread "Getting RuntimeException: after flush: fdx size mismatch while Indexing" <br/>
-(<a href="http://www.lucidimagination.com/search/document/a8db01a220f0a126">http://www.lucidimagination.com/search/document/a8db01a220f0a126</a>)</p>
-
-<p>In trunk,...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3714">[LUCENE-3714] add suggester that uses shortest path/wFST instead of buckets</a><br/>
-      <p>Currently the FST suggester (really an FSA) quantizes weights into buckets (e.g. single byte) and puts them in front of...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-2795">[LUCENE-2795] Genericize DirectIOLinuxDir -&gt; UnixDir</a><br/>
-      <p>Today DirectIOLinuxDir is tricky/dangerous to use, because you only want to use it for indexWriter and not IndexReader (searching).  It&apos;s...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3661">[LUCENE-3661] move deletes under codec</a><br/>
-      <p>After <a href="https://issues.apache.org/jira/browse/LUCENE-3631" title="Remove write access from SegmentReader and possibly move to separate class or IndexWriter/BufferedDeletes/..."><del>LUCENE-3631</del></a>, this should be easier I think.</p>
-
-<p>I haven&apos;t looked at it much myself but i&apos;ll play around...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-1817">[LUCENE-1817] it is impossible to use a custom dictionary for SmartChineseAnalyzer</a><br/>
-      <p>it is not possible to use a custom dictionary, even though there is a lot of code and javadocs to...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3722">[LUCENE-3722] make similarities/term/collectionstats take long (for &gt; 2B docs)</a><br/>
-      <p>As noted by Yonik and Andrzej on <a href="https://issues.apache.org/jira/browse/SOLR-1632" title="Distributed IDF">SOLR-1632</a>, this would be useful for distributed scoring.</p>
-
-<p>we can also add...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3672">[LUCENE-3672] IndexCommit.equals() bug</a><br/>
-      <p>IndexCommit.equals() checks for equality of Directories and versions, but it doesn&apos;t check IMHO the more important generation numbers. It looks...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3720">[LUCENE-3720] OOM in TestBeiderMorseFilter.testRandom</a><br/>
-      <p>This has been OOM&apos;ing a lot... we should see why, its likely a real bug.</p>
-
-<p>ant test -Dtestcase=TestBeiderMorseFilter -Dtestmethod=testRandom -Dtests.seed=2e18f456e714be89:310bba5e8404100d:-3bd11277c22f4591...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3724">[LUCENE-3724] SimpleText sumTotalTermFreq is wrong if only positions are omitted</a><br/>
-      <p>ant test -Dtestcase=TestOmitPositions -Dtestmethod=testBasic -Dtests.seed=-6c9bd4a6197b9463:-71d0d11bc2db9a15:697690b3dff2369 -Dargs="-Dfile.encoding=UTF-8"<br/>
-    <span class="error">&#91;junit&#93;</span> java.lang.AssertionError: sumTotalTermFreq=0,sumDocFreq=400<br/>
-    <span class="error">&#91;junit&#93;</span> 	at org.apache.lucene.search.CollectionStatistics.&lt;init&gt;(CollectionStatistics.java:38)</p>
-
-<p>This assert fails because #of positions for the...</p>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3723">[LUCENE-3723] Remove FieldMaskingSpanQuery (or fix its scoring)</a><br/>
-      <p>In Lucene 4.0 we added new scoring mechanisms, but FieldMaskingSpanQuery is a serious problem:</p>
-
-<p>Because it lies about the fields...</p>
     </div></div>
     <div id="dev-mail">
       <h1>Latest Dev</h1>