It's a bit off-topic, but .. to mention it, because Brian said Graph Database
-- Neo4J uses / can use Lucene .. so, dependent of the usecase this is worth a
look?
On Tuesday, March 19, 2013 at 10:11 PM, Shawn Heisey wrote:
> On 3/19/2013 2:31 PM, Brian Hurt wrote:
> > Which is the problem- yo
On 3/19/2013 2:31 PM, Brian Hurt wrote:
Which is the problem- you might think that 60ms unique key accesses
(what I'm seeing) is more than good enough- and for most use cases,
you'd be right. But it's not unusual for a single web-page hit to
generate many dozens, if not low hundreds, of calls to
: Which is the problem- you might think that 60ms unique key accesses
: (what I'm seeing) is more than good enough- and for most use cases,
: you'd be right. But it's not unusual for a single web-page hit to
: generate many dozens, if not low hundreds, of calls to get document by
: id. At which
while querying (and hence invalidating
caches)?
-- Jack Krupansky
-Original Message-
From: Brian Hurt
Sent: Tuesday, March 19, 2013 4:31 PM
To: solr-user@lucene.apache.org
Subject: Re: Help getting a document by unique ID
On Mon, Mar 18, 2013 at 7:08 PM, Jack Krupansky
wrote:
Hmmm.
On Mon, Mar 18, 2013 at 7:08 PM, Jack Krupansky wrote:
> Hmmm... if query by your unique key field is killing your performance, maybe
> you have some larger problem to address.
This is almost certainly true. I'm well outside the use cases
targeted by Solr/Lucene, and it's a testament to the qual
Can you send us what you're trying? It definitely should not be slow. Do
you have a lot or large stored fields that you're trying to retrieve?
Unless you're doing the transaction log / near-real-time stuff, here's how I'd
get a document by id:
/select?q={!term f=id}
The reason the {!t
ginal Message-
From: Brian Hurt
Sent: Monday, March 18, 2013 6:08 PM
To: solr-user@lucene.apache.org
Subject: Help getting a document by unique ID
So here's the problem I'm trying to solve: in my use case, all my
documents have a unique id associated with them (a string), and I very
of
So here's the problem I'm trying to solve: in my use case, all my
documents have a unique id associated with them (a string), and I very
often need to get them by id. Currently I'm doing a search on id, and
this takes long enough it's killing my performance. Now, it looks
like there is a GET call
