RT 4.0.5 in search don´t have content option

Hi to all.

I have 4.0.5 on centos and with mysql.

When i do a search i only have Content-Type, Subjet and Filename parameters
to search for data in the ticket.
In my old 3.6.5 installation y have Subjet, Filename Content-type and
CONTENT. Option that doesn´t exists on my RT 4.0.5
Could you hel me to get this option in the search options?

Thanks.
Kidest Regards.

Un saludo.
Juanjo Corral

Hi to all.

I have 4.0.5 on centos and with mysql.

When i do a search i only have Content-Type, Subjet and Filename parameters to search for data in the ticket.
In my old 3.6.5 installation y have Subjet, Filename Content-type and CONTENT. Option that doesn´t exists on my RT 4.0.5
Could you hel me to get this option in the search options?

Full content searches are disabled by default in the configuration file, because they’re not supported out of the box on all database types (at least, in an efficient manner). MySQL in particular, can’t do them efficiently because of the lack of full text indexes on InnoDB tables. In order to enable them on MySQL, you have to set up Sphinx and then enable that in the configuration. There are instructions in the docs/full_text_indexing.pod file that comes with the RT distribution.

Tim

The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.

OK, thanks.

Now works as the old RT.
But i think that i have to migrate RT 4.0.5 in mysql to postgre.

Anybody do it?

Thanks for your reply.

Yes, i read the full_text_indexing.pod
But, are the only option to search in content activate the indiexing
with a compatible database?

I don´t want to migrate to postgre, i think is very hard to my
knowledge.

You can do it with MySQL, if you enable sphinx (which is also fairly
difficult, but not as hard as a Postgres migration).

I think you can also switch it on without the indexing, which will
restore 3.x like behaviour, with very slow full content searches. I think
for this, you want something like this in your RT site config:

Set( %FullTextSearch,
Enable => 1,
Indexed => 0,
);

Regards,

Tim


The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.


Un saludo.
Juanjo Corral

Un saludo.
Juanjo Corral

I did it recently. There’s some good instructions on this older thread:

Specifically post #13On Thu, May 31, 2012 at 5:49 AM, Juanjo juanjillo@gmail.com wrote:

OK, thanks.

Now works as the old RT.
But i think that i have to migrate RT 4.0.5 in mysql to postgre.

Anybody do it?

2012/5/31 Tim Cutts tjrc@sanger.ac.uk

On 31 May 2012, at 10:06, Juanjo wrote:

Thanks for your reply.

Yes, i read the full_text_indexing.pod
But, are the only option to search in content activate the indiexing
with a compatible database?

I don´t want to migrate to postgre, i think is very hard to my
knowledge.

You can do it with MySQL, if you enable sphinx (which is also fairly
difficult, but not as hard as a Postgres migration).

I think you can also switch it on without the indexing, which will
restore 3.x like behaviour, with very slow full content searches. I think
for this, you want something like this in your RT site config:

Set( %FullTextSearch,
Enable => 1,
Indexed => 0,
);

Regards,

Tim


The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.


Un saludo.
Juanjo Corral


Un saludo.
Juanjo Corral

Thanks Nathan. I will check your migration process, and i will try it.

Regards.2012/5/31 Nathan Baker bakern@gmail.com

I did it recently. There’s some good instructions on this older thread:

Carbon60: Cloud Consulting - Services and Solutions

Specifically post #13

On Thu, May 31, 2012 at 5:49 AM, Juanjo juanjillo@gmail.com wrote:

OK, thanks.

Now works as the old RT.
But i think that i have to migrate RT 4.0.5 in mysql to postgre.

Anybody do it?

2012/5/31 Tim Cutts tjrc@sanger.ac.uk

On 31 May 2012, at 10:06, Juanjo wrote:

Thanks for your reply.

Yes, i read the full_text_indexing.pod
But, are the only option to search in content activate the indiexing
with a compatible database?

I don´t want to migrate to postgre, i think is very hard to my
knowledge.

You can do it with MySQL, if you enable sphinx (which is also fairly
difficult, but not as hard as a Postgres migration).

I think you can also switch it on without the indexing, which will
restore 3.x like behaviour, with very slow full content searches. I think
for this, you want something like this in your RT site config:

Set( %FullTextSearch,
Enable => 1,
Indexed => 0,
);

Regards,

Tim


The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.


Un saludo.
Juanjo Corral


Un saludo.
Juanjo Corral

Un saludo.
Juanjo Corral