Hi,
we are migrating to Lucene 5 and we have a strange Exception that was
not happening in Lucene 4.
We are indexing in a pre-production environment and we move the index
in the production environment later; in the prod env the indices are
visible to our application with read-only rights. To clari
Hi,
this should be fixed in coming Lucene 5.3:
https://issues.apache.org/jira/browse/LUCENE-6542
The reason for this behavior is that we need to ensure that the directory
exists before we open it. For that it calls Files.createDirectories - which
requires write access. The fix only calls create
Hi Uwe,
thanks for your reply. Do you have any planned date for 5.3?
Cheers,
Nicola
On Wed, 2015-08-12 at 11:23 +0200, Uwe Schindler wrote:
> Hi,
>
> this should be fixed in coming Lucene 5.3:
> https://issues.apache.org/jira/browse/LUCENE-6542
>
> The reason for this behavior is that we n
Hi,
The release branch is already created (and we are only finishing some remaining
Apache Solr stuff - otherwise it's ready), but we have not yet started the
release process. So it should just be a couple of weeks.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetap
I've been digging on a similar issue and eventually found this Jira ticket.
https://issues.apache.org/jira/browse/LUCENE-2229
So far I haven't received any response in IRC or from the mailing list, and
the bug is resolved as "won't fix" even though there's a patch attached
that attempts to solve
