Manual for Full-text search

RT Users
1

Hi.

I am currently evaluating RT4 on our RT test-server. I noticed that improved fulltext-search is one of the things mentioned in the release notes, and I can also see some settings regarding FullTextSearch in RT_Config.pm.
Is there any documentation on how to setup and use this feature? It would be very useful to us.
I tried setting “Enabled” and “Indexed” to 1 in RT_SiteConfig.pm and ran rt-fulltext-indexer as suggested in the configuration file, but I got an error message.
The configuration comments tells me to run rt-fulltext-indexer for instructions on setup, but this command tells me to read the documentation for the FullTextSearch setting.
We are using MySQL 5.0

Best Regards,
Johan Sjöberg

2

I am currently evaluating RT4 on our RT test-server. I noticed that
improved fulltext-search is one of the things mentioned in the release
notes, and I can also see some settings regarding FullTextSearch in
RT_Config.pm.

Is there any documentation on how to setup and use this feature? It
would be very useful to us.

We will be shipping much-improved documentation on the full-text
searching in RT 4.0.1. There is also a sizable bug which prevents it
from working on MySQL in RT 4.0.0, which we hope to resolve quickly
enough to also land in RT 4.0.1.

We are using MySQL 5.0

The updated documentation will also make clear that as MySQL does not
include built-in full-text search capabilities, we rely on the external
Sphinx FTS tool. Unfortunately, the SphinxSE engine which allows us to
make FTS queries from within MySQL requires recompiling MySQL. You can
find complete instructions on how to do this at
http://sphinxsearch.com/docs/2.0.1/sphinxse-installing.html

  • Alex
3

Hi.

Thank you for your reply. We will probably start looking at migrating from MySQL to Postgres, since it seems like that is much better way to go. Looking forward to the full-text search documentation.

/JohanFrom: Alex Vandiver [mailto:alexmv@bestpractical.com]
Sent: den 3 maj 2011 17:53
To: Johan Sjöberg
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Manual for Full-text search

I am currently evaluating RT4 on our RT test-server. I noticed that
improved fulltext-search is one of the things mentioned in the release
notes, and I can also see some settings regarding FullTextSearch in
RT_Config.pm.

Is there any documentation on how to setup and use this feature? It
would be very useful to us.

We will be shipping much-improved documentation on the full-text searching in RT 4.0.1. There is also a sizable bug which prevents it from working on MySQL in RT 4.0.0, which we hope to resolve quickly enough to also land in RT 4.0.1.

We are using MySQL 5.0

The updated documentation will also make clear that as MySQL does not include built-in full-text search capabilities, we rely on the external Sphinx FTS tool. Unfortunately, the SphinxSE engine which allows us to make FTS queries from within MySQL requires recompiling MySQL. You can find complete instructions on how to do this at Sphinx | Open Source Search Server

  • Alex
4

I’ve been debating the same thing…would the procedure shown on the MySQLToPg page on the Wiki still be valid for 4.0.x?

PatrickFrom: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Johan Sjöberg
Sent: Wednesday, May 04, 2011 12:38 AM
To: Alex Vandiver
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Manual for Full-text search

Hi.

Thank you for your reply. We will probably start looking at migrating from MySQL to Postgres, since it seems like that is much better way to go. Looking forward to the full-text search documentation.

/Johan

From: Alex Vandiver [mailto:alexmv@bestpractical.com]
Sent: den 3 maj 2011 17:53
To: Johan Sjöberg
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Manual for Full-text search

I am currently evaluating RT4 on our RT test-server. I noticed that
improved fulltext-search is one of the things mentioned in the release
notes, and I can also see some settings regarding FullTextSearch in
RT_Config.pm.

Is there any documentation on how to setup and use this feature? It
would be very useful to us.

We will be shipping much-improved documentation on the full-text searching in RT 4.0.1. There is also a sizable bug which prevents it from working on MySQL in RT 4.0.0, which we hope to resolve quickly enough to also land in RT 4.0.1.

We are using MySQL 5.0

The updated documentation will also make clear that as MySQL does not include built-in full-text search capabilities, we rely on the external Sphinx FTS tool. Unfortunately, the SphinxSE engine which allows us to make FTS queries from within MySQL requires recompiling MySQL. You can find complete instructions on how to do this at Sphinx | Open Source Search Server

  • Alex
5

I wanted to ask the same question, so I know if I should do the migration before or after upgrading to RT 4.
There are a lot of different methods on that page, and the simplest ones seem to be just dumping the MySQL database and importing it into Postgres. Is there any general consensus regarding which method is “best”, with the biggest chance of getting non-corrupted attachments etc.?

/JohanFrom: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Patrick Fish
Sent: den 4 maj 2011 09:51
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Manual for Full-text search

I’ve been debating the same thing…would the procedure shown on the MySQLToPg page on the Wiki still be valid for 4.0.x?

Patrick

From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Johan Sjöberg
Sent: Wednesday, May 04, 2011 12:38 AM
To: Alex Vandiver
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Manual for Full-text search

Hi.

Thank you for your reply. We will probably start looking at migrating from MySQL to Postgres, since it seems like that is much better way to go. Looking forward to the full-text search documentation.

/Johan

