Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hi, i've used Lucene API since RC version. There's problem since RC7 version in my site, LuceneAPI can not index nodes which have been indexed before, even if the index files deleted.
After I created a node and run cron to index the node, LuceneAPI shows no result, although the node is indexed.
Now, I'm using RC6 because it is the working one for me.
Comments
Comment #1
cpliakas CreditAttribution: cpliakas commentedHi gantenx.
I am afraid that I cannot replicate the issue. A couple of major difference between RC6 and 1.0 is that the sable version correctly honors node access, and it does not index nodes that are unpublished. Also, versions RC7 and later use a different analyzer and require an uprade of ZF components and an index rebuild. I just re-tested indexing on a 1.0 installation with and without node access rules, and it worked exactly as expected. I need some more information before I can help you out.
luceneapi_index_size('luceneapi_node')
somewhere in a custom function.Comment #2
cpliakas CreditAttribution: cpliakas commentedClosed manually after over 2 weeks of inactivity.
Comment #3
Dr Jay CreditAttribution: Dr Jay commentedI'm reopening this issue as I believe it may be related to a permissions problem. lucene works flawlessly until I run cron, after which it seems to somehow affect the permissions in the lucenapi_node folder/files (in the files directory). Running chmod on this directory once again allows the index to be accessed, though this is impractical as it requires to much human intervention.
Comment #4
cpliakas CreditAttribution: cpliakas commentedHi Jay.
If you are having permissions problems, check the settings in the Search Lucene API settings page. Towards the bottom, you will see options that allow you to set the UNIX permissions for the index. Try messing around with these to see if you get the desired results.
Thanks,
Chris
Comment #5
Dr Jay CreditAttribution: Dr Jay commentedHow embarassing! Thanks for that ...
Comment #6
cpliakas CreditAttribution: cpliakas commentedHaha. No problem! There are a lot of settings scattered over a lot of pages for this one module, so it is understandable that a couple can fall through the cracks. If anything else, you helped a bunch of people know this setting actually exists.
Thanks for posting,
Chris