It's all about the answers!

Ask a question

what is "Full Text Merge Limit" in Advanced properties of RTC?

Don Yang (7.6k21100135) | asked Jun 11 '12, 4:22 a.m.
retagged Jun 11 '12, 1:55 p.m. by Evan Hughes (2.4k1318)
RTC3013 used.

In RTC's advanced properties > workitem queries, there is "Full Text Merge Limit" and it says:
The number of full text results that will be merged with a structured query part. Technically, this is the size of an IN clause. Setting this parameter to a high value may have a severe impact on performance.

"The number of full text results that will be merged with a structured query part" does not make much sense. What does that mean here?

The background why we notice this setting is that we have a problem in query a Chinese word and it returns nothing, but adding one more character will return the expected results.
Then if we adjust the "Full Text Merge Limit", and the same problematic query against a full text(without adding extra characters) will now work.
What does this limit mean and how does it work in full text query? Thanks a lot.

One answer

permanent link
Arne Bister (2.6k12832) | answered Jun 11 '12, 3:47 p.m.
I cannot give you a complete answer but maybe contribute.
As described here in the section Query Services, JTS supports both structured queries and full text queries. Full text search in Jazz is done via Lucene. Structured queries are done via SPARQL. This technote describes how RTC interacts with Lucene in more detail for quick search. I imagine that in a regular work item query when you use the "full text" attribute, the result of the Lucene search result is then filtered by / merged with the structured query. This might explain "the number of full text results merged with a structured query part".

Do you get the same results when executing a query against work items using just "full text" attribute and when using QuickSearch in RTC (just entering full text in the quick search text field in e.g. Web)?

- Arne

Your answer

Register or to post your answer.