[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nepomuk
Subject:    Re: [Nepomuk] [RFC] Better Full text search
From:       phreedom () yandex ! ru
Date:       2013-05-04 14:09:59
Message-ID: 1814654.60iBfe618G () nixos
[Download RAW message or body]

On Суббота 04 мая 2013 18:49:05 Vishesh Handa wrote:
> Even when you're doing a simple search for one word
> it is still something like this -
> 
> select distinct ?r where {
>     { ?r ?p ?o .
>       bif:contains(?o, "word") .
>     }
>     UNION {
>         ?r ?p ?o1
>         ?o1 ?p2 ?o .
>         bif:contains(?o, "word") .
>    }
> }
> 
> which is again kinda slow cause we aren't using any of the indexes of the
> statements.
> 
> I was thinking of moving all the plain text related to a file into the
> nie:plainTextContent of the resource. So in the case of music we would have
> -
> 
> <res> nie:plainTextContent "title artist album whatevereElse" .
> 
> for the case of files, we would append the file name, and any other plain
> text that we want searched just in the nie:plainTextConent. So a search for
> any combination of text will just have to search through the plain text
> content.
> 
> Opinions?
> 
> We can easily do this for the 4.11 release cause we already need everyone
> to re-index everything cause of the migration.

Have you asked Virtuoso devs?
Unless someone tried using plainTextContent as primary storage, it shouldn't 
be a problem. But if structured data goes out of the window, we could as well 
use clucene to get good performance :(
_______________________________________________
Nepomuk mailing list
Nepomuk@kde.org
https://mail.kde.org/mailman/listinfo/nepomuk

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic