The Updateattributes method of Sphinx

Sphinx performed updateattributes when it was running. After execution, you can find the updated data.
But after a while it seems to have changed back to the original data. Not quite sure, but it should be.

I checked the updateattributes related content, said this is to modify the current memory in the data, if you want to modify the file, you need to restart the engine.

My question is, does modifying the data in memory mean that this value is kept in memory until Sphinx is restarted?
Or, when the document is moved out of memory, the change information is moved out? Cause the next time the document is re-imported into memory, only old data can be imported?

Our engine has been kept open and will not be restarted. Does this have any drawbacks?

Reply content:

Sphinx performed updateattributes when it was running. After execution, you can find the updated data.
But after a while it seems to have changed back to the original data. Not quite sure, but it should be.

I checked the updateattributes related content, said this is to modify the current memory in the data, if you want to modify the file, you need to restart the engine.

My question is, does modifying the data in memory mean that this value is kept in memory until Sphinx is restarted?
Or, when the document is moved out of memory, the change information is moved out? Cause the next time the document is re-imported into memory, only old data can be imported?

Our engine has been kept open and will not be restarted. Does this have any drawbacks?

Sphinx The storage mode of document information, including None,extern,inline. The default is extern, and when you use extern, the document's properties are stored in another file (SPD), but when you start Searchd, the file is loaded into memory.

After removal, it is lost and can be written back to disk via Attr_flush_period control, at how many times.

Resources:
Http://www.coreseek.cn/docs/coreseek_4.1-sphinx_2.0.1-beta.html
Http://www.cnblogs.com/yjf512/p/3598332.html

