Opened 14 years ago
Closed 9 years ago
#519 closed enhancement (fixed)
omindex should allow indexing files it doesn't understand
Reported by: | Olly Betts | Owned by: | Olly Betts |
---|---|---|---|
Priority: | normal | Milestone: | 1.3.4 |
Component: | Omega | Version: | |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Operating System: | All |
Description
Users may want to index just the filenames and other filesystem metadata for files which omindex doesn't have a filter for.
Should be a compatible change, so marking as 1.2.x.
Change History (3)
comment:1 by , 14 years ago
comment:2 by , 13 years ago
Milestone: | 1.2.x → 1.3.x |
---|
comment:3 by , 9 years ago
Milestone: | 1.3.x → 1.3.4 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Implemented a special case for true
and documented this in [99e02ae01df059805e5e0265865ce7c4a568c59f].
Note:
See TracTickets
for help on using tickets.
This post has a suggested change to allow this:
http://article.gmane.org/gmane.comp.search.xapian.general/8598
But with the recent omindex changes, it might be cleaner to add a way to say "don't try to extract text from this MIME content-type". With trunk, I think this should actually already work (I've not actually tested it though):
-Mjpg:image/jpeg -Mjpeg:image/jpeg -Fimage/jpeg:/bin/true
But it's not the most obvious interface, and we want to avoid running /bin/true in a subshell for each such file.