Hi Everyone,
I just had a follow up on the issue that I had. I think I figured out at least one thing. I had diacritics set as true so it was only returning those results without diacritics so I was able to get the two queries to return the same results and go faster. However I ran into a new interesting problem. When I have this:
ft:mark(db:get($db)/sample/entry[descendant::text() contains text 'fas'])
I see "- apply full-text index for "fas" using language """ which takes 164.24 ms but when I have this:
ft:mark(db:get('edil-new')/sample/entry[descendant::text() contains text 'fas' using wildcards])
I do not see the full-text index being applied and it takes 2283.14 ms (much like I had seen before).
My expectation is that having a full text option would have not triggered such a large change in the performance. This is also true when I haven't actually used any wildcards in the query but just turned the option on. Would this be expected behaviour?
Thanks and all the best, Chris
On Sun, Oct 2, 2022 at 10:41 AM Chris Yocum cyocum@gmail.com wrote:
Hi,
I had a chance to come back to basex after a while when I needed to do some querying on my data set. I updated to 10.2 and loaded the files. This was all fine.
I then ran this query:
for $x in db:get($db)/sample/entry return ft:mark($x[descendant::text() contains text {'fas'} using wildcards])
which ran in 2528.78ms and return 170 results. This seemed rather slow so I started to work on it. I also ran this:
for $x in db:get($db)/sample/entry return $x[descendant::text() contains text {'fas'} using wildcards]
which ran in 57.77ms and returned 35 results. I was very suprised by this as I had expected it to run in the same time and return the same result set. I, then, started look deeper and it seems like ft:mark does more than add an XML tag around the matched token?
My question is this: does ft:mark do more than what I had expected it to do? Am I misunderstanding or miswriting this query?
Thank you and all the best, Chris