left. the $20 under the tile with the hand prints. thx
On Tuesday, March 13, 2012, jlark wrote:
> Interestingly I'm getting this on other fields now.
>
> I have the field stored="true" />
>
> which is copied to text
>
> and my text field is simply indexed="true" stored="true" />
>
> I
A quick add on to this -- we have over 30 million documents.
I take it that we should be looking @ Distributed Solr?
as in
http://www.lucidimagination.com/content/scaling-lucene-and-solr#d0e344
Thanks.
On Mon, Feb 27, 2012 at 2:33 PM, Memory Makers wrote:
> Many thanks for the respo
ng the indexing to multiple machines, but pointing all to the
> same Solr server, is effectively the same as multi-threading it push
> documents into Solr from wherever as fast as it can handle it. This is
> definitely how many do this.
>
>Erik
>
> On Feb 27, 2012, a
I've been toying with the idea of setting up an experiment to index a large
document set 1+ TB -- any thoughts on an open data set that one could use
for this purpose?
Thanks.
On Mon, Jan 16, 2012 at 5:00 PM, Burton-West, Tom wrote:
> Hello ,
>
> Searching real-time sounds difficult with that am
Hi,
Is there a handy resource on the:
a. performance of: dynamic fields versus static fields
b. other pros-cons?
Thanks.
y a delete
> followed by an insert of a new document with the same primary key). There
> are performance considerations here as well (how to do bulk updates
> quickly, etc.).
>
> Bob
>
>
> On Nov 1, 2011, at 11:47 AM, Memory Makers wrote:
>
> > Greetings guys,
> &g
wrote:
> Other than "it isn't a database"?
>
> If you want a key/value store, use one of those. If you want a full DB
> with transactions, use one of those.
>
> wunder
>
> On Nov 1, 2011, at 8:47 AM, Memory Makers wrote:
>
> > Greetings guys,
&
Greetings guys,
I have been thinking of using Solr as a simple database due to it's
blinding speed -- actually I've used that approach in some projects with
decent success.
Any thoughts on that?
Thanks,
MM.
Eric,
NGrams could you elaborate on that ? -- haven't seen that before.
Thanks.
On Tue, Nov 1, 2011 at 11:06 AM, Erick Erickson wrote:
> NGrams are often used in Solr for this case, but they will also add to
> your index size.
>
> It might be worthwhile to look closely at your user requirements
Greetings,
I am trying to index hashtags from twitter -- so they are tokens that start
with a # symbol and can have any number of alpha numeric characters.
Examples:
1. #jane
2. #Jane
3. #Jane!
At a high level I'd like to be able to:
1. differentiate between say #jane and #jane!
2. differentiate
Well https://github.com/evolvingweb/ajax-solr is fairly decent for that --
haven't used it in a while but that is a minimalist client -- however I find
it hard to customize.
MM.
On Tue, Oct 25, 2011 at 8:34 AM, Fred Zimmerman wrote:
> what about something that's a bit less discovery-oriented? fo
gt;
> With only a few minutes (given the prerequisites already installed) to give
> it a try, might as well give it a go :) The Blacklight community is very
> helpful too, so ask on their e-mail list for assistance, or tap into the
> #blacklight IRC channel.
>
>Erik
>
>
r like this is determined by the
> programming language and frameworks used. Blacklight is "opinionated" (as
> any other concrete implementation would be) in this regard. If it fits your
> tastes, it's a great technology to use.
>
>Erik
>
>
> On Oct 24,
Greetings guys,
Is there a good front end application / interface for solr?
Features I'm looking for are:
configure query interface (using non programatic features)
configure pagination
configure bookmarking of results
export results of a query to a csv or other format (JSON, etc.)
Is
Thanks,
?q.alt=*:* worked for me -- how do I make sure that the standard query
parser is configured.
Thanks.
MM.
On Mon, Oct 24, 2011 at 2:47 AM, Ahmet Arslan wrote:
> > 2. If send solr the following query:
> > q=*:*
> >
> > I get nothing just:
> > > name="response" numFound="0" star
Hi,
I've spent quite some time reading up on the query format and can't seem to
solve this problem:
1. If send solr the following query:
q={!lucene}profile_description:*
I get what I would expect.
2. If send solr the following query:
q=*:*
I get nothing just:
Would appreciate some
16 matches
Mail list logo
