[
https://issues.apache.org/jira/browse/TIKA-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168212#comment-14168212
]
Hudson commented on TIKA-1441:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #255 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/255/])
TIKA-1441 change log. (mattmann:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1631062)
* /tika/trunk/CHANGES.txt
- fix for TIKA-1441 ExternalParsers should allow dynamic keys to be specified
for Regexs (mattmann:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1631060)
*
/tika/trunk/tika-core/src/main/java/org/apache/tika/parser/external/ExternalParser.java
> ExternalParsers should allow dynamic keys to be specified for Regexs
> --------------------------------------------------------------------
>
> Key: TIKA-1441
> URL: https://issues.apache.org/jira/browse/TIKA-1441
> Project: Tika
> Issue Type: Bug
> Components: parser
> Environment: while working on TIKA-605 and memex
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.7
>
> Attachments: TIKA-1441.Mattman.100914.patch.txt
>
>
> While working on TIKA-605, I was trying to use ExternalParsers and I came
> across an interesting use case. What if there are so many met keys that
> specifying all of them by hand as individual regexs would be repetitive, and
> tedious. What if the met key itself could also be specified by a regex, e.g.,
> we just take the first group to be the key, and then the next group would be
> the actual value? I ran across this in parsing GDAL output and so a very
> simple improvement to the ExternalParsers Map<Pattern, String> map would be
> to allow it to take e.g., null or "" Strings and then take that to mean that
> the Pattern specifies *both* the key name *and* the key value.
> I've got a patch I'll upload all tests pass and I need this to get TIKA-605
> in and done.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
