[ 
https://issues.apache.org/jira/browse/TIKA-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18129609#comment-18129609
 ] 

ASF GitHub Bot commented on TIKA-4987:
--------------------------------------

dschmidt commented on PR #3381:
URL: https://github.com/apache/tika/pull/3381#issuecomment-6315860073

   Nice :) 




> Read EXIF from BigTIFF through metadata-extractor 2.22.0
> --------------------------------------------------------
>
>                 Key: TIKA-4987
>                 URL: https://issues.apache.org/jira/browse/TIKA-4987
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Dominik Schmidt
>            Priority: Major
>
> metadata-extractor 2.22.0 (released 2026-10-20) reads BigTIFF containers 
> (drewnoakes/metadata-extractor#746): 8-byte offsets and counts, 20-byte IFD 
> entries, LONG8/IFD8. Tika is on 2.21.0 and works around the gap in two places.
> RawTiffParser skips EXIF for BigTIFF (magic 43) and only scans for XMP, so a 
> BigTIFF DNG (allowed since DNG 1.7) yields previews but no EXIF or DNG tags. 
> With the bump that branch goes away and BigTIFF takes the normal TiffParser 
> path.
> A plain BigTIFF .tif currently fails to parse at all: TiffMetadataReader 
> throws and ImageMetadataExtractor turns that into a TikaException. With 
> 2.22.0 TiffParser handles it without further changes.
> Detection is asymmetric: tika-mimetypes.xml lists the big-endian BigTIFF 
> magic (MM\0+) under image/tiff but not the little-endian one (II+\0), so 
> little-endian BigTIFF only resolves by extension. Add the missing magic.
> Scope:
> - bump metadata.extractor.version to 2.22.0
> - drop the BigTIFF branch in RawTiffParser.parse and the javadoc caveat
> - add the II+\0 magic to image/tiff, adjust TestMimeTypes
> - a BigTIFF fixture with EXIF tags (testDNG_bigtiff.dng carries none, only 
> the preview) and a test asserting them for both RawTiffParser and TiffParser



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to