Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>you appear to be mixing up your documentation. If you are using Lucene 4.3.0, use the documentation for it (see the correct documentation for <a href="http://lucene.apache.org/core/4_3_0/core/org/apache/lucene/index/TieredMergePolicy.html" rel="nofollow"><code>TieredMergePolicy</code></a> in 4.3.0), rather than for version 3.2.0. </p> <p>Anyway, on these particular questions: <a href="https://issues.apache.org/jira/browse/LUCENE-3577" rel="nofollow">See #Lucene-3577</a></p> <p>1 - Seems to be mainly a necessary name change, for all intents and purposes.</p> <p>2 - Firstly, <code>IndexWriter.expungeDeletes</code> no longer exists in 4.3.0. You can use <a href="http://lucene.apache.org/core/4_3_0/core/org/apache/lucene/index/IndexWriter.html#forceMergeDeletes%28%29" rel="nofollow"><code>IndexWriter.forceMergeDeletes()</code></a>, if you must, though it is strongly recommended against, as it is very, very costly. I believe this will only impact a <code>ForceMergeDeletes()</code> call. If you want to favor reclaiming deletions, set that in the MergePolicy, using: <a href="http://lucene.apache.org/core/4_3_0/core/org/apache/lucene/index/TieredMergePolicy.html#setReclaimDeletesWeight%28double%29" rel="nofollow"><code>TieredMergePolicy.setReclaimDeletesWeight</code></a></p> <p>3 - The percent allowed is right there in the method call you've indicated in your first question. Forcing all the deletions to be merged out when calling <code>ForceMergeDeletes()</code> will serve to make an already very expensive operation that much more expensive as well, though.</p> <p>Just to venture a guess, if you need to save disk space taken by your index, you'll likely have much more success looking more closely at how much data your are <em>storing</em> in the index. Not enough information to say for sure, of course, but seems a likely solution to consider.</p>
    singulars
    1. This table or related slice is empty.
    1. POInformations about TieredMergePolicy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USfemtoRgon
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POInformations about TieredMergePolicy
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you very much! It will help me to improve my merging strategy. By the way, I got another question about ReclaimDeletesWeight : Does it possible to set this value in the solrconfig.xml file ? For example : <mergePolicy class="org.apache.lucene.index.TieredMergePolicy"> <int name="maxMergeAtOnce">10</int> <int name="segmentsPerTier">10</int> <int name="ReclaimDeletesWeight">2.0</int> </mergePolicy> I don't understand very well the link between solrconfig.xml and Java Solr Classes...
      singulars
      1. PO
      1. USCorentin
    2. COIt should be a double, not an int (ie: `<double name="ReclaimDeletesWeight">2.0</double>`), but otherwise, yes. That should work fine. (2.0 is the default value, by the way)
      singulars
      1. PO
      1. USfemtoRgon
    3. COPerfect ! Thank you. Now it's much more clearer !
      singulars
      1. PO
      1. USCorentin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload