You can do range queries without an upper bound and just limit the
number of results. Then you look at the last result to obtain the new
lower bound.
-- Jens
On 17/12/13 20:23, Petersen, Robert wrote:
My use case is basically to do a dump of all contents of the index with no
ordering
Exactly, you should usually design your schema to fit your queries, and
if you need to retrieve all ancestors then you should index all
ancestors so you can query for them easily.
If that doesn't work for you then either Solr is not the right tool for
the job, or you need to rethink your
On 03/01/2013 07:46 PM, Neal Ensor wrote:
Again, it appears to work on Safari fine hitting the same container,
so must be something Chrome-specific (perhaps something I have
disabled?)
This sounds like it might just be a browser cache issue (if you used
Chrome to access the same URL
this morning, and it all appears to
work. Flushed cache as well, so could be part of that. All's well
that ends well I suppose.
neal
On Mon, Mar 4, 2013 at 4:44 AM, Jens Grivolla j+...@grivolla.net
(mailto:j+...@grivolla.net) wrote:
On 03/01/2013 07:46 PM, Neal Ensor wrote:
Again, it appears to work
On 01/11/2013 06:14 PM, Gora Mohanty wrote:
On 11 January 2013 22:30, Jens Grivolla j+...@grivolla.net wrote:
[...]
Actually, that is what you would get when doing a join in an RDBMS, the
cross-product of your tables. This is NOT AT ALL what you typically do in Solr.
Best start the other way
On 01/14/2013 12:50 PM, Gora Mohanty wrote:
On 14 January 2013 16:59, Jens Grivolla j+...@grivolla.net wrote:
[...]
Then please show me the query to find users that are fluent in spanish and
english. Bonus points if you manage to not retrieve the same user several
times. (Hint, your schema
On 01/11/2013 05:23 PM, Gora Mohanty wrote:
You are still thinking of Solr as a RDBMS, where you should not
be. In your case, it is easiest to flatten out the data. This increases
the size of the index, but that should not really be of concern. As
your courses and languages tables are connected
So are you even doing text search in Solr at all, or just using it as a
key-value store?
If the latter, do you have your schema configured so
that only the search_id field is indexed (with a keyword tokenizer) and
everything else only stored? Also, are you sure that Solr is the best
option as
Maybe a filter like ISOLatin1AccentFilter that doesn't get applied when
using wildcards? How do the terms actually appear in the index?
Jens
On 05/23/2012 01:19 PM, spr...@gmx.eu wrote:
No one an idea?
Thx.
The text may contain FooBar.
When I do a wildcard search like this: Foo* - no
On 11/30/2011 05:40 PM, Marco Martinez wrote:
For anyone interested, recently I've been using a new Solr client for
Python. It's easy and pretty well documented. If you're interested its site
is: http://mysolr.redtuna.org/
Do you know what advantages it has over pysolr or solrpy? On the page
On 11/25/2010 10:06 AM, Damien Fontaine wrote:
I have a problem with MoreLikeThis on Solr 1.4.1. I can't put two field
on mlt.fl.
Example : text and title, only text is in interestingTerms
It should work. My guess is that the terms from the title simply don't
make the cut due to mlt.mintf,
11 matches
Mail list logo
