On 2-May-08, at 1:20 PM, Alok Dhir wrote:
Here's another question on this rather old thread -- while poring
through various options in solrconfig, I came across the the
'native' lockType option.
That seems to indicate that SOLR/Lucene should work fine with
multiple writers, as long as a
Hi,
I have a requirement that one of the fields that I had indexed as a
Text Field earlier should now return me results when searched with blank
spaces in between the word. I had tried to use the example in
wiki(http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#head-83
c527b144cd9f71c
Hardy has solr packages already. You might want to look how they packaged
solr if you cannot move to that version.
Did you just drop the war file? Or did you use JNDI? You probably need to
configure solr/home, and maybe fiddle with
securitymanager stuff.
Albert
On Thu, May 1, 2008 at 6:46 PM, Jac
Try adding echoParams=all to the request.
Maybe there is a default rows=0 or something.
Are you using a recent version of Solr?
-Yonik
On Fri, May 2, 2008 at 4:30 PM, Jon Baer <[EMAIL PROTECTED]> wrote:
> Sorry about that, Im sending something simple like:
>
>http://search.company.com:8115/solr/
Sorry about that, Im sending something simple like:
http://search.company.com:8115/solr/search/players?q=Smith&shards=box1:8115/search/players,box2:8115/search/players
Im getting back:
0
18
Identical schemas, it found the correct 13 but no docs attached. In
the logs I can
Here's another question on this rather old thread -- while poring
through various options in solrconfig, I came across the the 'native'
lockType option.
That seems to indicate that SOLR/Lucene should work fine with multiple
writers, as long as a proper locking mechanism is in place, such as
On Fri, May 2, 2008 at 3:36 PM, Jon Baer <[EMAIL PROTECTED]> wrote:
> Im trying to figure out if I can do this or if something else needs to be
> set, trying to run a query over multiple cores w/ the shard param? I seem
> to be getting the correct number of results back but no data ... any ideas?
Hi,
Im trying to figure out if I can do this or if something else needs to
be set, trying to run a query over multiple cores w/ the shard param?
I seem to be getting the correct number of results back but no
data ... any ideas?
Thanks.
- Jon
I'm not sure what "large db" you are referring to (indexing a RDBMS to Solr?),
but the first thing to do is run ulimit -a (or some flavour of it, depending on
the OS) and increase the open file descriptors limit if the one you see there
is just very low (e.g. 1024). If that limit is not low, ma
This bug was introduced in SOLR-509 (committed April 17th).
I'm working on a fix now.
-Yonik
On Fri, May 2, 2008 at 2:32 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Fri, May 2, 2008 at 1:08 PM, Matthew Runo <[EMAIL PROTECTED]> wrote:
> > Hah, thank you for doing this. Sometimes I see MultiS
I'm getting this with Solr 1.2 trying to load a large db. Is there a
workaround?
On Fri, May 2, 2008 at 1:08 PM, Matthew Runo <[EMAIL PROTECTED]> wrote:
> Hah, thank you for doing this. Sometimes I see MultiSegmentReaders,
> sometimes SegmentReaders, so both show up from time to time. Right now we've
> got two MultiSegmentReaders open..
OK, this implies there's a leak and the
We have a dedicated server set up as the "master", with it's own local
index. We have an NFS mount (read-only) on each of the other machines
which the master copies it's index to every 20 minutes. We run a
commit on each "slave" then to force them to open new readers. So far,
it's worked fi
Ah, wait, my fault - I didn't have the right Solr port configured in
the slave, so snapinstaller was commiting the master :/
Thanks,
James
On 2 May 2008, at 09:17, Bill Au wrote:
snapinstall calls commit to trigger Solr to use the new index. Do
you see
the commit request in your Solr log?
Hah, thank you for doing this. Sometimes I see MultiSegmentReaders,
sometimes SegmentReaders, so both show up from time to time. Right now
we've got two MultiSegmentReaders open..
Thanks!
Matthew Runo
Software Developer
Zappos.com
702.943.7833
On May 1, 2008, at 7:19 PM, Koji Sekiguchi wrot
Hi Otis,
Thanks,
Before I sent my first email to solr-user, I checked the follows:
1. Disk is not full, there is 40G available.
2. There is not snapshot created last midnight under solr/data folder.
3. I checked the log and there is no any new log for the snapshoter.
4. I sent the snapshoter comm
snapinstall calls commit to trigger Solr to use the new index. Do you see
the commit request in your Solr log? Anything in the snapinstaller log?
Bill
On Thu, May 1, 2008 at 8:35 PM, James Brady <[EMAIL PROTECTED]>
wrote:
> Hi Ryan, thanks for that!
>
> I have one outstanding question: when I
Hi Feng,
That's not enough information for anyone to help. You should have a look at
the snapshooter log.
Here are some other ideas:
- What does "did not work" mean? No snapshot was created?
- Is your disk/partition full?
- Can you run commit or optimize now and see if snapshooter will work?
O
Hi,
Here is the config info in solrconfig.xml:
/opt/solr-jetty/solr/bin/snapshooter
/opt/solr-jetty/solr/data
true
arg1 arg2
MYVAR=val1
/opt/solr-jetty/solr/bin/snapshooter
/opt/solr-jetty/solr/data
true
Our system updates the solr index o
On Fri, May 2, 2008 at 8:17 AM, Geoffrey Young
<[EMAIL PROTECTED]> wrote:
> does this apply to facet fields as well? I noticed that that if I set
> facet.sort="true" the results are indeed sorted by count... until the counts
> are the same, after which they are in random order (instead of ascii a
Hey Matt - congratulations on your new site -- it looks great.
I'm curious, after a few weeks of having run this way, what your
findings are regarding running the shared index on NFS. Any problems
as of yet?
I assume you're indexing from one machine and calling 'commit' on the
others on
Ok, thanks for the question as it would seem that I have found the answer.
Changing to a string field type fixes the problem. As we do not search over
the chapterTitle field this is no loss.
Thanks again for pointing me in the right direction
--
View this message in context:
http://www.nabble.
Erik Hatcher wrote:
>
> What field type is chapterTitle? I'm betting it is an analyzed
> field with multiple values (tokens/terms) per document. To
> successfully sort, you'll need to have a single value per document -
> using copyField can help with this to have both a searchable field
Erik Hatcher wrote:
What field type is chapterTitle? I'm betting it is an analyzed field
with multiple values (tokens/terms) per document. To successfully sort,
you'll need to have a single value per document - using copyField can
help with this to have both a searchable field and a sortab
What field type is chapterTitle? I'm betting it is an analyzed
field with multiple values (tokens/terms) per document. To
successfully sort, you'll need to have a single value per document -
using copyField can help with this to have both a searchable field
and a sortable version.
Thanks a lot. I could able to extract all terms in a field for any query.
Also I was wondering how can I extract nearest term info for autocomplete
kind of suggestion. In one of my earlier post, I asked same kind of question
related to faceted search.
-RB
On 4/27/08, Chris Hostetter <[EMAIL PROT
I have some data which I am querying with
?q=aseptic technique&fl=id,score,chapterTitle&sort=chapterTitle asc&rows=200
The results are being reordered (at least they are no longer in score order)
but the order makes no sense:
Communication
Drug administration: cytotoxic drugs
Elimination: bowel
27 matches
Mail list logo
