You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/01/21 04:34:34 UTC
[jira] Created: (TIKA-116) Streaming parser for OpenDocument files
Streaming parser for OpenDocument files
---------------------------------------
Key: TIKA-116
URL: https://issues.apache.org/jira/browse/TIKA-116
Project: Tika
Issue Type: Improvement
Components: parser
Reporter: Jukka Zitting
Assignee: Jukka Zitting
Fix For: 0.2-incubating
The current OpenOfficeParser first reads the entire meta.xml and content.xml files from the given OpenDocument zip into memory, then parses the in-memory files to DOM trees, merges the trees, and finally evaluates a number of XPath expressions against the resulting DOM tree to extract metadata and document content. All this requires quite a bit of memory and multiple passes over the document.
It would be better if the document could be streamed directly through zip and sax parsers without keeping a full copy of the document in memory or doing multiple passes over the document.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TIKA-116) Streaming parser for OpenDocument files
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated TIKA-116:
-------------------------------
Attachment: TIKA-116.patch
Attached a patch that implements streaming parsing for XML and OpenDocument files.
The patch contains an implementation of a simple SAX-based XPath subset (in o.a.t.sax.xpath) that is capable of processing all the XPath expressions in our current codebase.
> Streaming parser for OpenDocument files
> ---------------------------------------
>
> Key: TIKA-116
> URL: https://issues.apache.org/jira/browse/TIKA-116
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 0.2-incubating
>
> Attachments: TIKA-116.patch
>
>
> The current OpenOfficeParser first reads the entire meta.xml and content.xml files from the given OpenDocument zip into memory, then parses the in-memory files to DOM trees, merges the trees, and finally evaluates a number of XPath expressions against the resulting DOM tree to extract metadata and document content. All this requires quite a bit of memory and multiple passes over the document.
> It would be better if the document could be streamed directly through zip and sax parsers without keeping a full copy of the document in memory or doing multiple passes over the document.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TIKA-116) Streaming parser for OpenDocument files
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TIKA-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-116.
--------------------------------
Resolution: Fixed
Patch committed in revision 614000.
> Streaming parser for OpenDocument files
> ---------------------------------------
>
> Key: TIKA-116
> URL: https://issues.apache.org/jira/browse/TIKA-116
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 0.2-incubating
>
> Attachments: TIKA-116.patch
>
>
> The current OpenOfficeParser first reads the entire meta.xml and content.xml files from the given OpenDocument zip into memory, then parses the in-memory files to DOM trees, merges the trees, and finally evaluates a number of XPath expressions against the resulting DOM tree to extract metadata and document content. All this requires quite a bit of memory and multiple passes over the document.
> It would be better if the document could be streamed directly through zip and sax parsers without keeping a full copy of the document in memory or doing multiple passes over the document.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.