Description
Fulltext conditions of the following form return the child node instead of the parent node:
contains([node1/text], 'hello')
This is because the filter doesn't contain the relative path (it doesn't contain the property name either, but that's not the problem here).
The problem here is not the Lucene index, but the filter API, so it can't be easily fixed. I think it makes sense to fix it as part of OAK-902.
Attachments
Issue Links
- is blocked by
-
OAK-902 Lucene fulltext query: "contains(*, 'x OR y')" not working
-
- Closed
-