Hi Davide I have looked into the issue some more and found that it is not actually related to the document.
The issue occurs when an property is indexed in a lucene index and is marked as ordered. Now if a property with a matching name is created with multiple values, the exception occurs. I have attached a simple test case to the jira issue that allows reproducing the issue. Would it be appropriate to ignore a property during indexing if it does not correspond to the expectation in the index definition? Regards Julian On Tue, Jun 23, 2015 at 11:04 AM, Davide Giannella <[email protected]> wrote: > On 22/06/2015 18:06, Julian Sedding wrote: >> Hi Chetan >> >> I created OAK-3020 and attached the full stack trace there. The root >> cause is an IllegalArgumentException in Lucene, which in turn causes a >> CommitFailedException (OakLucene003): >> >> Caused by: java.lang.IllegalArgumentException: DocValuesField >> ":dvjcr:content/metadata/prism:expirationDate" appears more than once >> in this document (only one value is allowed per field) >> at >> org.apache.lucene.index.NumericDocValuesWriter.addValue(NumericDocValuesWriter.java:54) >> at >> org.apache.lucene.index.DocValuesProcessor.addNumericField(DocValuesProcessor.java:153) >> > Thanks Julian, > > would it be possible to have the actual document that cause the error? > It will be extremely helpful if we could reproduce it on a pure oak side > with a unit test. > > Cheers > Davide > >
