[
https://issues.apache.org/jira/browse/OAK-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874246#comment-17874246
]
Julian Reschke commented on OAK-11025:
--------------------------------------
{noformat}
org.osgi.framework.BundleException: Unable to resolve
org.apache.jackrabbit.oak-lucene [48](R 48.0): missing requirement
[org.apache.jackrabbit.oak-lucene [48](R 48.0)] osgi.wiring.package;
(osgi.wiring.package=org.apache.jackrabbit.oak.commons.log) Unresolved
requirements: [[org.apache.jackrabbit.oak-lucene [48](R 48.0)]
osgi.wiring.package;
(osgi.wiring.package=org.apache.jackrabbit.oak.commons.log)]
at
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4398)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2308)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1566)
at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
> Silence more warnings for ordered properties
> --------------------------------------------
>
> Key: OAK-11025
> URL: https://issues.apache.org/jira/browse/OAK-11025
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: indexing
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Major
>
> With oak-run indexing, we have a lot of warnings, with stack trace each time,
> that look like this:
> {noformat}
> 07:23:34.803 [main] WARN o.a.j.o.p.i.l.LuceneDocumentMaker - [...] Ignoring
> ordered property. Could not convert property ... of type STRING to type DATE
> for path ...
> java.lang.IllegalArgumentException: Not a date string: 2025-05-06T15:27:36
> at
> org.apache.jackrabbit.oak.plugins.value.Conversions$Converter.toCalendar(Conversions.java:100)
> at
> org.apache.jackrabbit.oak.plugins.value.Conversions$Converter.toDate(Conversions.java:112)
> {noformat}
> We already have a mechanism to silence (only log once every 10 seconds)
> similar messages. So we can extend that mechanism to also cover the other
> cases.
> I checked and found 3 cases:
> * IllegalArgumentException: Not a date string
> * RuntimeException: Unable to parse the provided date field
> * NumberFormatException: For input string
> This issue is not about the performance impact, but to reduce the amount of
> unnecessary logging.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
