I am wondering if any one has tried this with MySQL 5.6 and RT 4.x?
FYI, MySQL 5.6 has still not hit general availability (GA), and is hence
still a development release.
I have RT 4.0.8 working on my test VM with MySQL 5.6.8, but need to
confirm if I can use same Index as documented here:
No. That index is specific to the Sphinx indexer, and will do nothing
useful to interact with MySQL 5.6.
RT does not have support for MySQL 5.6’s fulltext search; we’re looking
forward to it hitting GA, at which point we’ll look into implementing
support for it. But as of now, 5.0 or 5.1 with Sphinx is the only
solution on MySQL.
Can I just confirm a couple of things here? (since I’m just about to upgrade our slightly aged RT system)
If I migrate my 3.6.5 mySQL-based system to 4.x, the current content searches will still work at the same sort of speed that they do now, will they not? Is the full-text search in postgres-based systems an enhancement or is 4.0/mySQL/content search a regression over 3.x?
Is there a simple way to migrate from mySQL to postgres?
Thanks in advance,
AndyOn 12 Dec 2012, at 19:23pm, Alex Vandiver wrote:
On Wed, 2012-12-12 at 18:08 +0000, Daksh Chauhan wrote:
I am wondering if any one has tried this with MySQL 5.6 and RT 4.x?
FYI, MySQL 5.6 has still not hit general availability (GA), and is hence
still a development release.
I have RT 4.0.8 working on my test VM with MySQL 5.6.8, but need to
confirm if I can use same Index as documented here:
No. That index is specific to the Sphinx indexer, and will do nothing
useful to interact with MySQL 5.6.
RT does not have support for MySQL 5.6’s fulltext search; we’re looking
forward to it hitting GA, at which point we’ll look into implementing
support for it. But as of now, 5.0 or 5.1 with Sphinx is the only
solution on MySQL.
If I migrate my 3.6.5 mySQL-based system to 4.x, the current content
searches will still work at the same sort of speed that they do now,
will they not? Is the full-text search in postgres-based systems an
enhancement or is 4.0/mySQL/content search a regression over 3.x?
Indexed searching on MySQL with Sphinx, Postgres, and Oracle, is an
enhancement in 4.0. If you wish to have non-indexed content searching
in 4.0 (as 3.8 and below have), you will need to explicitly enable it in
your RT_SiteConfig; 4.0 defaults it to off. See the %FullTextSearch
documentation in RT_Config.pm.
Is there a simple way to migrate from mySQL to postgres?
Not currently. There are community-created tools that attempt it, and
we’ve been working with a few clients on a more robust solution; we
expect that it will ship with RT 4.2.
Is there a simple way to migrate from mySQL to postgres?
Not currently. There are community-created tools that attempt it, and
we’ve been working with a few clients on a more robust solution; we
expect that it will ship with RT 4.2.
I’ve used this tool with success, I also package it with request-tracker in
the OpenSuSE devel:languages:perl repo. There are also a number of
“generic” mysql to postgres tools available which I’ve used with success as
well, google will be your friend to find them.
I’ve used this tool with success, I also package it with request-tracker
in the OpenSuSE devel:languages:perl repo. There are also a number of
“generic” mysql to postgres tools available which I’ve used with success
as well, google will be your friend to find them.
Thanks for maintaining distribution packages of RT! If you ever run
into issues or have questions about releases, find us in #rt on irc.perl.org.
It’d be great if you could clearly mark rt-mysql2pg as community
contributed, since it’s not an officially supported migration tool. It
may appear as such since it’s packaged with the rest of RT.
On Wed, 2012-12-12 at 18:08 +0000, Daksh Chauhan wrote:
I am wondering if any one has tried this with MySQL 5.6 and RT 4.x?
FYI, MySQL 5.6 has still not hit general availability (GA), and is hence
still a development release.
I have RT 4.0.8 working on my test VM with MySQL 5.6.8, but need to
confirm if I can use same Index as documented here:
No. That index is specific to the Sphinx indexer, and will do nothing
useful to interact with MySQL 5.6.
RT does not have support for MySQL 5.6’s fulltext search; we’re looking
forward to it hitting GA, at which point we’ll look into implementing
support for it. But as of now, 5.0 or 5.1 with Sphinx is the only
solution on MySQL.
-kevin> On Wed, 2012-12-12 at 14:23 -0500, Alex Vandiver wrote:
On Wed, 2012-12-12 at 18:08 +0000, Daksh Chauhan wrote:
I am wondering if any one has tried this with MySQL 5.6 and RT 4.x?
FYI, MySQL 5.6 has still not hit general availability (GA), and is hence
still a development release.
I have RT 4.0.8 working on my test VM with MySQL 5.6.8, but need to
confirm if I can use same Index as documented here:
No. That index is specific to the Sphinx indexer, and will do nothing
useful to interact with MySQL 5.6.
RT does not have support for MySQL 5.6’s fulltext search; we’re looking
forward to it hitting GA, at which point we’ll look into implementing
support for it. But as of now, 5.0 or 5.1 with Sphinx is the only
solution on MySQL.
Just out of curiosity, were you guys planning on