From: Alex Vandiver [mailto:alexmv@bestpractical.com]
Sent: den 3 maj 2011 17:53
To: Johan Sjöberg
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Manual for Full-text search

I am currently evaluating RT4 on our RT test-server. I noticed that
improved fulltext-search is one of the things mentioned in the release
notes, and I can also see some settings regarding FullTextSearch in
RT_Config.pm.

Is there any documentation on how to setup and use this feature? It
would be very useful to us.

We will be shipping much-improved documentation on the full-text searching in RT 4.0.1. There is also a sizable bug which prevents it from working on MySQL in RT 4.0.0, which we hope to resolve quickly enough to also land in RT 4.0.1.

We are using MySQL 5.0

The updated documentation will also make clear that as MySQL does not include built-in full-text search capabilities, we rely on the external Sphinx FTS tool. Unfortunately, the SphinxSE engine which allows us to make FTS queries from within MySQL requires recompiling MySQL. You can find complete instructions on how to do this at Sphinx | Open Source Search Server

  • Alex
6

I wanted to ask the same question, so I know if I should do the
migration before or after upgrading to RT 4.
There are a lot of different methods on that page, and the simplest
ones seem to be just dumping the MySQL database and importing it into
Postgres. Is there any general consensus regarding which method is
“best”, with the biggest chance of getting non-corrupted attachments
etc.?

I had success to do this using a script that select in source DB and
insert in the destination DB (with a schema without datas).

Test: Oracle->Pg, MySQL → Pg

to my knowledge and experience, this is the best way to do this.

You can do this either:

  • 4.0 schema and datas → 4.0 schema
  • 3.8 schema and datas → 3.8 schema → run 3.8->4.0 upgrades scripts
7

Hi.

This sounds great. Is this script one of the methods at http://requesttracker.wikia.com/wiki/MySQLToPg ?

/Johan-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Emmanuel Lacour
Sent: den 4 maj 2011 10:48
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Manual for Full-text search

On Wed, May 04, 2011 at 08:01:58AM +0000, Johan Sjöberg wrote:

I wanted to ask the same question, so I know if I should do the
migration before or after upgrading to RT 4.
There are a lot of different methods on that page, and the simplest
ones seem to be just dumping the MySQL database and importing it into
Postgres. Is there any general consensus regarding which method is
“best”, with the biggest chance of getting non-corrupted attachments
etc.?

I had success to do this using a script that select in source DB and insert in the destination DB (with a schema without datas).

Test: Oracle->Pg, MySQL → Pg

to my knowledge and experience, this is the best way to do this.

You can do this either:

  • 4.0 schema and datas → 4.0 schema
  • 3.8 schema and datas → 3.8 schema → run 3.8->4.0 upgrades scripts
8

Hi.

This sounds great. Is this script one of the methods at http://requesttracker.wikia.com/wiki/MySQLToPg ?

I used a script inspired from AndreSachs one (slightly modified because
I had MySQL encoding changes to handle at the same time).

9

Hi,

we stored a saved search (Tickets) in “RT System’s saved searches” with
the intention to make the search visible to all users.

However,

normal users cannot even see saved searches. We do require users to load
them only and i gave the showsavedsearch and loadsavedsearch to every one.

It is not clear to me which access rights are needed to enable users to
see those system searches.

If this is not possible via “RT System’s saved searches”, how do I make
searches available to all users?
Otherwise every user has to save his/her own identical query which is
impractical and most of our users do not want to understand detailed
search semantics.

greetings,
l.r.

10

Lars:

we stored a saved search (Tickets) in “RT System’s saved searches” with
the intention to make the search visible to all users.

“RT System Saved Searches” are only available to SuperUsers, these are the searches you include as default in home page etc etc.
I think for your purposes and if its possible for you (pending number of users etc), I would suggest you create a new generic group and add all your users as members, then make your search as the new group search.

Over here I have few generic groups, AllStaff which include all our staff, AllCustomers include our customers groups
And 3rdParty which include suppliers groups etc, having these generic groups make my life much easier when applying permissions / dashboards and saved searches etc.

Regards;
Roy

11

Lars,

All searches are saved based on two things; personal and group membership.
Therefore, I give all the search rights (See, Create, Load, etc.) to all
privileged users, GLOBALLY. Reason, you can only see a search that either
you own or for a group you are a member of. Granting those search rights
globally does NOT give anyone the right to see some search they shouldn’t.
That is always dependant on the groups you are a member of. This saves a LOT
of time when setting up.maintaining rights.

As Raed explained, simply create a group with all the user you want to see a
set of searches and put the users in that group.

Kenn
LBNLOn Wed, May 4, 2011 at 3:43 AM, Lars Reimann l.reimann@metaways.de wrote:

Hi,

we stored a saved search (Tickets) in “RT System’s saved searches” with the
intention to make the search visible to all users.

However,

normal users cannot even see saved searches. We do require users to load
them only and i gave the showsavedsearch and loadsavedsearch to every one.

It is not clear to me which access rights are needed to enable users to see
those system searches.

If this is not possible via “RT System’s saved searches”, how do I make
searches available to all users?
Otherwise every user has to save his/her own identical query which is
impractical and most of our users do not want to understand detailed search
semantics.

greetings,
l.r.