You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Charles Erwin (JIRA)" <ji...@apache.org> on 2012/05/01 16:43:50 UTC
[jira] [Updated] (JCR-3287) Fulltext search breaking between 2.2
and 2.4.1
[ https://issues.apache.org/jira/browse/JCR-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Erwin updated JCR-3287:
-------------------------------
Attachment: tika_lucene_config.zip
I think I have finally gotten full text search to work, given Razvan's comments. I disabled the tika-parser and tika-core dependencies from Jackrabbit 2.4.1 and manually included version 1.1 of those dependencies. Now it seems that search works, but docx files do not seem to be indexed correctly. I will research that independently of this issue.
I am guessing that the wiki/documentation just needs to include that you must add an indexing configuration and a tika-config to enable full text search on content, which I don't believe it does currently.
> 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
> Attachments: tika_lucene_config.zip
>
>
> 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