You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "yoavhhh (via GitHub)" <gi...@apache.org> on 2025/06/17 06:57:48 UTC

[PR] Feature/ntfs [tika]

yoavhhh opened a new pull request, #2253:
URL: https://github.com/apache/tika/pull/2253

   <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
     regarding copyright ownership.  The ASF licenses this file
     to you under the Apache License, Version 2.0 (the
     "License"); you may not use this file except in compliance
     with the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
     Unless required by applicable law or agreed to in writing,
     software distributed under the License is distributed on an
     "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
   -->
   
   Thanks for your contribution to [Apache Tika](https://tika.apache.org/)! Your help is appreciated!
   
   Before opening the pull request, please verify that
   * there is an open issue on the [Tika issue tracker](https://issues.apache.org/jira/projects/TIKA) which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes.
   * the issue ID (`TIKA-XXXX`)
     - is referenced in the title of the pull request
     - and placed in front of your commit messages surrounded by square brackets (`[TIKA-XXXX] Issue or pull request title`)
   * commits are squashed into a single one (or few commits for larger changes)
   * Tika is successfully built and unit tests pass by running `mvn clean test`
   * there should be no conflicts when merging the pull request branch into the *recent* `main` branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled `main` branch
   * if you add new module that downstream users will depend upon add it to relevant group in `tika-bom/pom.xml`.
   
   We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the [Tika mailing list](http://tika.apache.org/mail-lists.html). Thanks!
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@tika.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Feature/ntfs [tika]

Posted by "tballison (via GitHub)" <gi...@apache.org>.
tballison commented on PR #2253:
URL: https://github.com/apache/tika/pull/2253#issuecomment-3052961846

   The above is all high-level. At a lower level, I'm concerned about platform dependent binary code in Tika. We definitely have it it tika-parsers-extended (sqlite3). Another way to handle that is to require users to install the binaries on their system (or in Docker) first, as we do with tesseract (and why we opted not to integrate with `tess4`j).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@tika.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Feature/ntfs [tika]

Posted by "tballison (via GitHub)" <gi...@apache.org>.
tballison commented on PR #2253:
URL: https://github.com/apache/tika/pull/2253#issuecomment-3052951215

   Thank you for opening this. I'm not sure that it fits within the current design goals of Tika, but there may be ways forward.
   
   I deeply respect sleuthkit and would be interested in pursuing whatever we can to work together.
   
   I also may misunderstand your use case and this PR. Please bear with me.
   
   My major concern is that Tika is intended to process individual files one at a time. Even with a single large docx or PDF, Tika can go out of memory. 
   
   If we treat an entire filesystem as a file (obv with embedded files), I think we're aiming for serious problems.
   
   There are two ways I could see some kind of integration point with Tika.
   
   1) Create a pipesiterator and fetchers so that Tika could iterate through ntfs or any other format handled by sleuthkit.
   
   2) Create standardized "Unpackaging" api in Tika that would use sleuthkit commandline(s?) to extract binary files for further processing. There are lots of use cases I've seen where "unpackaging" is required rather than the usual parsing. This is typically a pre-parsing step required to unpackage a bundle of files that someone packages for transfer. For example, this can be useful with zips, PSTs, mbox etc.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@tika.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org