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

Hudson commented on TIKA-1578:
------------------------------

SUCCESS: Integrated in tika-trunk-jdk1.7 #568 (See 
[https://builds.apache.org/job/tika-trunk-jdk1.7/568/])
updated patch for TIKA-1578: outputs file type in metadata (aburgess: 
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1668952)
* 
/tika/trunk/tika-parsers/src/main/java/org/apache/tika/parser/hdf/HDFParser.java
* 
/tika/trunk/tika-parsers/src/test/java/org/apache/tika/parser/hdf/HDFParserTest.java


> Add file type description to HDFParsers
> ---------------------------------------
>
>                 Key: TIKA-1578
>                 URL: https://issues.apache.org/jira/browse/TIKA-1578
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.7
>            Reporter: Ann Burgess
>            Assignee: Ann Burgess
>              Labels: parser
>             Fix For: 1.8
>
>         Attachments: TIKA-1578.abburgess.150319.patch.txt
>
>
> [~gostep] explains that, there are three versions of NetCDF (classic format, 
> 64-bit offset, and netCDF-4/HDF5 format). When opening an existing netCDF 
> file, the netCDF library will transparently detect its format so we do not 
> need to adjust according to the detected format. 
> That said, it would be good to know the file type as each can have the .nc 
> extension.  This will add patch with add file type to the metadata. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to