jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Erwin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3287) Fulltext search breaking between 2.2 and 2.4.1
Date Wed, 25 Apr 2012 20:02:18 GMT

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

Charles Erwin commented on JCR-3287:
------------------------------------

Thank you for the information Razvan.  I am pretty sure that we are storing content with the
correct mimeType, so that should not be the issue. 

I will try changing the dependencies for Tika as you suggest and see if I get different results.
 Did you have any other configuration changes you had to make for the text extraction to work?
 I am concerned that aside from the Tika issue that there is new configuration needed from
2.2.x that has not been updated on the Wiki.
                
> Fulltext search breaking between 2.2 and 2.4.1
> ----------------------------------------------
>
>                 Key: JCR-3287
>                 URL: https://issues.apache.org/jira/browse/JCR-3287
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.4
>         Environment: 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12 18:47:41 PST 2012;
root:xnu-1699.24.23~1/RELEASE_X86_64 x86_64
> java version "1.6.0_29"
> Java(TM) SE Runtime Environment (build 1.6.0_29-b11-402-11D50b)
> Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02-402, mixed mode)
>            Reporter: Charles Erwin
>
> Upgraded Jackrabbit Dependencies from 2.2.0 to 2.4.1 and now cannot get Full Text search
to work.  I have created a Github project to show the repository.xml configuration and the
search code to prevent it being cluttered up here:  https://github.com/greymeister/jackrabbit-2.4-search-bug

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message