Revision: 18060
http://sourceforge.net/p/gate/code/18060
Author: ian_roberts
Date: 2014-06-10 17:11:33 +0000 (Tue, 10 Jun 2014)
Log Message:
-----------
Typos
Modified Paths:
--------------
mimir/trunk/doc/introduction.tex
Modified: mimir/trunk/doc/introduction.tex
===================================================================
--- mimir/trunk/doc/introduction.tex 2014-06-10 17:09:30 UTC (rev 18059)
+++ mimir/trunk/doc/introduction.tex 2014-06-10 17:11:33 UTC (rev 18060)
@@ -133,7 +133,7 @@
indexing} mode, when it would accept new documents for indexing. When all the
documents had been indexed, the index would need to be {\em closed}, which
would
switch its operation mode to {\em searching}, and the index would then be able
-to answer queries. Once closed, and index could not accept any further
docuemnts
+to answer queries. Once closed, and index could not accept any further
documents
for indexing. Starting with version $5.0$, a MÃmir index is continually
accepting documents to be indexed and can answer queries that address the
currently indexed document set. From being sent to \Mimir{} for indexing to
@@ -143,7 +143,7 @@
Documents submitted for indexing are initially accumulated in RAM, during
which time they are not available for being searched. A {\em sync-to-disk}
operation writes all the documents currently in RAM to disk, in the form of an
-{\em index batch}, after which the docuemnts can be searched. Sync-to-disk
+{\em index batch}, after which the documents can be searched. Sync-to-disk
operations happen automatically when too much document data has been
accumulated
in RAM, or after a given time interval has passed since the last sync.
Alternatively, the user can also trigger a sync operation from index admin web
@@ -162,4 +162,4 @@
(e.g. the {\tt mimir-cloud} web application) will automatically close all
currently open indexes. Users should never forcefully destroy the mimir server
process, as that would not allow the close operations to be performed, which
can
-lead to data loss, or it can corrupt existing indexes.
\ No newline at end of file
+lead to data loss, or it can corrupt existing indexes.
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
GATE-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gate-cvs
