[rt-users] Possible bug in fulltext search with mysql and sphinx

[Carlos Fuentes Bermejo]

Hi Rus,

I think that you should warn this issue and show the alternative when you run rt-setup-fulltext-index. 

I just installed rt 4.2.0 in a CentOS 6.4 (64bits) with MariaDB (which it's already supporting Sphinx ) and I had the same issue.

Cheers,
Carlos
El 15/04/2013, a las 20:20, Maciej Dobrzanski escribió:

> Hello,
> 
>> Looking in the RT log I found this error:
>> "ERROR 1430: There was a problem processing the query on the foreign 
>> data source.
>> Data source error: INTERNAL ERROR: 1st column must be bigint to accept
> 64-bit DOCID"
> 
> The problem I think is not so much in RT as it is in Sphinx. When building
> Sphinx binary, you can choose how long the document identifiers should be -
> they can be either 32-bit or 64-bit if --enable-id64 was specified.
> Depending on this setting Sphinx simply wants either 4 or 8 byte integers on
> input to match the internal type. It simply lacks some flexibility to accept
> shorter types. You can maintain compatibility with the original RT database
> by re-building Sphinx without --enable-id64.
> 
> Maciek
> 

--
Carlos Fuentes Bermejo
Security Engineer. IRIS-CERT
RedIRIS / Red.es

Tel.: +34 91 212 76 20 (Ext. 5583)
Mobile: + 34 675 54 41 69
E-Mail: carlos.fuentes at rediris.es
PGP Key ID: 0xF20D4295 2004-06-24
	Fingerprint: ED02 A355 71B6 702A 5907 2571 8C2C E601 F20D 4295

http:://www.rediris.es/cert


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20131011/da31f116/attachment.sig>