Fulltext search in RT4

RT Users
1

Hi all,

Have upgraded to RT4 (from 3.8.4) and I have to say it went really well, so
much so that the “beta” became the “final” in one hit. Well done all at Best
Practical.

Only thing that does not seem to work any more is searching for tickets by
looking for words in the body of messages. In 3.8 we used “fulltext:word” to
search. This returns nothing in RT4. Is there anything equivalent, or have I
missed something?

Also, any idea when documentation on the new lifecycle features will appear?
This was the big draw for us with RT4.

Thanks,
Gary

2

Hi all,
Have upgraded to RT4 (from 3.8.4) and I have to say it went really well,
so much so that the “beta” became the “final” in one hit. Well done all at
Best Practical.
Only thing that does not seem to work any more is searching for tickets by
looking for words in the body of messages. In 3.8 we used “fulltext:word”
to search. This returns nothing in RT4. Is there anything equivalent, or
have I missed something?
Also, any idea when documentation on the new lifecycle features will
appear? This was the big draw for us with RT4.

All your questions are answered in the RT_Config.pm file :wink:

For FTS:

=item C<%FullTextSearch>

Full text search (FTS) without indexes is a very slow operation and by
default is disabled at all. To enable FTS set key ‘Enable’ to 1.

Setup of indexes and filling them with data requires additional steps
that vary from DB to DB. Use F<sbin/rt-setup-fulltext-index> helper
for quick start. This script creates required structures in the DB and
gives some ideas on next steps. Use F<sbin/rt-fulltext-indexer> to
keep the index in sync.

=cut

[…]

For LifeCycle:

=head1 Lifecycles

=head2 Lifecycle definitions

Each lifecycle is a list of possible statuses split into three logic
sets: B, B and B. Each status in a
lifecycle must be unique. (Statuses may not be repeated across sets.)
Each set may have any number of statuses.

[…]

3

Only thing that does not seem to work any more is searching for
tickets by looking for words in the body of messages. In 3.8 we used
“fulltext:word” to search. This returns nothing in RT4. Is there
anything equivalent, or have I missed something?

As Emmanuel notes, you need to:

    Set( %FullTextSearch,
      Enable => 1
    );

…to enable the 3.8 unindexed FTS functionality. This became disabled
by default in 4.0 because of the performance implications of the search
on most large deployments. If you want indexed FTS, we suggest you wait
for 4.0.1, as it contains a number of critical bugfixes and
documentation updates in this codepath.

  • Alex
4

Alex, Emmanuel:

Thanks for the heads up. Is working again, will wait for 4.0.1 for the
indexed version (we’ve about 2000 tickets so it isn’t too painful right now
without it).

Regards,
GaryOn 23 May 2011 15:11, Alex Vandiver alexmv@bestpractical.com wrote:

On Mon, 2011-05-23 at 14:45 +0100, Gary Holmes wrote:

Only thing that does not seem to work any more is searching for
tickets by looking for words in the body of messages. In 3.8 we used
“fulltext:word” to search. This returns nothing in RT4. Is there
anything equivalent, or have I missed something?

As Emmanuel notes, you need to:

   Set( %FullTextSearch,
     Enable => 1
   );

…to enable the 3.8 unindexed FTS functionality. This became disabled
by default in 4.0 because of the performance implications of the search
on most large deployments. If you want indexed FTS, we suggest you wait
for 4.0.1, as it contains a number of critical bugfixes and
documentation updates in this codepath.

  • Alex