Hi,
We are facing a problem in getting the facet Count for a
particular query. We are getting the weight as 12m and it is indexed a string
field.
But when we make a facet query like,
http://localhost:8983/solr/select?q=ipod&rows=0&facet=true&facet.limit=-1&fac
et.query=weight:{0m TO 1
Bill,
Thanks for the explanation. That helps my understanding on rsync and the
replication in general.
regards,
-Hui
On 9/20/07, Bill Au <[EMAIL PROTECTED]> wrote:
>
> The "solr" that you are referring to in your third question in the
> name of the rsync area which is map to the solr data dire
Got it. So what's the easiest way to get this patch? Sorry i'm new to this.
regards,
-Hui
On 9/20/07, Bill Au <[EMAIL PROTECTED]> wrote:
>
> That would be my bad. I noticed the problem while fixing SOLR-282
> which is not related. I fixed both problems in stead of opening a
> different bug fo
Hi,
I need a clarification regarding the SOLR Ranking.
consider the scenario for searching for courses based on following
relevance:
a. Courses with the term in the courseTitle, courseTag and in the
courseDescription would appear first
b. Courses with the term in the courseTitle and i
That would be my bad. I noticed the problem while fixing SOLR-282
which is not related. I fixed both problems in stead of opening a
different bug for the response format issue. I will update the change
log.
Bill
On 9/20/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> :
> : It seems there's a
The "solr" that you are referring to in your third question in the
name of the rsync area which is map to the solr data directory. This
is defined in the rsyncd configuration file which is generated on the
fly as Chris has pointed out. Take a look at rsyncd-start.
snappuller rsync the index from
: So just to help my knowledge, where does this virtual setting of this "solr"
: string happen? Should it be in some config file or sth?
rsyncd-start creates an rsync config file on the fly ... much of it is
constants, but it fills in the rsync port using a variable from your
config.
-Hoss
ok. Hoss. I think I'll believe you since nobody raised any issue running the
script. And I'm about to try it out shortly with different solr home names.
So just to help my knowledge, where does this virtual setting of this "solr"
string happen? Should it be in some config file or sth?
thanks,
You mean, when it says that facet term "foo" has 10 documents, you want
those 10 ids? I think that will require a further query from your
application.
Peter
-Original Message-
From: Cric Digs [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 20, 2007 12:43 PM
To: solr-user@lucene.apac
: I'm using faceting to get some results. I also want to get another field -
: the id field along with it. Is it possible to get that somehow in the facet
: results?
you're going to have to elaborate on what it is you are trying to do ... i
genuinely have no idea what you are asking (and i think
: home we have named. However, there's still the last part of my question
: that feels suspicious why the "solr" string is directly coded in the script
: (unlike other cases they usually use ${solr_root} to get to specific dirs.
: ) I pasted this line again below:
sorry ... i didn't realize you
Thanks, Hoss.
For the last question, yes I understand now it's referring to whatever solr
home we have named. However, there's still the last part of my question
that feels suspicious why the "solr" string is directly coded in the script
(unlike other cases they usually use ${solr_root} to get to
On 9/20/07, Walter Ferrara <[EMAIL PROTECTED]> wrote:
> I have an index with several fields, but just one stored: ID (string,
> unique).
> I need to access that ID field for each of the tops "nodes" docs in my
> results (this is done inside a handler I wrote), code looks like:
>
> Hits hits =
: 1) config different port for each solr home dir (since they run on the same
: host);
you mean a differnet rsync port right? ... yes the scripts as distributed
assume that each rsync daemon will be dedicated to a single solr
"instance" .. the idea beaing that even if you have 12 Solr intances
: Hits hits = searcher.search(query);
: for(int i=0; i
Ok, I should correct myself. For #1, I think we need to
1) config different port for each solr home dir (since they run on the same
host);
2) run rsync-start script under each of the solr home's bin dir.
(btw, just to make clear, we should run rsync-start after rsync-enable that
I understand.)
C
On 9/20/07, Walter Ferrara <[EMAIL PROTECTED]> wrote:
> I'm just wondering, as this cached object could be (theoretically)
> pretty big, do I need to be aware of some OOM? I know that FieldCache
> use weakmaps, so I presume the cached array for the older reader(s) will
> be gc-ed when the reader is
I've been struggling with this a bit so here goes:
I'm using faceting to get some results. I also want to get another field -
the id field along with it. Is it possible to get that somehow in the facet
results?
Thanks!
About stored/index difference: ID is a string, (= solr.StrField) so
FieldCache give me what I need.
I'm just wondering, as this cached object could be (theoretically)
pretty big, do I need to be aware of some OOM? I know that FieldCache
use weakmaps, so I presume the cached array for the older rea
English and French are messy, so heuristic methods are the only possible.
Spanish is rigorously clean, and stemming should be done from the declension
rules and irregular conjugation tables. This involves large (fast) tables in
ram rather than small (slow) string-shuffling.
Lance Norskog
-Ori
At 5:30 PM +0200 9/20/07, Walter Ferrara wrote:
>I have an index with several fields, but just one stored: ID (string,
>unique).
>I need to access that ID field for each of the tops "nodes" docs in my
>results (this is done inside a handler I wrote), code looks like:
>
> Hits hits = searcher.se
I have an index with several fields, but just one stored: ID (string,
unique).
I need to access that ID field for each of the tops "nodes" docs in my
results (this is done inside a handler I wrote), code looks like:
Hits hits = searcher.search(query);
for(int i=0; i
I am running against 1.2. Where would I get the 1.3-dev version?
I will try different versions of Tomcat and/or Jetty. Thanks for all
your suggestions, I'll let you know.
-Original Message-
From: Ryan McKinley [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 19, 2007 8:30 PM
To:
On 9/20/07, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> ...Betrand, does the French Snowball work fine?...
I've seen some weirdnesses, like "tennis" and "tenir" (means to hold)
both stemmed to "ten", but in all of our (simple) tests it was ok.
The application where we're using it does not requ
On Thu, 20 Sep 2007 09:53:46 -0400
"Yonik Seeley" <[EMAIL PROTECTED]> wrote:
> On 9/19/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
> > Maybe I got this wrong...but isn't this what mapreduce is meant to deal
> > with?
>
> Not really... you could force a *lot* of different problems into
> map-
On Thu, 20 Sep 2007 09:58:17 +0200
"David Welton" <[EMAIL PROTECTED]> wrote:
> That seems to be how Sphinx works:
>
> http://www.sphinxsearch.com/doc.html#distributed
>
> Of course, the details of this are far over my head for either system,
> so I don't really know if that's a sensible way of d
Nevermind! I figured out that the qf parameter handles any field names
that match a dynamic field name pattern, regardless of whether a field
is defined with that name.
-Doug
Doug Daniels wrote:
Hi,
I noticed that the "field list" (fl) parameter ignores field names that
it cannot locate, w
On 9/19/07, Pieter Berkel <[EMAIL PROTECTED]> wrote:
> However, I'd like to be able to
> analyze documents more intelligently to recognize phrase keywords such as
> "open source", "Microsoft Office", "Bill Gates" rather than splitting each
> word into separate tokens (the field is never used in sea
On Thu, 2007-09-20 at 15:27 +0200, Bertrand Delacretaz wrote:
> On 9/20/07, Thierry Collogne <[EMAIL PROTECTED]> wrote:
>
> > ...Thank you very much. Moving the up in the chain fixed it
>
> Yes, the problem was the EnglishPorterFilterFactory before the accents
> removal: the stemmer doesn't
On 9/19/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
> Maybe I got this wrong...but isn't this what mapreduce is meant to deal with?
Not really... you could force a *lot* of different problems into
map-reduce (that's sort of the point... being able to automatically
parallelize a lot of differen
We are indexing both french and dutch. I will take a look at
SnowballPorterFilterFactory later, but thanks for the advice.
On 20/09/2007, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
>
> On 9/20/07, Thierry Collogne <[EMAIL PROTECTED]> wrote:
>
> > ...Thank you very much. Moving the up in the c
Thanks, Pieter. I'll go for that then.
Mark
On Sep 19, 2007, at 10:15 PM, Pieter Berkel wrote:
Sounds like you're on the right track, if your groups overap (i.e. a
document can be in group A and B), then you should ensure your
"groups"
field is multivalued.
If you are searching for "foo" i
Not sure if this is in the same league or not, but Yahoo offers a term
extraction
web service.
http://developer.yahoo.com/search/content/V1/termExtraction.html
On 9/20/07, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
>
> You might investigate some tools like Alias-i's LingPipe or do some
> search
You might investigate some tools like Alias-i's LingPipe or do some
searches for phrase recognition software, etc.
-Grant
On Sep 19, 2007, at 9:58 PM, Pieter Berkel wrote:
I'm currently looking at methods of term extraction and automatic
keyword
generation from indexed documents. I've bee
On 9/20/07, Thierry Collogne <[EMAIL PROTECTED]> wrote:
> ...Thank you very much. Moving the up in the chain fixed it
Yes, the problem was the EnglishPorterFilterFactory before the accents
removal: the stemmer doesn't know about accents, so no stemming
occured on "matthé" whereas "matthe" wa
We often have data that isn't generated by us going into our search. Sometimes there's a field that
shouldn't be multiValued, but the data comes in with multiple fields of the same name in a single
document.
Is there any way to continue processing other documents in a file even if one document
Thorsten,
Thank you very much. Moving the up in the chain fixed it.
On 20/09/2007, Thorsten Scherler <[EMAIL PROTECTED]>
wrote:
>
> On Thu, 2007-09-20 at 14:01 +0200, Thierry Collogne wrote:
> > I have entered the the matthé term in the the analyzer, but as far as I
> > understand, it should be
On Thu, 2007-09-20 at 14:01 +0200, Thierry Collogne wrote:
> I have entered the the matthé term in the the analyzer, but as far as I
> understand, it should be ok. I have made some screenshots with the results.
>
> http://farm2.static.flickr.com/1407/1412619772_0b697789cd_o.jpg
>
> http://farm2.s
On Thu, 2007-09-20 at 13:33 +0200, Thierry Collogne wrote:
> We are using this schema definition
>
Thierry, try to move the solr.ISOLatin1AccentFilterFactory up the filter
cue, like:
...
...
for both indexing and query.
This way you make sure that all accent are gone before you do further
I have entered the the matthé term in the the analyzer, but as far as I
understand, it should be ok. I have made some screenshots with the results.
http://farm2.static.flickr.com/1407/1412619772_0b697789cd_o.jpg
http://farm2.static.flickr.com/1245/1412619774_3351b287bc_o.jpg
I find it strange th
We are using this schema definition
I will take a look at the analyzer took.
Thank you both for the quick response.
O
On 9/20/07, Thierry Collogne <[EMAIL PROTECTED]> wrote:
> ..when we search for "matthé" or for "matthe", we get two totally
> different results
The analyzer admin tool should help you find out what's happening, see
http://wiki.apache.org/solr/FAQ#head-b25df8c8393bbcca28f1f344c432975002e29ca9
On Thu, 2007-09-20 at 10:11 +0200, Thierry Collogne wrote:
> Hello,
>
> We are experiencing some strange behavior while searching with words
> containing accents.
> We are using two examples "rené" and "matthé"
>
> When we search for "rené" or for "rene", we get the same results, so that is
> ok.
Hello,
We are experiencing some strange behavior while searching with words
containing accents.
We are using two examples "rené" and "matthé"
When we search for "rené" or for "rene", we get the same results, so that is
ok.
But when we search for "matthé" or for "matthe", we get two totally
differ
> Maybe I got this wrong...but isn't this what mapreduce is meant to deal with?
> eg,
>
> 1) get the job (a query)
> 2) map it to workers ( servers that provide search results from their own
> indexing)
> 3) wait for the results from all workers that reply within acceptable
> timeframe.
> 4) comb
: Does this case arise when i do a search when there is no index?? - If yes,
: then i guess the Exception can be made more meaningful.
in normal operation, i believe this shouldn't happen -- Solr will create
the index for you on startup if there isn't one. You're attampting a
fairly advanced
:
: It seems there's a small bug in the bin/commit script for solr 1.2.
A fix was already commited to the trunk for this as part of SOLR-282 (but
there doesn't seem to be a note about it in the changelog)
-Hoss
Hi, guys,
It seems there's a small bug in the bin/commit script for solr 1.2.
I was able to run snapinstaller successfully to install the index and open a
new searcher. (This is verified by querying the new docs through the web
admin UI.) However, the snapinstaller script failed due to the commit
48 matches
Mail list logo