Luis Filipe Nassif commented on TIKA-1466:

>From [~gagravarr] on dev list:
{quote}What happens if you have two different custom files which both claim the 
same glob?

We have historically been a bit stricter about built-in types overriding, in 
part to avoid people doing silly things by mistake, and in part to push people 
a bit more towards contributing fixes/enhancements for built-in types. I think 
the latter is less of a thing today, as we've a lot more covered as standard, 
so it's just the former we need to worry about.

How do we help people know when they have conflicting overrides (possibly from 
different projects), help them sensibly merge or turn off Tika provided 
magic+definitions, and to alert them to when their copied + customised version 
probably wants updating following a tika upgrade giving a newer definition? Do 
a better job of those than we currently do now, then I'm very happy to +1 it :)

> Enable overriding of mimetype glob pattern definitions
> ------------------------------------------------------
>                 Key: TIKA-1466
>                 URL: https://issues.apache.org/jira/browse/TIKA-1466
>             Project: Tika
>          Issue Type: Improvement
>          Components: mime
>    Affects Versions: 1.6
>            Reporter: Luis Filipe Nassif
>            Priority: Major
> I think it is important to enable an overriding of the default 
> tika-mimetypes.xml glob pattern definitions within a custom-mimetypes.xml. 
> Currently, you can not define in a custom mimetype an already used glob 
> pattern, even if you redefine in custom-mimetypes.xml the first mimetype 
> using the conflicting glob pattern. The same extension can be used by 
> different applications in different domains or datasets. 

This message was sent by Atlassian JIRA

Reply via email to