Hi,
Wrong list. :) I answered your question on solr-user.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: rahul_k123 <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Tuesday, September 23, 2008 11:00:02 PM
> Subject: Rsync cau
Hi,
I am using snappuller to sync my slave with master, i am not using rsync
daemon, i am doing Rsync using remote shell.
When i am serving requests from the master when the snappuller is running
(after optimization, total index is arnd 4 gb it doing the transfer of whole
index), the performance
Thanks Matt,
I will go for Erick's suggestion as the combination can be messy: for
a.b.c I would need to store a,b,c,a.b,b.c and a.b.c
Cheers
Matthew Hall wrote:
We have a similar requirement here at our work.
In order to get around it we create two indexes, one of which
punctuation is re
But the "default_field" for your query parser is just that, the default
*if nothing else is specified*. So the following would work just fine:
QueryParser parser = new QueryParser("default_field", analyzer);
query = parser.parse("name:Erin AND name:Brochowich AND organization:ABC AND
organization:
unstructured query:
default_field: abc ^5 and xyz
seems to have created a confusion, what I meant was while initializing
the parser I have "default_field" as the default text field. So, the
query should be:
QueryParser parser = new QueryParser("default_field",analyzer);
query = parser.parse("abc
We have a similar requirement here at our work.
In order to get around it we create two indexes, one of which
punctuation is relevant, and one in which all punctuation is treated as
a place to break tokens.
We then do a search against both indexes and merge the results, it seems
that such a
Thanks Erick, you are right about the various combinations.
Cheers,
Erick Erickson wrote:
Yes you can query *method. But you have to turn leading wildcards
(which I don't have right on the tips of my fingers, but know it's been
an option for some time now).
But your solution doesn't scale well.
On Sep 23, 2008, at 8:35 AM, Anshul jain wrote:
yes you are partly correct
what I need is that lucene should support two type of queries for the
following document:
name: abc^10
organization: xyz^3
structured query:
name: abc and organization: xyz
unstructured query:
default_field: abc ^5 an
Just an idea... Along winded one. I'm not sure either.! Pardon me if I am
directing you in the wrong direction
If you add a lucene doc like below into your main index
- Doc 1 -
Field1: rainy today
Field2: rainy yesterday
Field3: weather forcast for tomorrow
- Doc 2 -
Field1: rainy tomorrow
Fiel
On Tue, Sep 23, 2008 at 5:28 PM, Grant Ingersoll <[EMAIL PROTECTED]>wrote:
> So, the piece I'm missing is how do you know what field for which terms.
> In other words how do you know xyz goes against organization and abc
> against name. Your wording implies that you don't know this before hand,
Are you sure you want to be boosting the document fields at
index time? From Hossman
<<>>
But Lucene isn't magic, it's an engine that you have to
make do what you want. You say
"But i do not want to create one more field(default_field)
that will contain all the values concatenated in it"
Is t
That still seems excessive. Are you measuring your first sort? Lucene
builds up caches to help sort with the first few *sorts* that happen, so
that's a possibility.
But if that isn't the case, I think you need to slap a profiler on the
problem and see where you're spending your time. I'd also be c
yes you are partly correct
what I need is that lucene should support two type of queries for the
following document:
name: abc^10
organization: xyz^3
structured query:
name: abc and organization: xyz
unstructured query:
default_field: abc ^5 and xyz
But i do not want to create one more field(de
Yes you can query *method. But you have to turn leading wildcards
(which I don't have right on the tips of my fingers, but know it's been
an option for some time now).
But your solution doesn't scale well. If you had
a.b.c.d.e.f.g.h you'd have to store many combinations in order
to do what you wan
So, the piece I'm missing is how do you know what field for which
terms. In other words how do you know xyz goes against organization
and abc against name. Your wording implies that you don't know this
before hand, yet you are somehow suggesting that Lucene should be able
to do it. Corre
Here is what I'm trying to do:
say a lucene document:
name: abc ^10
organization: xyz ^3
^10 and ^3 are boosts in the document.
now if I query name: abc ^5 AND organization: xyz this will work.
but if I query (default_field): abc^5 AND xyz this won't work.
Now what I want is that a text can be
Thanks a lot, i've discovered about Solr , column classification and other
interesting things. ;)
Best
Stas
hossman wrote:
>
>
> : For example, in my case it's car searching form.
> : First of all i'm telling that i want to search for BMW. System returning
> set
> : of results.
> : In pro
17 matches
Mail list logo
