REST Resources Flush
Please provide documentation on what the flush variable is
doing? What is the behavior? Is it kind of like a db commit (needs
to be called with true at the end)? Or is it different (it will
eventually get into the memory if you wait long enough)?
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Chet Patel on 01 Apr, 2010 09:06 PM
flush is only required if you are querying the data. For batch ingest, multiple resources can be queued up for ingestion via the REST api. This does not require flush. After the resources are processed by server, the data is automatically flushed. But if you are doing a batch ingest and users are simultaneously querying the data then to ensure the correct results you have to flush. There is a down side to this performance wise. So you can balance the performance/query problem by setting flush to true every 5000 resources or so. This really depends on the number of resources you are ingesting. Of course if this is done at night where no one is querying the data, then set flush to false.
Support Staff 3 Posted by Jim Fleming on 04 May, 2010 08:28 PM
Issue has been resolved.
Jim Fleming closed this discussion on 04 May, 2010 08:28 PM.