eXistdb 3 index usage problem

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

eXistdb 3 index usage problem

Zoltán Szilágyi

Hi all!

 

I have an index usage problem with final eXistdb 3.

 

The collection „/db/apps/sls/data/en” contains a „collection.xconf” file:

 

<collection xmlns="http://exist-db.org/collection-config/1.0">

    <index xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sls="http://sls.internal.epo.org/legal-book">

        <fulltext default="none" attributes="false"/>

        <lucene>

            <analyzer class="org.apache.lucene.analysis.standard.StandardAnalyzer"/>

            <analyzer id="ws" class="org.apache.lucene.analysis.WhitespaceAnalyzer"/>

            <text qname="sls:text"/>

        </lucene>

        <range>

            <create qname="@uuid" type="xs:string"/>

            <create qname="@refuuid" type="xs:string"/>

            <create qname="@layerLevel" type="xs:integer"/>

            <create qname="@user" type="xs:string"/>

            <create qname="@version" type="xs:string"/>

            <create qname="@tid" type="xs:string"/>

        </range>

    </index>

</collection>

 

This config used by the system by both on 2.4 and 3.0. The Profiler’s “Indexes” section shows the usage of the indexes:

“Index Configuration for /db/apps/sls/data/en

 

Open .xconf file in eXide

Item Indexed    Index    Show Index Keys By

-              Legacy Fulltext (disabled)           -

sls:text                 Lucene QName (default analyzer)          QName, Node

@uuid New Range QName (xs:string)                 Node

@refuuid            New Range QName (xs:string)                 Node

@layerLevel      New Range QName (xs:integer)              Node

@user New Range QName (xs:string)                 Node

@version            New Range QName (xs:string)                 Node

@tid      New Range QName (xs:string)                 Node”

 

When I access the data from an XQL, the 2.4 version use these indexes, but the 3.0 is not.

 

3.0 in the Profiler’s “Index Usage” tab:

 

Source Index    Optimization     Calls       Timing

/db/apps/sls/get_section_by_uuid.xql [79:62]                range    No index             23           2.168

 

But in 2.4:

                                                                                                    

get_section_by_uuid.xql [79:62]             range    Full         99           0.046

 

Any idea how to force the db to use the indexes?

 

(I have reindexed the data many times, and all the data copied to the 3.0 version with the webdav interface)

 

Regards,

Zoltán

 


------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|

Re: eXistdb 3 index usage problem

dumont
The class name of the Standard Analyzer was changed:
try org.apache.lucene.analysis.core.StandardAnalyzer instead of
org.apache.lucene.analysis.standard.StandardAnalyzer!

Best regards,
Stefan

Am 08.03.2017 um 14:47 schrieb Zoltán Szilágyi:

> Hi all!
>
>  
>
> I have an index usage problem with final eXistdb 3.
>
>  
>
> The collection „/db/apps/sls/data/en” contains a „collection.xconf” file:
>
>  
>
> <collection xmlns="http://exist-db.org/collection-config/1.0">
>
>     <index xmlns:xs="http://www.w3.org/2001/XMLSchema"
> xmlns:sls="http://sls.internal.epo.org/legal-book">
>
>         <fulltext default="none" attributes="false"/>
>
>         <lucene>
>
>             <analyzer
> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/>
>
>             <analyzer id="ws"
> class="org.apache.lucene.analysis.WhitespaceAnalyzer"/>
>
>             <text qname="sls:text"/>
>
>         </lucene>
>
>         <range>
>
>             <create qname="@uuid" type="xs:string"/>
>
>             <create qname="@refuuid" type="xs:string"/>
>
>             <create qname="@layerLevel" type="xs:integer"/>
>
>             <create qname="@user" type="xs:string"/>
>
>             <create qname="@version" type="xs:string"/>
>
>             <create qname="@tid" type="xs:string"/>
>
>         </range>
>
>     </index>
>
> </collection>
>
>  
>
> This config used by the system by both on 2.4 and 3.0. The Profiler’s
> “Indexes” section shows the usage of the indexes:
>
> “Index Configuration for /db/apps/sls/data/en
>
>  
>
> Open .xconf file in eXide
>
> Item Indexed    Index    Show Index Keys By
>
> -              Legacy Fulltext (disabled)           -
>
> sls:text                 Lucene QName (default analyzer)          QName,
> Node
>
> @uuid New Range QName (xs:string)                 Node
>
> @refuuid            New Range QName (xs:string)                 Node
>
> @layerLevel      New Range QName (xs:integer)              Node
>
> @user New Range QName (xs:string)                 Node
>
> @version            New Range QName (xs:string)                 Node
>
> @tid      New Range QName (xs:string)                 Node”
>
>  
>
> When I access the data from an XQL, the 2.4 version use these indexes,
> but the 3.0 is not.
>
>  
>
> 3.0 in the Profiler’s “Index Usage” tab:
>
>  
>
> Source Index    Optimization     Calls       Timing
>
> /db/apps/sls/get_section_by_uuid.xql [79:62]                range    No
> index             23           2.168
>
>  
>
> But in 2.4:
>
>                                                                                                    
>
>
> get_section_by_uuid.xql [79:62]             range    Full         99
>           0.046
>
>  
>
> Any idea how to force the db to use the indexes?
>
>  
>
> (I have reindexed the data many times, and all the data copied to the
> 3.0 version with the webdav interface)
>
>  
>
> Regards,
>
> Zoltán
>
>  
>
>
>
> ------------------------------------------------------------------------------
> Announcing the Oxford Dictionaries API! The API offers world-renowned
> dictionary content that is easy and intuitive to access. Sign up for an
> account today to start using our lexical data to power your apps and
> projects. Get started today and enter our developer competition.
> http://sdm.link/oxford
>
>
>
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

--
Berlin-Brandenburgische Akademie der Wissenschaften
TELOTA-Arbeitsgruppe
Jägerstraße 22/23
10117 Berlin

Tel.: 030 / 20370 -684
[hidden email]
www.bbaw.de/telota

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open