[TIKA-3362] AsyncParser and EmitterResource have handler type hardcoded to text

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: tika-pipes
• Assignee: Tim Allison
• Reporter: Giovanni De Stefano
• Created: 20/Apr/21 08:12
• Updated: 21/Apr/21 12:09
• Resolved: 20/Apr/21 20:34

Description

All calls to  RecursiveMetadataResource.parseMetadata have text hardcoded as handlerTypeName while it should be dynamic.

AsyncParser worker threads process FetchEmitTuple objects asynchronously and by then the http headers are not available. An idea to make the handlerTypeName dynamic could be to add it to the configuration of the emitter (so directly into FetchEmitTuple).

EmitterResource on the other hand, could take the handlerTypeName as PathParam (just as it is in TikeResource).

What do you think about this reasoning? If this is acceptable I could work on PR