I ran into a situation whereby for some reasons, the permissions were not right and the index turned out to be read-only for the application.

The problem is that I was able to call the indexing method and it returned as if it had done it's job, but then I was not able to find the records I indexed right after indexing them.

I traced the problem down to the index being read-only and resolving this solved my problem.

My question is:

Why is it not throwing an Exception? Is there a way to make it error when attempting to update an index that is read-only?


Etienne

Hi,

what do you mean with read-only? File permissions on the file system? What OS are you using? Have you checked the logs whether there was anything in them? Maybe you could give us some more information so that we cold try to reproduce the problem.

--Hardy

Yes, file system permission, on Linux. In this case, the index is on an NFS share that is mounted as RW but despite that, due to the owner on the NFS server, the files were read-only for the PC that has the share mounted RW.

In terms of solving the indexing problem in itself, that's fine, I fixed the permissions and it indexes correctly now.

The log did not have any errors and the application behaved as if it was indexing the records. Hence my question about whether there is a way to have it error.



Etienne

I think this is worth a Jira issue. I created this one - http://opensource.atlassian.com/project ... SEARCH-382

I haven't reproduced the problem yer though.

--Hardy

Ok thanks. I'll what I can do to get more specific to help reproduce it.


Etienne