Sphinx Search

[kontrabass]

Is there a definite solution for the "duplicate key" errors? Had been running Orban's original Sphinx solution for 2 years... Migrated site to new servers, then implemented Orbans version .1 solution. Now I'm getting these errors like many others in this thread:


MySQL Error : Duplicate entry 'c7ff13943221ad39284628de371af860-lastpost-DESC' for key 2
Error Number : 1062


I've tried repairing, optimizing, and truncating the table, No change

Someone mentioned modifying the php to read "REPLACE" instead of "INSERT" ? I'm running 3.6

Thanks!

[kmike]

Originally Posted by kontrabass

Someone mentioned modifying the php to read "REPLACE" instead of "INSERT" ? I'm running 3.6

I'm not sure why there are duplicate keys, but looking at the script, I guess that changing INSERT to REPLACE at the end of the script will indeed help.


Another note for those running Sphinx search: if you have "finduser" action handled by Sphinx, it will _not_ find user's posts comprised entirely of separators, i.e. not containing any accepted characters from Sphinx charset_table.
Some examples of the posts ignored by Sphinx:

.....

--------->

It may appear as not important, but it's something to remember when the user's post count differs from the number of his posts found by Sphinx.

[DaiTengu]

I'm looking to upgrade to 3.8, and I've seen a few posts stating that 0.1 is not working properly there. Can anyone confirm/deny this?

[mlx]

We are still using the old instructions with vB 3.8.2 and didn't hear any complaints yet, so I believe it's still working nicely. Not sure about that plugin version though.

[DaiTengu]

Originally Posted by mlx

We are still using the old instructions with vB 3.8.2 and didn't hear any complaints yet, so I believe it's still working nicely. Not sure about that plugin version though.

Yeah, I'm using the plugin version.


Maybe I'll just have to spend some time running some more test upgrades.

[mute]

Has anyone looked into the MySQL binary support in Sphinx 0.9.9? It seems to me like this would greatly simplify the integration of Sphinx into vB. The gist of it is:

"The ultimate new feature couple is MySQL binary protocol and SphinxQL query language. Meaning that searchd can now pretend it's mysqld. Meaning that you can use ye good olde mysql command-line client to connect to searchd and fire your queries using regular SELECT syntax!"

For more info: http://sphinxsearch.com/docs/current.html#sphinxql

[kmike]

SphinxQL isn't quite ready for the production at this moment.

[RedWingFan]

I've had an odd problem come up.

We only have Sphinx running on our private testing-only forum, where our staff puts it through the paces a bit. I noticed a few days ago that, during a search, I came up with this error message:

unknown local index 'threaddelta' in search request

Another of our staff got that error yesterday. I've been trying other searches on and off, but I can't duplicate the error.

On the server side, here's what I found. In my Sphinx data directory, all the files look OK, except for the threaddelta.* files. In fact, there is a set of threaddelta.* files that hasn't been touched since May 29. However, there is now a new group of files, threaddelta.new.* in the same directory that are getting updated every three minutes by our cron job.

I realize I could delete all the files rebuild the indexes, which I will do (this isn't exactly a critical forum, as it's just for testing), but I would still like to know how Sphinx is generating the "threaddelta.new.* files vs. the original "threaddelta.*" files. None of the config files or cron entries have been touched since last year, when I set this up.

We're about to roll out Sphinx on our main forum as we're getting slammed with traffic lately, but I'm still hesitant due to unresolved bugs...

[UK Jimbo]

Originally Posted by RedWingFan

On the server side, here's what I found. In my Sphinx data directory, all the files look OK, except for the threaddelta.* files. In fact, there is a set of threaddelta.* files that hasn't been touched since May 29. However, there is now a new group of files, threaddelta.new.* in the same directory that are getting updated every three minutes by our cron job.

Is the cronjob that's running the indexer creating any output?

Do you see any output if you run the indexer from the command line?

Can you copy/paste the command line you're using along with any output back here?

[mute]

Originally Posted by kmike

SphinxQL isn't quite ready for the production at this moment.

Well, a few months have gone by, hopefully Andrew has fixed most of the outstanding bugs by now. I'm still excited at the prospect of leaving most of the vB search code alone, and just hooking in before the queries get executing and diverting them to sphinx (or something along those lines).

Our sphinx implementation has been going strong for a few years now, and while we still don't have "Find all posts/threads" queries hitting it, or any of the new search functionality, I'm still enormously pleased with what it can do for you.