I was testing the new feature for lastmodified date in the latest 2.1
dev release and I think I found a bug with the indexing of binary files
but I need confirmation on if this is a bug or expected behavior.
In 1.3 and 2.0.5 I was able to index a .doc or .xls file even though it
was binary. Now when I index these types of files I get the following
Warning: Possible embedded null in file '/www/html/.../SurveyQues
The same file works fine for indexing and searching in 2.0.5.
I notice that in 2.1 there is a Document Filter Directive to preprocess
a file in an external program. Is this now required (and what I am
seeing above is expected behavior) or should I still be able to index
binary files (and thus, should I report my issue above as a bug?).
I should add that is is very convenient that swish 2.0.5 just indexed
the files 'as-is'. If I do have to use the Document Filter, can i just
run the files thru the UNIX strings command? All I really care about is
the strings inside the file anyays.
Bill Moseley wrote:
> At 06:48 PM 05/27/01 -0700, Steve McMillen wrote:
> >It would be very helpful to be able to have the last modified date in
> >the index file that swish-e generates.
> Yes it would.
> >In my case I would like to be able to just report that information to in
> >the search results since it helps the user decide relevance of the
> > swish-e -w not ssksk -x '<swishlastmodified>\n' -m 1
> # SWISH format: 2.1-dev-21
> # Search words: not ssksk
> # Number of hits: 121
> # Search time: 0.000 seconds
> # Run time: 0.007 seconds
> 2000-02-23 15:11:39
> Development version is at http://sunsite.berkeley.edu:4444/swish-daily/
> Yes, you can sort by the date, too. (Just can't select a date range as a
> meta name. Someday.)
> Some more info at http://sunsite.berkeley.edu:4444/SWISH-RUN.html.
> Bill Moseley
Received on Fri Jun 1 01:22:08 2001