Hello Matteo, Thank you for your quick response.
>>You should be able to use query manager and to succesfully execute this query: >>SELECT * FROM nt:base I tried to run it against DMS successfully: 244 nodes returned in 734ms >>But when you restarted tomcat, did you see any exception after the indexes rebuilding phase? No I don't see any exception while booting tomcat. After some time playing with search (activating, making website references etc) I'm able to see .txt files and .doc (Word 97-03) files. Unfortunately no luck with PDF. As STK has majority of PDF documents in DMS that could be the reason why I couldn't search documents.Still I'm not sure when exactly Magnolia will index this or that document in DMS. Regards, Denis On Thu, Oct 15, 2009 at 10:31 AM, Matteo Pelucco <[email protected]>wrote: > > Denis Demichev ha scritto: > >> Hello, >> >> Matteo, thank you for clarification. >> Actually I'm asking because my Magnolia 4.1.1 doesn't return any search >> result even if I know that some specific term is inside that specific >> document (.txt file uploaded to DMS). >> > > This can happen probably because of index corruption. > Are you sure that indexes exist and that they are not broken? > > It looks like my DMS is not indexed at all. However, I can search through >> website pages, i.e. WEBSITE workspace is indexed, I guess. >> > > Ok, so it is only related to DMS. > Delete DMS indexes, removing with stopped tomcat all files inside > repo/magnolia/worskpaces/dms/index folder. > Leave other workspaces index folder as it, you will gain time. > Then restart tomcat and let luceen scanning your db to reconstruct indexes > (you can monitor file creation). > > You should be able to use query manager and to succesfully execute this > query: > > SELECT * FROM nt:base > > (select nt:base as result node type and DMS as workspace). > > I tried to delete index folder in default, DMS, website workspaces on both >> Author and Public instances but this didn't help. >> > > But when you restarted tomcat, did you see any exception after the indexes > rebuilding phase? > > Could STK affect this Magnolia's behavior or I just didn't configure it >> properly? >> > > STK is a templating module. > Nothing related so directly to JCR / Jackrabbit. > > HTH, > matteo > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
