[ 
https://issues.apache.org/jira/browse/SOLR-7139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338426#comment-14338426
 ] 

Uwe Schindler edited comment on SOLR-7139 at 2/26/15 2:20 PM:
--------------------------------------------------------------

Patch. This also makes the fields final to ensure no accidental reuse & co.

I would like to get this also in 4.10.4, because Mattman set this fix version 
and set "critical".


was (Author: thetaphi):
Patch. This also makes the fields final to ensure no accidental reuse & co.

I would like to get this also in 4.10.4, because Mattman set this fix version 
and set blocker.

> SolrContentHandler for TIKA is broken by TikaOCR (caused by multiple 
> startDocument events)
> ------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7139
>                 URL: https://issues.apache.org/jira/browse/SOLR-7139
>             Project: Solr
>          Issue Type: Bug
>          Components: contrib - Solr Cell (Tika extraction)
>    Affects Versions: 4.10.3
>            Reporter: Chris A. Mattmann
>            Assignee: Uwe Schindler
>            Priority: Critical
>             Fix For: 4.10.4, 5.1, 5.0.1
>
>         Attachments: SOLR-7139.Mattmann.022115.patch.txt, SOLR-7139.patch
>
>
> While testing my large scale Tika/SolrCell indexing (great work on 
> /extraction guys, really really appreciate it) on my 40M image dataset, I was 
> pulling my frickin' hair out trying to figure out why the TesseractOCR 
> extracted content wasn't actually making it into the index. Well I figured it 
> out lol (many many System.out.printlns later) - it's the disabling of div 
> tags (=>ignored) in the default solrconfig.xml. This basically renders 
> TesseractOCR output in SolrCell useless since it is surrounded by a div tag.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to