[
https://issues.apache.org/jira/browse/OAK-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason E Bailey resolved OAK-7150.
---------------------------------
Resolution: Cannot Reproduce
Upon further research, it was determined that the initial fault was incorrect,
it was not a missing index-details.txt that was creating the NPE. It was
index-details.txt files that were zerobyte long. Closing this as an invalid bug
report
> LuceneIndexProviderService fails to start due to extraneous folder
> ------------------------------------------------------------------
>
> Key: OAK-7150
> URL: https://issues.apache.org/jira/browse/OAK-7150
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Jason E Bailey
> Priority: Minor
>
> As part of our upgrade from oak 1.2.18 to 1.6.1 as part of our AEM 6.1 - 6.3
> migration. We encountered a problem where LuceneIndexProviderService would
> not start up due to a Null Pointer Exception. That was appearing in the
> IndexMeta(file) constructor for
> org.apache.jackrabbit.oak.plugins.index.lucene.directory.IndexMeta
> Our index directory had two sub folders with a long alpha numeric name
> i.e. 36620ebfe6a77b4cf94f9a12c2679d3dcb6f79231556559db2c933b1c28b5cc4
> One appears to be expected the other appears to be legacy. Neither of these
> directories contain a file called index-details.txt which the IndexMeta is
> expecting. The lack of this file in the legacy folder is what prevented the
> LuceneIndexProviderService from starting.
> This is a request to either gracefully handle the lack of this file or to
> have the error message generated by this constructor explicitly state that
> the specific file is missing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
