The General crawl settings¶
This page is generated by Machine Translation from Japanese.
Overview¶
Describes the settings related to crawling.
Setting item¶
Scheduled full crawl frequency¶
You can set the interval at which the crawl for a Web site or file system. By default, the following.
0 0 0 * * ?
Figures are from left, seconds, minutes, during the day, month, represents a day of the week. Description format is similar to the Unix cron settings. For this example, am 0 時 0 分 in crawling daily.
Following are examples of how to write.
| 0 0 12 * *? | Each day starts at 12 pm |
| 0 15 10? * * | Day 10: 15 am start |
| 0 15 10 * *? | Day 10: 15 am start |
| 0 15 10 * *? * | Day 10: 15 am start |
| 0 15 10 * *? 2009 | Each of the 2009 start am, 10:15 |
| 0 * 14 * *? | Every day 2:00 in the PM-2: 59 pm start every 1 minute |
| 0 0 / 5 14 * *? | Every day 2:00 in the PM-2: 59 pm start every 5 minutes |
| 0 0 / 5 14, 18 * *? | Every day 2:00 pm-2: 59 pm and 6: 00 starts every 5 minutes at the PM-6: 59 pm |
| 0 0-5 14 * *? | Every day 2:00 in the PM-2: 05 pm start every 1 minute |
| 0 10, 44 14? 3 WED | Starts Wednesday March 2: 10 and 2: 44 pm |
| 0 15 10? * MON-FRI | Monday through Friday at 10:15 am start |
Also check if the seconds can be set to run at intervals 60 seconds by default. If you set seconds exactly and you should customize webapps/fess/WEB-INF/classes/chronosCustomize.dicon taskScanIntervalTime value, if enough do I see in one-hour increments.
Search log¶
When the user enters a search, the search the output log. If you want to get search statistics to enable.
User log¶
Save the information you find. Identifying the users becomes possible.
Favorite log¶
You can collect the search result was judged good by the user. Search result voting link appears to result in list screen, so that link press made the record. You can also reflect the results collected during the crawl index.
Add search parameters¶
Search results link attaches to the search term. To display the find search terms in PDF becomes possible.
XML response¶
Search results can be retrieved in XML format. http://localhost:8080/ Fess /XML? can get access query = search term.
JSON response¶
Search results available in JSON format. http://localhost:8080/ Fess /JSON? can get access query = search term.
Suggest API response¶
Suggest candidates for search suggestions can be retrieved in XML or JSON format. If you want to get the words beginning with ‘test’ is the http://localhost:8080/fess/json? type = suggest
Analysis API response¶
Morphological analysis of the results can be retrieved in XML or JSON format. If you want to apply morphological analysis on today’s weather is sunny’s http://localhost:8080/fess/json? type = analysis
Mobile translation¶
If these PC website search results on mobile devices may not display correctly. And select the mobile conversion, such as if the PC site for mobile terminals, and to show that you can. You can if you choose Google Google Wireless Transcoder allows to display content on mobile phones. For example, if site for PC and mobile devices browsing the results in the search for mobile terminals search results will link in the search result link passes the Google Wireless Transcoder. You can use smooth mobile transformation in mobile search.
The default label value¶
You can specify the label to see if the label by default,. Specifies the value of the label.
Search support¶
You can specify whether or not to display a search screen. If you select Web unusable for mobile search screen. If not available not available search screen. And if you want to create a dedicated index server and select not available.
Featured keyword response¶
In JSON format often find search words becomes available. can be retrieved by accessing the http://localhost:8080/ Fess /hotsearchword.
Specify the number of days before session information removed¶
Delete a session log for the specified number of days ago. One day in the one log purge old log is deleted.
Specify the number of days before search log delete¶
Delete a search log for the specified number of days ago. One day in the one log purge old log is deleted.
Log deletion Bots name¶
Specifies the Bots name Bots you want to remove from the search log logs included in the user agent by commas (,). Log is deleted by log purge once a day.
CSV encoding¶
Specifies the encoding for the CSV will be available in the backup and restore.
Index commit, optimize¶
After the data is registered for Solr. Index to commit or to optimize the registered data becomes available. If optimize is issued the Solr index optimization, if you have chosen, you choose to commit the commit is issued.
Server switchovers¶
Fess can combine multiple Solr server as a group, the group can manage multiple. Solr server group for updates and search for different groups to use. For example, if you had two groups using the Group 2 for update, search for use of Group 1. After the crawl has been completed if switching server updates for Group 1, switches to group 2 for the search. It is only valid if you have registered multiple Solr server group.
Committed to the document number of each¶
In Fess in 10 units send the document for Solr. For each value specified here Solr issued document commits. If 0 commit is performed after crawl completion.
Number of concurrent crawls settings¶
Fess document crawling is done on Web crawling, and file system CROLL. You can crawl to a set number of values in each crawl specified here only to run simultaneously multiple. For example, crawl setting number of concurrent as 3 Web crawling set 1-set 10 if the crawling runs until the set 3 3 set 1-. Complete crawl of any of them, and will start the crawl settings 4. Similarly, setting 10 to complete one each in we will start one.
But you can specify the number of threads in the crawl settings simultaneously run crawl setting number is not indicates the number of threads to start. For example, if 3 in the number of concurrent crawls settings, number of threads for each crawl settings and 5 3 x 5 = 15 thread count up and crawling.
Expiration date of the index¶
You can automatically delete data after the data has been indexed. If you select the 5, with the expiration of index register at least 5 days before and had no update is removed. If you omit data content has been removed, can be used.
Disability types to exclude¶
Registered disabled URL URL exceeds the failure count next time you crawl to crawl out. Does not need to monitor the fault type is being crawled next time by specifying this value.
Failure count¶
Disaster URL exceeds the number of failures will crawl out.