Is the above supported? What I mean is, I have a field that is defined maxOccurs=unbounded, created index “standard and text”. When I run ino:explain ( my query ), it told me that ino:postprocessing=“TRUE”. How can I solve this? Frankly speaking, is this case logically correct (want to sort by a unbounded field)?
could you please post the schema and the query, and let us know which version of Tamino you are using?
Thanks in advance,
We are using Tamino XML Server 126.96.36.199, and please find our attached schema.
hklit.tsd (8.71 KB)
I loaded the schema that you provided (into a Tamino 188.8.131.52), made a simple instance with 3 occurrences of the “creator” element and loaded the instance 5 times.
Even a simple query like /article sortby(.) returns postprocessing=“TRUE”, so I would guess that the sortby is always handled by the postprocessor with my test data.
I have heard that some cases of sortby are actually handled faster by sorting the results in postprocessing, rather than trying to do it via indices.
I believe that the threshold for this behaviour is adjustable in Tamino 4.1.
[This message was edited by Trevor Ford on 01 Mar 2003 at 01:51.]
But our database contains around 100,000 documents, and is increasing, it’s nearly an infinite process (in fact, I’ve never seen it sorted, everytime I aborted) if I issue the query and sortby creator. It’s ok for other field that only allow one occurence, over 100,000 documents can be sorted around 3 seconds! Sort by creator is indeed our project requirement. So, any workaround?
Many thanks and best regards,
could you estimate how many occurrences of the creator element there are? For example, if there are 10 per document, you would have 1 million occurrences in Tamino.
Could you also please post the actual query that is causing problems?
(Is the problem the duration of the sortby query is too long?)
It’s strange that when I backed office this morning and ran the query again, it responsed almost as fast as sortby other field. The query that I mentioned to have problem is just as simple as “/article sortby (createor asc)”, I just wondering why the speed is back to good now. I havn’t restarted anything, non have changed any server properties…etc.
But, ino:explain(/article sortby (creator asc)) still gives me,
<ino:explanation ino:preselection=“FALSE” ino:postprocessing=“TRUE” />
Is it really still OK if postprocessing exists?
what was the exact timeline for the creation of the schema, loading content, and so on?
Is it possible that you defined an index after loading the documents, and that the index was still being created when you tried the first queries? (So now it is faster because the indexes have all been built…?)
Perhaps one of the Support guys has already had some experience with this kind of scenario with Tamino 184.108.40.206, and would like to comment?