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

Nick Burch commented on TIKA-1952:
----------------------------------

In order to read the file's contents to get the metadata, Tika has to open the 
file. Many filesystems will consider that as an access and update their access 
times accordingly. 

Short of re-mounting your filesystem with the option `noatime` (or suitable 
equivalent), which would prevent other accesses of the file from updating it 
to, I'm not sure what else can be done here.

> Access Date is getting modified while capturing the MetaData information 
> using AutoDetectParser
> -----------------------------------------------------------------------------------------------
>
>                 Key: TIKA-1952
>                 URL: https://issues.apache.org/jira/browse/TIKA-1952
>             Project: Tika
>          Issue Type: Bug
>          Components: metadata
>    Affects Versions: 1.12
>         Environment: Windows
>            Reporter: RameshKalidindi
>              Labels: features
>             Fix For: 1.13
>
>
> I have been developing a project where in am capturing the MetaData 
> information( like File name, Author, File Extension, Last Modified Date and 
> Access Date) of each file in a folder using AutoDetectParser of Tika, I am 
> able to get meta data information for all files in a given folder, but my 
> issue is that the value of Access Date (MetaData attibute) is getting changed 
> with current date and Time as the program is accessing the each and every 
> file while extracting the MetaData information.
> My Issue : is there anyway that i can get the last Access Date of the file? 
> or can we stop changing Access Date value that was happening due to 
> AutoDetectParser of Tika API. Please help me in this regard. 
> Note: This Access Date information is very important  for my project, based 
> on this we need to build reports.
> Thanks,



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

Reply via email to