Hi,
I'm trying to get replication working, and it's failing because commit
refuses to work (at least as I understand it).
I run commit and point it to the update URL. I know the URL is correct,
because solr returns something to me:
commit request to Solr at http://solr.solrflare.com:8080/solr/a
For capacity planning, our autocomplete gets more than 10X as many
requests as our search. Solr can handle our search just fine, but
I wrote an in-memory prefix match to handle the 25-30M autocomplete
matches each day. I load that by doing Solr queries, so the two
stay in sync.
wunder
On 7/9/08 9
Would facet.prefix work for you?
-Yonik
On Fri, Jul 4, 2008 at 4:58 AM, Marian Steinbach <[EMAIL PROTECTED]> wrote:
> Hi all!
>
> I just startet evaluating Solr a few days ago and I'm quite happy with
> the way it works. The test project I am using on is a product search
> for a wine shop with 25
: Now I'd like to know what would be the best way to implement a search
: term autocompletion in the way of Google Suggest
: (http://www.google.com/webhp?complete=1&hl=en).
:
: Most autocomplete implementations aim to display search result entries
: during input. What Suggest does, and what I'd l
Thanks for the responses, Ian, Jacob.
While I could not locate the previous thread, this is what I understand..
While we can fine tune the cache parameters and other stuff which we can
directly control, with respect to index files the key is to give enough RAM
and let the the OS do its best with
On Thu, 10 Jul 2008 09:36:01 +0530
"Noble Paul _ __" <[EMAIL PROTECTED]> wrote:
> > 2. We're assuming we'll have thousands of users with independent data; any
> > good way to partition multiple indexes with solr? With Lucene we could
> > just save those in ind
: > Are there any other compatibility issues between the would-be
: > Solr 1.3 and Solr 1.2?
:
: It shouldn't be a compatibility issue since both will be accepted.
Note that the example configs tend to represent the latest/greatest syntax
& features, but existing configs should generally contin
On Thu, Jul 10, 2008 at 7:53 AM, aris buinevicius <[EMAIL PROTECTED]> wrote:
> We're trying to implement a large scale domain specific web email
> application, and so far solr performance on the search side is really doing
> well for us.
>
> There are two limitations that I can't seem to get around
We're trying to implement a large scale domain specific web email
application, and so far solr performance on the search side is really doing
well for us.
There are two limitations that I can't seem to get around however, and was
hoping for some advice.
1. We would like to do bulk tagging on larg
I would guess so also to a point. After you run out of RAM, indexing
also takes a hit. I have noticed on a 2Gb machine when the index gets
over 2Gb, my indexing rate when down from 100/s to 40/s. After
reaching 4Gb it was down to 10/s. I am trying now with a 8Gb machine
to see how far I get through
Is anyone out there using nagios to monitor solr?
I remember some discussion of this in the past around exposing
response handler timing info so it could play nice with nagios... did
anyone get anywhere with this? want to share :)
Any other pointers to solr monitoring tools would be good too.
t
On Wed, Jul 9, 2008 at 7:13 PM, Teruhiko Kurosaka <[EMAIL PROTECTED]> wrote:
> I've noticed that schema.xml in the dev version of Solr spells
> what used to be fieldtype as fieldType with capital T.
>
> Are there any other compatibility issues between the would-be
> Solr 1.3 and Solr 1.2?
It shoul
My total guess is that indexing is CPU bound, and searching is RAM bound.
Best,
Jacob
Ian Connor wrote:
> There was a thread a while ago, that suggested just need to factor in
> the index's total size (Mike Klaas I think was the author). It was
> suggested having the RAM is enough and the OS will
I've noticed that schema.xml in the dev version of Solr spells
what used to be fieldtype as fieldType with capital T.
Are there any other compatibility issues between the would-be
Solr 1.3 and Solr 1.2?
How soon Solr 1.3 will be available, by the way?
Basis Technology Corporation, San
There was a thread a while ago, that suggested just need to factor in
the index's total size (Mike Klaas I think was the author). It was
suggested having the RAM is enough and the OS will cache the files as
needed to give you the performance boost needed.
If I misread the thread, please chime in -
Oh thanks.
I don't want to search on that. I will have a name field that contains the
unique identifier of the document.
2008/7/9 Noble Paul നോബിള് नोब्ळ् <[EMAIL PROTECTED]>:
> On Wed, Jul 9, 2008 at 8:46 PM, Noble Paul നോബിള് नोब्ळ्
> <[EMAIL PROTECTED]> wrote:
> > yep. you cant search. It i
Hello All,
Prior to SOLR 1.3 and nutch patch integration - what actually is the effect of
SOLR (non)-timeout? Do the threads eventally die? DOes a new request cause a
new query thread to open, or is the system locked?
What causes a timeout- a complex query?
Is SOLR 1.2 open to DoS attack
On Wed, Jul 9, 2008 at 8:46 PM, Noble Paul നോബിള് नोब्ळ्
<[EMAIL PROTECTED]> wrote:
> yep. you cant search. It is better to extract the data out and index
> it if you want to search
>
> On Wed, Jul 9, 2008 at 8:37 PM, Norberto Meijome <[EMAIL PROTECTED]> wrote:
>> On Wed, 9 Jul 2008 19:51:45 +0530
yep. you cant search. It is better to extract the data out and index
it if you want to search
On Wed, Jul 9, 2008 at 8:37 PM, Norberto Meijome <[EMAIL PROTECTED]> wrote:
> On Wed, 9 Jul 2008 19:51:45 +0530
> "Noble Paul _ __" <[EMAIL PROTECTED]>
> wrote:
>
>> Y
On Wed, 9 Jul 2008 19:51:45 +0530
"Noble Paul _ __" <[EMAIL PROTECTED]> wrote:
> You can put it into a 'string' field directly
if we refer to the default string field , you won't be able to search for the
contents of the XML (unless you search for the whole t
You can put it into a 'string' field directly
On Wed, Jul 9, 2008 at 7:41 PM, Alexander Ramos Jardim
<[EMAIL PROTECTED]> wrote:
> I need to put big xml files on a string field in one of my projects. Does
> Solr accept it automatically or should I put a on my xml before
> putting on the index?
>
I need to put big xml files on a string field in one of my projects. Does
Solr accept it automatically or should I put a on my xml before
putting on the index?
--
Alexander Ramos Jardim
On Wed, 9 Jul 2008 08:48:35 +0530
"Shalin Shekhar Mangar" <[EMAIL PROTECTED]> wrote:
> Yes, SOLR-350 added that capability. Look at
> http://wiki.apache.org/solr/MultiCore for details.
ahh loving SOLR more every day :P
thx
_
{Beto|Norberto|Numard} Meijome
I used to hate
Hi,
we have found that some of the jars (like stax-api-xxx.jar, stax-utils.jar,
stax-xxx-dev.jar, commons-codec-xxx.jar) were missing in our application's
lib directory, by adding these libraries the mentioned exception resolved.
On Tue, May 27, 2008 at 12:56 PM, Akeel <[EMAIL PROTECTED]> wrote:
Hi Koji
Thanks for clarifying my understanding about MoreLikeThis.
After your response and reading from Solr Wiki, I am now successfully using
MoreLikeThis as follows -
- Using StandardRequestHandler. Removed MoreLikeThisHandler in
solrconfig.xml.
- Modified the query to be -
htt
Hi,
Since we plan to share the same box among multiple solr instances on a 16gb
RAM multi core box, Need to estimate how much memory we need for our
application.
The index size is on disk 2.4G with close to 3 million documents. The plan
is to use dismax query with some fqs.
Since we do not sort
26 matches
Mail list logo