Thanks Otis.
I went through every piece of info that I could lay may hands on.
Most of them are about incompatible SolrJ versions (that's not my case) and
there was one message from Mark Miller that Solr may respond with an XML
instead of javabin in case there was some kind of http error being
I'm unclear on this point from the documentation. Is it possible to give
Solr X # of document IDs and tell it that I want documents similar to those
X documents?
Example:
- The user is browsing 5 different articles
- I send Solr the IDs of these 5 articles so I can present the user other
simi
I want to avoid duplicate values in one multivalued field.
i am using dataimport handler to import data, the particular multivalued
field are being filled from xml source. now that xml has duplicate values,
but i want to have unique valued in this multivalued field.
e.g. xml
a1
b1
According to what I see, the basic LRUCache implementation has an empty
close(), that is why it still works for the already closed searcher.
According to the base interface, the close() is there for "freeing non
memory resources".
Can someone explain this counter intuitive behavior?
Why is it allo
> I want to avoid duplicate values in
> one multivalued field.
>
> i am using dataimport handler to import data, the
> particular multivalued
> field are being filled from xml source. now that xml has
> duplicate values,
> but i want to have unique valued in this multivalued field.
>
> e.g. xml
> The values are at same logical
> position.
You mean positionIncrementGap set to 0? can you see that duplicates are removed
in analysis page?
By the way returned values are original (stored) values. Analysis (tokenfilter
tokenizer etc) are about indexed values. UpdateProcessorFactory can chang
Otis, stop teasing people! You know as well as I do that 2 is the maximum
edit distance for fuzzy query in 4.0.
So,
Keyword~5
Is treated as:
Keyword~2
Check with &debug=query to see.
-- Jack Krupansky
-Original Message-
From: Otis Gospodnetic
Sent: Tuesday, December 25, 201
25 December 2012, Apache Solr™ 3.6.2 available
The Lucene PMC and Santa Claus are pleased to announce the release of
Apache Solr 3.6.2.
Solr is the popular, blazing fast open source enterprise search
platform from the Apache Lucene project. Its major features include
powerful full-text search, hi
Please see http://wiki.apache.org/solr/SimpleFacetParameters for more
details
On Friday, December 21, 2012, hank williams wrote:
> Great, thank you.
>
> > Date: Fri, 21 Dec 2012 14:42:13 +0100
> > From: r@solr.pl
> > To: solr-user@lucene.apache.org
> > Subject: Re: facet query
> >
> > Hello
But you are assuming 4.0 :)
Otis
Solr & ElasticSearch Support
http://sematext.com/
On Dec 25, 2012 10:47 AM, "Jack Krupansky" wrote:
> Otis, stop teasing people! You know as well as I do that 2 is the maximum
> edit distance for fuzzy query in 4.0.
>
> So,
>
>Keyword~5
>
> Is treated as:
>
>
Hi,
I went through example for spatial search in Solr 4.0
(http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4)
Both indexing and searching work fine.
Example is: fq=geo:"Intersects(-74.093 41.042 -69.347 44.558)"
My problem is how to send values to "Intersects" operation as parameters.
If
I've been thinking about aliases for a while as well. Seem very handy and
fairly easy to implement. So far there has just always been higher priority
things (need to finish collection api responses this week…) but this is
something I'd def help work on.
- Mark
On Dec 25, 2012, at 1:49 AM, Otis
The problem is not necessary xml - it seems to be anything that is not valid
javabin - I've just most often seen it with 404s that return an html error.
I'm not sure if there is a jira issue or not, but this type of thing should be
failing in a more user friendly way.
As to why your response is
MLT has both a request handler and a search component.
The MLT handler returns similar documents only for the first document that
the query matches.
The MLT search component returns similar documents for each of the documents
in the search results, but processes each search result base docume
Hi Mladen,
Despite some similarities at first glance, the Solr 4 spatial fields are not
implemented with Solr query parsers, unlike Solr 3 spatial. Everything in
quotes is handled by the field type. What you're looking for is for the
Solr 3 geospatial functions to be adapted to support the Solr
15 matches
Mail list logo
