Hi,
I'm actually facing a relevancy issue with multiword synonyms.
Let's expose it by a test case:
Giving the following synonyms definitions:
capital punishement, death sentence, death penalty
Bill,
Currently it is a plug-in. Put the lower case filter ahead of kstem,
just as for porter (example below). You can use it with porter, but I
can't imagine why you would want to. At least not in the same analyzer.
Hope this helps.
fieldtype name=text_kstem class=solr.TextField
Inline...
On Sep 11, 2007, at 7:27 AM, Laurent Gilles wrote:
Hi,
I'm actually facing a relevancy issue with multiword synonyms.
Let's expose it by a test case:
Giving the following synonyms definitions:
capital
Hi, I just posted this to the ruby/google group. It probably belongs
here! Also, anyone know exactly what the @ symbol in the curl command
is doing?
Thanks,
Matt
I've got a script that uses curl, and would like (for educational
purposes mind you) to use ruby instead. This is the curl
The curl man page states:
If you start the data with the letter @, the rest should be a
file name to read the data from, or - if you want curl to read the data
from stdin. The contents of the file must already be
url-encoded. Multiple files can also be specified.
Hello,
I have a question regarding filter query default operator. Is there
a way, to change the default filter query parser operator. As i know
it`s being set to 'OR' regardless of what the solrconfig says.
Thanks in advance
-Rafal
Hi Michael,
Thanks for that. I've got something that's working now:
data = File.read('my_solr_docs.xml')
url = URI.parse('http://localhost:8080/my_solr/update')
http = Net::HTTP.new(url.host, url.port)
response, body = http.post(url.path, data, {'Content-type'='text/
xml; charset=utf-8'})
I was going through some old emails on this topic. Rafael Rossini figured
out how to run multiple indices on single instance of jetty but it has to
be jetty plus. I guess jetty doesn't allow this? I suppose I can add
additional jars and make it work but I haven't tried that. It'll
always be much
Jack L wrote:
Hi,
I'm about to start a new solr installation. Given the good quality of
development builds in the past, should I use 1.2 or just grab a
nightly build?
Unless you *need* the new features in trunk, stick with 1.2
While we aim to keep the trunk functioning properly, the API's,
Matt,
Try this instead:
gem install solr-ruby # ;)
Then in irb or wherever:
solr = Solr::Connection.new(http://localhost:8983/solr;)
solr.add(:id = 123, :title = insert title here)
solr.commit
solr.query(title)
Visit us over on the [EMAIL PROTECTED] e-mail list for more
on
Is there any chance you're optimizing each time you commit?
Erick
On 9/10/07, Marius Hanganu [EMAIL PROTECTED] wrote:
Hi,
We're having a problem when commiting to SOLR.
Our application commits right after each update - we need the data to be
available instantaneously. The index' size is
Yes! Beautiful. I'll be checking that out.
matt
On Sep 11, 2007, at 12:18 PM, Erik Hatcher wrote:
Matt,
Try this instead:
gem install solr-ruby # ;)
Then in irb or wherever:
solr = Solr::Connection.new(http://localhost:8983/solr;)
solr.add(:id = 123, :title = insert title here)
On 11-Sep-07, at 7:53 AM, Rafał Kuć wrote:
Hello,
I have a question regarding filter query default operator. Is there
a way, to change the default filter query parser operator. As i know
it`s being set to 'OR' regardless of what the solrconfig says.
Nope. The default query parser
On 11-Sep-07, at 8:33 AM, Jack L wrote:
Hi,
I'm about to start a new solr installation. Given the good quality of
development builds in the past, should I use 1.2 or just grab a
nightly build?
Probably 1.2, unless you need new features. Note that there has been
a lot of major work
On 10-Sep-07, at 4:07 AM, Marius Hanganu wrote:
Hi,
We're having a problem when commiting to SOLR.
Our application commits right after each update - we need the data
to be available instantaneously. The index' size is about 166M,
Solr has 1024M on a dual quad.
The update takes a few
On 11-Sep-07, at 8:52 AM, Jack L wrote:
I was going through some old emails on this topic. Rafael Rossini
figured
out how to run multiple indices on single instance of jetty but it
has to
be jetty plus. I guess jetty doesn't allow this? I suppose I can add
additional jars and make it work
Erik Hatcher wrote:
melkink - are you using solr-ruby? If so, that bug has been fixed in
later versions ;)
Erik
Erik,
Indeed I am! Thanks for letting me know that there's a new version
available that fixes this bug. Like I said I'm a bit of noob when it comes
to both
Hello Mike,
but it is still just an example application.
I think this is a very modest statement. I'd like to say both solr
(including the example) and jetty are production level software.
I suppose many users, like me, will just take it and make minimum
modification of the configs and use it
I was going through some old emails on this topic. Rafael Rossini
figured out how to run multiple indices on single instance of jetty
but it has to be jetty plus. I guess jetty doesn't allow this? I
suppose I can add additional jars and make it work but I
haven't tried
that. It'll
On 11-Sep-07, at 3:32 PM, George Aroush wrote:
The example that comes with Solr is meant to be a starting
point for users. It is a relatively functional and
well-commented example, and its config files are pretty much
the canonical documentation for solr config, and for many
people they can
On Sep 11, 2007, at 5:13 PM, melkink wrote:
Erik Hatcher wrote:
melkink - are you using solr-ruby? If so, that bug has been fixed in
later versions ;)
Erik
Erik,
Indeed I am! Thanks for letting me know that there's a new version
available that fixes this bug. Like I
21 matches
Mail list logo
