[fw-formats] Unitialized string offset

hi,

"Do not use networked file systems with Zend_Search_Lucene" period end of
paragraph (a new addition to
http://framework.zend.com/manual/en/zend.search.lucene.index-creation.html#zend.search.lucene.index-creation.limitations.filesystems).
Why are no networked file systems safe? Flock() isn't safe with Apache if
the indexes are on a Windows Network?

Perhaps not--I just searched for "test", got "error [8] Uninitialized string
offset: 0 on line 161 in file
C:\xampplite\php\zf\Zend\Search\Lucene\Storage\File.php", searched for
"design", got a few hits, searched for "test" again, and it worked without
error. We're using ZSL in production and it's not working smooth enough...

What should my error_reporting() be set to when using ZSL? E_ERROR?

What's the best way to test a Lucene index for corruption? Are detection
and repair utilities for this in development (pls) ?

http://framework.zend.com/manual/en/zend.search.lucene.best-practice.html#zend.search.lucene.best-practice.maintenance
has:
"If index corruption occures [sic] for any reason, the corrupted index
should be restored or completely rebuilt.
"So it's a good idea to backup large indexes and store changelogs to
perform manual restoration and roll-forward operations if necessary."
How does one create a changelog that allows rolling Lucene forward?

What are the ZSL changes in ZF1.6? I tried searching but
http://framework.zend.com/search?query=release+notes&language=en&type=all&x=0&y=0
currently returns "HTTP 500 - Internal server error".

thanks alot,
george herson
--
View this message in context: http://www.nabble.com/Unitialized-string-offset-tp19414579p19414579.html
Sent from the Zend MFS mailing list archive at Nabble.com.