Let me give the full user case... There has been a little
misunderstanding, but really some good discussions...
1. Some Cardiologists are also Family Doctors and Internal Medicine
doctors (Internist).
2. The use case that confuses the users is the output of the query
when using dismax across 2 fie
Remy,
didn't use it myself .. but you know about
https://github.com/gsf/node-solr ?
Regards
Stefan
Am 20.07.2011 20:05, schrieb Remy Loubradou:
I think I can trust you but this is weird.
Funny things if you try to validate on http://jsonlint.com/ this JSON,
duplicates keys are automatically
What does the committers think about adding a index queue in Solr?
Then we can have lots of one-off index requests that would queue up...
On Fri, Jul 22, 2011 at 3:14 AM, Pierre GOSSE wrote:
> Solr still respond to search queries during commit, only new indexations
> requests will have to wait
I have a site where users can place advertisements. My DB is MSSQL2008.
This is my sql statement when a user deletes an ad (you see its not
completely deleted, but rather its updated):
UPDATE ads SET deletedate = GETDATE(), deletereason = @deletereason,
updatedate = GETDATE() WHERE (id = @id)
he
It works fine but you would keep an eye on additional overhead, cores
`stealing` too much CPU from others, trouble with cores that merge segments
stealing I/O and of course RAM. It can also result in quite a high number of
open file descriptors.
There are more, but these seem most common to me.
