|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (TIKA-69) ParseUtils methods need to support MetadataParseUtils methods need to support Metadata
------------------------------------------- Key: TIKA-69 URL: https://issues.apache.org/jira/browse/TIKA-69 Project: Tika Issue Type: Improvement Components: general Affects Versions: 0.1-incubator Reporter: Keith R. Bennett Fix For: 0.1-incubator ParseUtils methods need to support Metadata and in general need updating and streamlining to reflect recent changes in the source code base. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Updated: (TIKA-69) ParseUtils methods need to support Metadata[ https://issues.apache.org/jira/browse/TIKA-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith R. Bennett updated TIKA-69: --------------------------------- Attachment: tika69.patch Patch Notes: TikaConfig.getDefaultConfig(): * Now throws TikaException wrapping IOException and JDOMException. * Now uses TikaConfig.class instead of Utils.class to load the resource. ParseUtils: * methods taking a TikaConfig can take null; this results in use of the default configuration. * parse methods now all take a Metadata parameter. To simplify use for those who only want full text, it can be null and a dummy instance will be created. Therefore, the methods names have changed from getStringContent() to parse(). * the parse() methods that allow the user to specify the MIME type have been removed. This functionality can be achieved by calling getParser() with the MIME type and config, and using parse(InputStream, Metadata, Parser). * Parse methods are provided for InputStream, File, and URL as inputs. * Required parameters are now checked, and passing null results in an exception with a message more descriptive than before. * Minor javadoc and indentation issues were fixed. * To keep the number of methods manageable, some convenience methods were removed, with the result that more parses need to be done in two steps: 1) get a parser, and 2) parse the stream. While this is an added step for the user, IMO it's a logical one, and simplifies the API considerably. * ParseUtils.getResourceName() needs attention in that the property name I used is arbitrary. It may need to be changed, and definitely should be made a constant. Or even made into a Metadata property with its own getter and setter. > ParseUtils methods need to support Metadata > ------------------------------------------- > > Key: TIKA-69 > URL: https://issues.apache.org/jira/browse/TIKA-69 > Project: Tika > Issue Type: Improvement > Components: general > Affects Versions: 0.1-incubator > Reporter: Keith R. Bennett > Fix For: 0.1-incubator > > Attachments: tika69.patch > > > ParseUtils methods need to support Metadata and in general need updating and streamlining to reflect recent changes in the source code base. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
|
|
[jira] Assigned: (TIKA-69) ParseUtils methods need to support Metadata[ https://issues.apache.org/jira/browse/TIKA-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned TIKA-69: ------------------------------------- Assignee: Chris A. Mattmann > ParseUtils methods need to support Metadata > ------------------------------------------- > > Key: TIKA-69 > URL: https://issues.apache.org/jira/browse/TIKA-69 > Project: Tika > Issue Type: Improvement > Components: general > Affects Versions: 0.1-incubating > Reporter: Keith R. Bennett > Assignee: Chris A. Mattmann > Fix For: 0.2-incubating > > Attachments: tika69.patch > > > ParseUtils methods need to support Metadata and in general need updating and streamlining to reflect recent changes in the source code base. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. |
| Free Forum Powered by Nabble | Forum Help |