[jira] [Commented] (TIKA-3981) Tika parser meets window system file
[ https://issues.apache.org/jira/browse/TIKA-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693140#comment-17693140 ] Nick Burch commented on TIKA-3981: -- Is this happening for all executables on your machine, or just some? And if is there any pattern on which executables are showing sensible dates and which are showing future ones? Does Windows Explorer show a more sensible date? Can anyone reproduce this with a small file from an open source project? (We have 8 test files in our test suite, all of which are coming back with sensible dates, so need some help to track down more details on this bug!) > Tika parser meets window system file > > > Key: TIKA-3981 > URL: https://issues.apache.org/jira/browse/TIKA-3981 > Project: Tika > Issue Type: Bug >Reporter: Tika User >Priority: Major > Attachments: ASK_Tika_Parser.docx > > > Hi All, > > I execute the command "java -jar tika-app-2.7.0.jar." and load the > windows system execute file where.exe. > You could find the file in your own windows system, > c:\Windows\systen32\where.exe. > Tika gets the dcterms:created, "2037-03-05T20:49:08Z" , but I get > confused the future time. > Could you help check why tika gets the special created date, please? > > Attachment is also my testing with several tika versions, for your > reference. > Thank you. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TIKA-3970) Certain OneNote documents produce duplicate text
[ https://issues.apache.org/jira/browse/TIKA-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693178#comment-17693178 ] Tim Allison commented on TIKA-3970: --- Thank you, Nick! > Certain OneNote documents produce duplicate text > > > Key: TIKA-3970 > URL: https://issues.apache.org/jira/browse/TIKA-3970 > Project: Tika > Issue Type: Bug > Components: app >Affects Versions: 2.7.0 >Reporter: David Avant >Priority: Minor > Attachments: Screenshot 2023-02-21 at 3.43.08 PM.png, > lyrics-crawlAllFileNodesFromRoot-false.txt, lyrics.docx, lyrics.one, > lyrics.txt > > > Extracting text from certain OneNote documents produces more text than is > actually in the document. In this case, the OneNote document was created > by opening a Word document and "printing" it to the OneNote. > To reproduce the issue, open the attached "lyrics.one" using the Tika App > version 2.7.0 and view the plain text. Look for the phrase "Sunday > Morning" and observe that there are 14 occurrences. However in the actual > displayed text, it occurs only once. > The original text in this document is only about 12K characters, but the > extracted text from tika is over 300K. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TIKA-3982) Tika Examples pages reference deprecated LanguageIdentifier class instead of LanguageDetector
James Daily created TIKA-3982: - Summary: Tika Examples pages reference deprecated LanguageIdentifier class instead of LanguageDetector Key: TIKA-3982 URL: https://issues.apache.org/jira/browse/TIKA-3982 Project: Tika Issue Type: Bug Components: documentation Affects Versions: 2.7.0, 2.6.0 Reporter: James Daily The following Tika Examples pages reference the deprecated LanguageIdentifier class, including dead links: * [https://tika.apache.org/2.7.0/examples.html#Language_Identification] * [https://tika.apache.org/2.6.0/examples.html#Language_Identification] I'd suggest that these sections should be rewritten to cover the LanguageDetector class instead: [https://tika.apache.org/2.7.0/api/org/apache/tika/language/detect/LanguageDetector.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] davidxie-glean opened a new pull request, #985: [TIKA-3979] OneNoteParser - Improve performance for deserialization
davidxie-glean opened a new pull request, #985: URL: https://github.com/apache/tika/pull/985 Context --- CPU profiling of OneNoteParser shows that a lot of cpu time is spent creating the BitSet in `BitReader`. Reusing the byte array reference will prevent the need to make a copy of the byte array. Template --- 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-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] 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-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (TIKA-3979) OneNoteParser - Improve performance for deserialization
[ https://issues.apache.org/jira/browse/TIKA-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693332#comment-17693332 ] ASF GitHub Bot commented on TIKA-3979: -- davidxie-glean opened a new pull request, #985: URL: https://github.com/apache/tika/pull/985 Context --- CPU profiling of OneNoteParser shows that a lot of cpu time is spent creating the BitSet in `BitReader`. Reusing the byte array reference will prevent the need to make a copy of the byte array. Template --- 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-`) - is referenced in the title of the pull request - and placed in front of your commit messages surrounded by square brackets (`[TIKA-] 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! > OneNoteParser - Improve performance for deserialization > --- > > Key: TIKA-3979 > URL: https://issues.apache.org/jira/browse/TIKA-3979 > Project: Tika > Issue Type: Improvement > Components: parser >Affects Versions: 2.7.0 >Reporter: David Xie >Priority: Major > Attachments: image-2023-02-20-14-42-10-590.png > > > We noticed some performance issues specific to parsing OneNote files. Our cpu > profiler reports that the parser spends a lot of time on deserializing byte > arrays (image included below) > !image-2023-02-20-14-42-10-590.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [tika] tballison commented on pull request #985: [TIKA-3979] OneNoteParser - Improve performance for deserialization
tballison commented on PR #985: URL: https://github.com/apache/tika/pull/985#issuecomment-1444388841 Do you have any performance comparisons before/after? Thank you for this PR! -- 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-unsubscr...@tika.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (TIKA-3979) OneNoteParser - Improve performance for deserialization
[ https://issues.apache.org/jira/browse/TIKA-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693338#comment-17693338 ] ASF GitHub Bot commented on TIKA-3979: -- tballison commented on PR #985: URL: https://github.com/apache/tika/pull/985#issuecomment-1444388841 Do you have any performance comparisons before/after? Thank you for this PR! > OneNoteParser - Improve performance for deserialization > --- > > Key: TIKA-3979 > URL: https://issues.apache.org/jira/browse/TIKA-3979 > Project: Tika > Issue Type: Improvement > Components: parser >Affects Versions: 2.7.0 >Reporter: David Xie >Priority: Major > Attachments: image-2023-02-20-14-42-10-590.png > > > We noticed some performance issues specific to parsing OneNote files. Our cpu > profiler reports that the parser spends a lot of time on deserializing byte > arrays (image included below) > !image-2023-02-20-14-42-10-590.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
