Re: [Exist-open] Are more elaborate xpath expressions allowed in Lucene's index config <text match='...'/>.

[Stanislav <st...@gm...>]

I've become an expert in overlooking the relevant parts of the
documentation.

Thanks again, Joe

On Tue, Aug 14, 2018 at 4:54 PM, Joe Wicentowski <jo...@gm...> wrote:

> Hi Stanislav,
>
> Please see https://exist-db.org/exist/apps/doc/lucene#D3.19.58:
>
> > Please note that the argument to match is a simple path pattern, not a
> full XPath expression. It only allows / and // to denote child or
> descendant steps, plus the wildcard * to match an arbitrary element.
>
> Joe
>
>
> On Tue, Aug 14, 2018 at 9:18 AM Stanislav <st...@gm...> wrote:
>
>> Hi guys,
>> I needed a finer control over which title nodes get selected for
>> indexing, so I opened collection.xconf and replaced:
>>
>>            <text match="//tei:teiHeader/tei:fileDesc//tei:title"/>
>>
>> With the more elaborate:
>>
>>            <text match="//tei:teiHeader/tei:
>> fileDesc//tei:title[@xml:lang='Sa-Ltn']"/>
>>
>> And this resulted in:
>>
>> *WARN  (LuceneConfig.java [parseConfig]:311) - Invalid lucene
>> configuration element: Lucene module: invalid qname in configuration:
>> Illegal QName: 'tei:title[@xml:lang='Sa-Ltn']' not a valid local name. *
>>
>> eXist version is 3.4.1
>>
>>
>> What have gone wrong?
>>
>>
>> Kindly,
>> /St.
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______
>> _________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>>
>