Changeset 4325


Ignore:
Timestamp:
01/23/14 15:08:59 (10 years ago)
Author:
twagoo
Message:

Upgraded to SOLR 4.6 (version configured through property in parent pom)
Configured SLF4J version via parent pom as well

Location:
vlo/branches/vlo-3.0/vlo-solr/src/main/solr_conf/solr/collection1
Files:
2 added
13 deleted
16 copied
1 moved

Legend:

Unmodified
Added
Removed

  • vlo/branches/vlo-3.0/vlo-solr/src/main/solr_conf/solr/collection1/conf/schema.xml

    r4322 r4325  
    438438   <field name="_contentSearchRef" type="string" indexed="true" stored="true" multiValued="true" />
    439439   <field name="_landingPageRef" type="string" indexed="true" stored="true" multiValued="true" />
    440    <field name="_lastSeen" type="tdate" index="true" stored="true" multiValued="false" />
     440   <field name="_lastSeen" type="tdate" indexed="true" stored="true" multiValued="false" />
    441441   <field name="_searchPageRef" type="string" indexed="true" stored="true" multiValued="true" />
    442442   <field name="metadataSource" type="metadataSource" indexed="false" stored="true" multiValued="true" />
    … …  
    452452
    453453 <solrQueryParser defaultOperator="AND"/>
    454 
    455454</schema>
     455

  • vlo/branches/vlo-3.0/vlo-solr/src/main/solr_conf/solr/collection1/conf/solrconfig.xml

    r4322 r4325  
    2424-->
    2525<config>
     26    <luceneMatchVersion>LUCENE_40</luceneMatchVersion>
     27   
    2628  <!-- Set this to 'false' if you want solr to continue working after it has
    2729       encountered an severe configuration error.  In a production environment,
    … …  
    7072       If replication is in use, this should match the replication configuration. -->
    7173<!--   <dataDir></dataDir>-->
    72 
    73   <!-- WARNING: this <indexDefaults> section only provides defaults for index writers
    74        in general. See also the <mainIndex> section after that when changing parameters
    75        for Solr's main Lucene index. -->
    76   <indexDefaults>
    77    <!-- Values here affect all index writers and act as a default unless overridden. -->
    78     <useCompoundFile>false</useCompoundFile>
    79 
    80     <mergeFactor>10</mergeFactor>
    81     <!-- If both ramBufferSizeMB and maxBufferedDocs is set, then Lucene will flush
    82      based on whichever limit is hit first.  -->
    83     <!--<maxBufferedDocs>1000</maxBufferedDocs>-->
    84 
    85     <!-- Sets the amount of RAM that may be used by Lucene indexing
    86       for buffering added documents and deletions before they are
    87       flushed to the Directory.  -->
    88     <ramBufferSizeMB>32</ramBufferSizeMB>
    89     <!-- <maxMergeDocs>2147483647</maxMergeDocs> -->
    90     <maxFieldLength>20000</maxFieldLength>
    91     <writeLockTimeout>1000</writeLockTimeout>
    92     <commitLockTimeout>10000</commitLockTimeout>
    93 
    94     <!--
    95      Expert: Turn on Lucene's auto commit capability.  This causes intermediate
    96      segment flushes to write a new lucene index descriptor, enabling it to be
    97      opened by an external IndexReader.  This can greatly slow down indexing
    98      speed.  NOTE: Despite the name, this value does not have any relation to
    99      Solr's autoCommit functionality
    100      -->
    101     <!--<luceneAutoCommit>false</luceneAutoCommit>-->
    102 
    103     <!--
    104      Expert: The Merge Policy in Lucene controls how merging is handled by
    105      Lucene.  The default in 2.3 is the LogByteSizeMergePolicy, previous
    106      versions used LogDocMergePolicy.
    107 
    108      LogByteSizeMergePolicy chooses segments to merge based on their size.  The
    109      Lucene 2.2 default, LogDocMergePolicy chose when to merge based on number
    110      of documents
    111 
    112      Other implementations of MergePolicy must have a no-argument constructor
    113      -->
    114     <!--<mergePolicy class="org.apache.lucene.index.LogByteSizeMergePolicy"/>-->
    115 
    116     <!--
    117      Expert:
    118      The Merge Scheduler in Lucene controls how merges are performed.  The
    119      ConcurrentMergeScheduler (Lucene 2.3 default) can perform merges in the
    120      background using separate threads.  The SerialMergeScheduler (Lucene 2.2
    121      default) does not.
    122      -->
    123     <!--<mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/>-->
    124 
    125          
    126     <!--
    127       This option specifies which Lucene LockFactory implementation to use.
    128      
    129       single = SingleInstanceLockFactory - suggested for a read-only index
    130                or when there is no possibility of another process trying
    131                to modify the index.
    132       native = NativeFSLockFactory  - uses OS native file locking
    133       simple = SimpleFSLockFactory  - uses a plain file for locking
    134 
    135       (For backwards compatibility with Solr 1.2, 'simple' is the default
    136        if not specified.)
    137     -->
    138     <lockType>native</lockType>
    139     <!--
    140      Expert:
    141     Controls how often Lucene loads terms into memory -->
    142     <!--<termIndexInterval>256</termIndexInterval>-->
    143   </indexDefaults>
    144 
    145   <mainIndex>
    146     <!-- options specific to the main on-disk lucene index -->
    147     <useCompoundFile>false</useCompoundFile>
    148     <ramBufferSizeMB>32</ramBufferSizeMB>
    149     <mergeFactor>10</mergeFactor>
    150     <!-- Deprecated -->
    151     <!--<maxBufferedDocs>1000</maxBufferedDocs>-->
    152     <!--<maxMergeDocs>2147483647</maxMergeDocs>-->
    153 
    154     <!-- inherit from indexDefaults <maxFieldLength>10000</maxFieldLength> -->
    155 
    156     <!-- If true, unlock any held write or commit locks on startup.
    157          This defeats the locking mechanism that allows multiple
    158          processes to safely access a lucene index, and should be
    159          used with care.
    160          This is not needed if lock type is 'none' or 'single'
    161      -->
    162     <unlockOnStartup>false</unlockOnStartup>
    163    
    164     <!-- If true, IndexReaders will be reopened (often more efficient) instead
    165          of closed and then opened.  -->
    166     <reopenReaders>true</reopenReaders>
    167 
    168     <!--
    169      Expert:
    170     Controls how often Lucene loads terms into memory.  Default is 128 and is likely good for most everyone. -->
    171     <!--<termIndexInterval>256</termIndexInterval>-->
    172 
    173     <!--
    174         Custom deletion policies can specified here. The class must
    175         implement org.apache.lucene.index.IndexDeletionPolicy.
    176 
    177         http://lucene.apache.org/java/2_3_2/api/org/apache/lucene/index/IndexDeletionPolicy.html
    178 
    179         The standard Solr IndexDeletionPolicy implementation supports deleting
    180         index commit points on number of commits, age of commit point and
    181         optimized status.
    182 
    183         The latest commit point should always be preserved regardless
    184         of the criteria.
    185     -->
    186     <deletionPolicy class="solr.SolrDeletionPolicy">
    187       <!-- The number of commit points to be kept -->
    188       <str name="maxCommitsToKeep">1</str>
    189       <!-- The number of optimized commit points to be kept -->
    190       <str name="maxOptimizedCommitsToKeep">0</str>
    191       <!--
    192           Delete all commit points once they have reached the given age.
    193           Supports DateMathParser syntax e.g.
    194          
    195           <str name="maxCommitAge">30MINUTES</str>
    196           <str name="maxCommitAge">1DAY</str>
    197       -->
    198     </deletionPolicy>
    199 
    200     <!--  To aid in advanced debugging, you may turn on IndexWriter debug logging.
    201       Setting to true will set the file that the underlying Lucene IndexWriter
    202       will write its debug infostream to.  -->
    203      <infoStream file="INFOSTREAM.txt">false</infoStream>
    204 
    205   </mainIndex>
    20674
    20775  <!--  Enables JMX if and only if an existing MBeanServer is found, use this
    … …  
    1039907       every xsltCacheLifetimeSeconds. 
    1040908   -->
    1041   <queryResponseWriter name="xslt" class="org.apache.solr.request.XSLTResponseWriter">
     909  <queryResponseWriter name="xslt" class="org.apache.solr.response.XSLTResponseWriter">
    1042910    <int name="xsltCacheLifetimeSeconds">5</int>
    1043911  </queryResponseWriter>
Note: See TracChangeset for help on using the changeset viewer.