The downloads definitely include an -example- configuration. Look under
example/solr/conf
Erik
On Jan 21, 2012, at 10:51, remi tassing tassingr...@gmail.com wrote:
In the Solr-3.5 zip file I downloaded there was no solrconfig.xml
On Friday, January 20, 2012, Erik Hatcher erik.hatc
On Jan 20, 2012, at 13:23 , remi tassing wrote:
The tutorial works with Solr-3.4.0!
It works for 3.5 too... via Jetty as prescribed by the tutorial. No?
Should the tutorial be updated with newer versions?
Have you tried the instructions here?
said you would fix 3.6?
Steve
-Original Message-
From: Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Friday, January 20, 2012 4:23 PM
To: solr-user@lucene.apache.org
Subject: Re: Just can't get Solritas to work, help!
On Jan 20, 2012, at 13:23 , remi tassing wrote
/browse is defined solrconfig.xml. Its details need adjusting for datasets
other than the example data that ships with Solr. Templates may also need
adjusting, but does handle arbitrary facet fields automatically.
Erik
On Jan 19, 2012, at 7:56, remi tassing tassingr...@gmail.com wrote:
Perhaps this the known issue with the 3.5 example schema being used in Tomcat
and the VelocityResponseWriter issue? I'm on my mobile now so don't have easy
access to a pointer with details but check the archives if this seems to be the
issue on how to resolve it.
Erik
On Jan 17, 2012,
Because you're using the lucene query parser which doesn't use qf. Add
defType=dismax to get the effect you want.
Erik
On Jan 11, 2012, at 12:22, Matthias Müller mm4...@googlemail.com wrote:
Hi,
when I request a query to solr with
/solr/select?q=querydebugQuery=trueqf=title
I get no
Mike -
Indeed users won't be able to *search* for things removed by the stop filter at
index time (the terms literally aren't in the index then). But be careful with
the stored value. Analysis does not affect stored content.
Are you anonymizing before sending to Solr (if so, why stop-word
Also note that an EmbeddedSolrServer is for a specific core, not for all cores
(and thus solr.xml is not used). My hunch is that you need to point to the
core's home directory, not to the parent of solr.xml.
Erik
On Jan 6, 2012, at 03:06 , Sven Maurmann wrote:
Hi,
from your
On Jan 6, 2012, at 10:46 , Yury Kats wrote:
On 1/6/2012 10:19 AM, Phillip Rhodes wrote:
2012/1/6 Yury Kats yuryk...@yahoo.com:
Have you tried passing core name (collection1) to the c'tor, instead
of the empty string?
Yep, but that gives the same error (with the core name appended) such
I'd recommend what Andy said, but if all you're interested in is a single term
combined, you can do facet.query=product:computer OR tag:computer and you'll
get the merged count.
Erik
On Jan 4, 2012, at 07:51 , Andrew Ingram wrote:
Hi Marc,
I'd probably have another field called
You're using a string field type, I imagine. Use a numeric field type instead.
wc-search.xml? That's not a solr config file; must be something specific to
your app.
Erik
On Jan 4, 2012, at 08:40 , umaswayam wrote:
Hi,
We want to sort our records based on some sequence which is
As I understand it, the document and filter caches add value *intra* request
such that it keeps additional work (like fetching stored fields from disk more
than once) from occurring.
Erik
On Jan 3, 2012, at 16:26 , Jason Rutherglen wrote:
*Laugh*
I stand by what Mark said:
Aleksander -
Looks like you've experienced the issue described with fixes here:
http://www.lucidimagination.com/search/document/48b9e75fe68be4b7
Erik
On Dec 29, 2011, at 08:40 , Aleksander Akerø wrote:
Hi!
So I've decided try out Solr 3.5.0.
What I have done this far is basicly
it several hours a day in XWiki.
It's fast and easy but its testing ability is simply... unpredictable.
I did not mean to say it is not documented enough but that it could be
reformulated as a tutorial wiki page instead of an example software.
paul
Le 9 déc. 2011 à 23:17, Erik Hatcher
No, multiselect is not wired into /browse. That'd be a nice addition though.
Erik
On Dec 8, 2011, at 16:30 , PJ Shimmer wrote:
Greetings,
I see that we can query multiple facets for a search with a syntax like
fq=grade:A OR grade:B. However, I only know how to do this by
constraints?
Erik
On Dec 9, 2011, at 10:15 , PJ Shimmer wrote:
Thanks Erik.
Is there any available UI that supports multi-select faceting?
From: Erik Hatcher erik.hatc...@gmail.com
To: solr-user@lucene.apache.org
Sent: Friday, December 9, 2011 9
My bad.
To clarify the issue here... the problem manifests itself only on Solr 3.5
specifically when the example configuration is copied somewhere else (losing
the relative path nature to the lib references). Generally this happens when
folks want to deploy into Tomcat. In Solr 3.5, the
So I thought that Solr having a decent HTML search UI out of the box was a good
idea. I still do. But it's been a bit of a pain to maintain (originally it
was a contrib module, then core, then folks didn't want it as a core
dependency, and now it is back as a contrib), and the UI has
The one trick that can be done with 3.x is something like this (try this URL on
the example app with the example data indexed):
http://localhost:8983/solr/browse?v.template.doc=%23set%28$cents=$doc.getFieldValue%28%27price%27%29*100%29%20$cents%20cents
Un-urlencoded, this is saying to make
making it an example or tutorial?
paul
PS: I'll note that I would prefer a candid jsp equivalent (I still do) but
it was never available (one day I'll make one).
Le 9 déc. 2011 à 22:30, Erik Hatcher a écrit :
So I thought that Solr having a decent HTML search UI out of the box
s/choice templating languages/template language choices/
Also, meant to include
* http://today.java.net/pub/a/today/2003/12/16/velocity.html
On Dec 9, 2011, at 17:07 , Erik Hatcher wrote:
Paul -
Thanks for your feedback.
As for JSP... the problem with JSP's is that they must be inside
First, could you tell us more about your use case? Why do you want to change
the response code? HTTP 307 = Temporary redirect - where are you going to
redirect? Sounds like something best handled outside of Solr.
If you went down the route of creating your own custom response writer,
asked if it was somehow possible to leave that
functionality in the search engine.
thanks again
Inizio: Erik Hatcher [erik.hatc...@gmail.com]
Inviato: mercoledì 7 dicembre 2011 14.12
Fine: solr-user@lucene.apache.org
Oggetto: Re: Solr response writer
creating the index? (may not be the
right place, but is something like this possible?)
On Tue, Dec 6, 2011 at 5:13 PM, Erik Hatcher erik.hatc...@gmail.com wrote:
Right. Not sure what to advise you. We have worked on this problem with
our LucidWorks platform and have some tools available to do
What you can do is index the redirect documents along with the associated
words, and let Solr do the stemming. Maybe add a document type field and if
you get a match on a redirect document type, your web service can do what it
needs to do from there.
Erik
On Dec 7, 2011, at 10:43
On Dec 7, 2011, at 13:20 , Shawn Heisey wrote:
On 12/6/2011 2:06 PM, Erik Hatcher wrote:
I think the best thing that you could do here would be to lock in a version
of Lucene (all the Lucene libraries) that you use with SolrCloud. Certainly
not out of the realm of possibilities of some
Within one request, it isn't possible to highlight the same field twice
differently (what's the use case here?), but you could either make multiple
requests or copyField to have two stored copies that could be highlighted
separately in a single request.
Erik
On Dec 6, 2011, at 06:01 ,
Mark -
So you want the *server* to be started programmatically? You could use
Jetty's API to do this... or fork a JVM.
As for client-side SolrJ, you can pass an HttpClient to CommonsHttpSolrServer's
constructor to customize how the HTTP connection is configured.
EmbeddedSolrServer - no, it
As for XML overloading Solr... certainly it will add processing time to the
situation as well as additional memory requirements. At worst it'd require
more RAM and slow things down, but all depends on scale of ingestion rate and
size of the documents whether it'd be prohibitive.
Erik
Jamie -
I think the best thing that you could do here would be to lock in a version of
Lucene (all the Lucene libraries) that you use with SolrCloud. Certainly not
out of the realm of possibilities of some upcoming SolrCloud capability that
requires some upgrading of Lucene though, but you
that are present when I build locally?
On Tue, Dec 6, 2011 at 4:06 PM, Erik Hatcher erik.hatc...@gmail.com wrote:
Jamie -
I think the best thing that you could do here would be to lock in a version
of Lucene (all the Lucene libraries) that you use with SolrCloud. Certainly
not out
PM, Erik Hatcher erik.hatc...@gmail.com wrote:
Oh geez... no... I didn't mean 3.x JARs... I meant the trunk/4.0 ones that
are there now.
Erik
On Dec 6, 2011, at 16:22 , Jamie Johnson wrote:
So if I wanted to used lucene index 3.5 with SolrCloud I should be
able to just move
Michael -
I was following your discussion on the MCF list too as well.
What kind of information do you want to extract from the HTML pages? The UIMA
thing would be fairly heavy weight. The simplest thing on the Solr-side of the
equation would be to write an UpdateProcessor(Factory) and
On Nov 23, 2011, at 09:56 , Ahmet Arslan wrote:
is this is the trunk of solr 4.0 ,
can't i implement in solr 3.1 .?
Author of the patch would know answer to this. But why not use trunk?
I spent a fair bit of time yesterday on making a 3.x compatible patch but have
not completed that
not very much aware of it , can i use lucene query parser with
solr and make this fuzzy search possible?
Erik Hatcher-4 wrote
Sure... if you're using the lucene query parser and put a ~ after every
term in the query :)
But that would mean that either the users or your application do
Meghana -
There's currently no facility in Solr to return results for suggestions
automatically. You'll have to code this into your client to make another
request to Solr for the suggestions returned from the first request.
Erik
On Nov 23, 2011, at 07:58 , meghana wrote:
Hi,
I
=*:* and not
specify q if no user provided terms.
Take it easy,
Jeff
On Nov 22, 2011, at 11:53 AM, Erik Hatcher wrote:
I think you're using dismax, not edismax. edismax will take q=*:* just fine
as it handles all Lucene syntax queries also. dismax does not.
So, if you're using dismax
.
Thanks,
Jeff
On Nov 22, 2011, at 7:06 AM, Erik Hatcher wrote:
If all you're doing is filtering (browsing by facets perhaps), it's
perfectly fine to have q=*:*. MatchAllDocsQuery is fast (and would be
cached anyway), so use *:* as appropriate without worries.
Erik
On Nov 22
provides the fuzzy
search by applying tilde(~) symbol at the end of search with like
delll~0.8
can we apply such fuzzy logic in solr in any way?
Thanks
Meghana
Erik Hatcher-4 wrote
Meghana -
There's currently no facility in Solr to return results for suggestions
automatically. You'll
The surround query parser is fully wired into Solr trunk/4.0, if that helps.
See http://wiki.apache.org/solr/SurroundQueryParser and the JIRA issue linked
there in case you want to patch it into a different version.
Erik
On Jan 21, 2011, at 02:24 , Ahson Iqbal wrote:
Hi All
I
If all you're doing is filtering (browsing by facets perhaps), it's perfectly
fine to have q=*:*. MatchAllDocsQuery is fast (and would be cached anyway), so
use *:* as appropriate without worries.
Erik
On Nov 22, 2011, at 07:18 , pravesh wrote:
Usually,
Use the 'q' parameter to
? I don't see in the code (looking at my trunk checkout) where
there's any *:* used in the SolrJ library. Can you provide some details on how
you used SolrJ? It'd be good to track this down as that seems like a bug to me.
Erik
Thanks,
Jeff
On Nov 22, 2011, at 7:06 AM, Erik
. Again, this is stock Solr 3.4.0, running the Apache war
under Tomcat 6.
Jeff
On Nov 22, 2011, at 8:05 AM, Erik Hatcher wrote:
On Nov 22, 2011, at 09:55 , Jeff Schmidt wrote:
When using [e]dismax, does configuring q.alt=*:* and not specifying q
affect the performance/caching in any
Ben,
Not quite sure how to interpret what you're asking here. Are you speaking of
the /browse view? If so, you can tweak the templates under conf/velocity to
make links out of things.
But generally, it's the end application that would take the results from Solr
and render links as
On Nov 17, 2011, at 10:38 , Ari King wrote:
I'm considering migrating from Hibernate Search to Solr, but in order
to make that decision, I'd appreciate insight on the following:
1. How difficult is getting Solr up and running? With Hibernate I had
to annotate a few classes and setup a
Yes... use key instead of name in your example below :)
http://wiki.apache.org/solr/SimpleFacetParameters#key_:_Changing_the_output_key
On Nov 15, 2011, at 15:12 , Robert Stewart wrote:
Is there any way to give a name to a facet query, so you can pick
facet values from results using
Set the cache lifetime high, like it says.
Questions - why use the XSLT response writer? What are you transforming the
response into and digesting it with?
Erik
On Nov 14, 2011, at 09:31 , vrpar...@gmail.com wrote:
Hello All,
i am using xslt to transform solr xml response, when
SolrDispatchFilter is where HTTP headers get set, and currently there isn't
really any flexibility on Solr response writers being able to affect HTTP
headers. (note here that it isn't necessarily true that Solr requests are
happening over HTTP, so that's not always a given)
You could come up
Does pivot faceting solve this? At first glance, seems like the same thing,
but I haven't grokked fully the followup e-mails on this thread, sorry.
Erik
On Nov 7, 2011, at 13:03 , Steve Fatula wrote:
So, I have a bunch of products indexed in Solr. Each product may exist in any
-safe way to do
that.
Erik
Erik Hatcher wrote:
It's certainly quite possible with Lucene/Solr. But you have to index the
field to accommodate it. If you literally want an exact match query, use
the string field type and then issue a term query. q=field:value
It's certainly quite possible with Lucene/Solr. But you have to index the
field to accommodate it. If you literally want an exact match query, use the
string field type and then issue a term query. q=field:value will work in
simple cases (where the value has no spaces or colons, or other
Be aware that even /select could have some harmful effects, see
https://issues.apache.org/jira/browse/SOLR-2854 (addressed on trunk).
Even disregarding that issue, /select is a potential gateway to any request
handler defined via /select?qt=/req_handler
Again, in general it's not a good idea
there is actually an interesting trick here using facet.query (which would only
entail a single filter cache entry):
http://127.0.0.1:/solr/collection1/select?q={!tag=main}country:Spainfacet=onfacet.query={!ex=main
key=total}*:*
[my test data has a country field]
Using facet
Paul (*bows* to the NINES!) -
If you literally want Citations always at the bottom regardless of other
relevancy, then perhaps consider indexing boolean top_sort as true for
everything Citations and false otherwise, then use sort=top_sort asc,score
desc (or do you need to desc top_sort? true
my query had no effect, though. There's
obviously something I don't get about queries.
On Mon, Oct 31, 2011 at 10:08 AM, Erik Hatcher erik.hatc...@gmail.com wrote:
Paul (*bows* to the NINES!) -
If you literally want Citations always at the bottom regardless of other
relevancy, then perhaps
I would personally implement this in the app tier, above Solr.
One way to do it using Solr to match keywords to URLs is to index special
redirect documents with the keywords in the search field (either in the main
index, or in a separate core index).
But there is nothing magically built
Robert -
Can you give us a concrete input text, the field type definition, and the
query(/ies) that you'd expect to match? The devil is in the details.
Just because analysis.jsp _only_ means that an index and query time output
token for the given text was equal. But in the real world of
You've got two q parameters. For filtering on facet values, you're better off
using fq parameters instead (and if there is no other query, set q=*:*, or if
using dismax set q.alt=*:* and leave q empty/unspecified). Only one q
parameter is used, but any number of fq parameters may be
That URL has several oddities to it... empty fq and qt parameters. Try simply
?q=*:*facet=onfacet.field=Categoryfacet.field=Warehouse and see if that
helps.
Erik
On Oct 26, 2011, at 07:08 , Tiernan OToole wrote:
Good morning all.
I am currently indexing about 11 million records,
Maybe a case sensitive issue? defType it should be.
Erik
On Oct 26, 2011, at 16:03, jyn7 jyotsna.namb...@gmail.com wrote:
Hi,
I am using a dismax search and limiting the query parameters using qf:
/solrbgp/select/?facet=trueqf=memnumq=%229065%22deftype=dismaxstart=0rows=10
My
Blacklight - http://projectblacklight.org/
It's a full featured application fronting Solr. It's Ruby on Rails based, and
powers many library front-ends but is becoming much more general purpose for
other domains. See examples here:
I'm not following exactly what you're looking for here, but sounds like you
want to facet on name... facet=onfacet.field=name1
and then to filter on a selected one, you can use fq=name:name1
Erik
On Oct 24, 2011, at 20:18 , solrdude wrote:
Hi,
I am implementing an solr solution
at 5:49 AM, Erik Hatcher erik.hatc...@gmail.comwrote:
Blacklight - http://projectblacklight.org/
It's a full featured application fronting Solr. It's Ruby on Rails based,
and powers many library front-ends but is becoming much more general purpose
for other domains. See examples here
On Oct 25, 2011, at 07:24 , Robert Stewart wrote:
It is really not very difficult to build a decent web front-end to SOLR using
one of the available client libraries
Or even just not using any client library at all (other than an HTTP library).
I've done a bit of
Also, those boosts on your qf and pf are a red flag and may be causing you
issues. Look at explains provided with debugQuery=true output to see how your
field/phrase boosts are working in conjunction with your date boosting attempts.
Erik
On Oct 23, 2011, at 17:15 , Erick Erickson
, 2011 at 7:40 AM, Erik Hatcher erik.hatc...@gmail.comwrote:
On Oct 25, 2011, at 07:24 , Robert Stewart wrote:
It is really not very difficult to build a decent web front-end to SOLR
using one of the available client libraries
Or even just not using any client library at all (other than
Sure. Just facet on a tokenized field of the tweet text. You'll want to tune
the analysis configuration to suit your desires, but no problem getting counts
back using facet=onfacet.field=tweet_text kinda thing.
Erik
On Oct 24, 2011, at 13:14 , Rohit wrote:
I have saved tweets
On Oct 23, 2011, at 19:34 , Fred Zimmerman wrote:
it seems from my limited experience thus far that as new data types are
added, schema.xml will tend to become bloated with many different field and
fieldtype definitions. Is this a problem in real life, and if so, what
strategies are used to
. Certainly there is much room for improvement in most things.
Erik
On Sun, Oct 23, 2011 at 6:38 PM, Erik Hatcher erik.hatc...@gmail.comwrote:
On Oct 23, 2011, at 19:34 , Fred Zimmerman wrote:
it seems from my limited experience thus far that as new data types are
added, schema.xml
It's certainly possible to develop a Solr admin (or search) UI using Spring
MVC. But we won't be adding any Spring MVC to Solr itself; I'm not sure if you
are proposing that Solr refactor the UI with that technology or not.
Erik
On Oct 20, 2011, at 06:26 , nagarjuna wrote:
Thank u
On Oct 3, 2011, at 23:32 , jwang wrote:
Solritas is a nice search UI integrated with Solr with many features we could
use. However we do not want to build our UI into our Solr instance. We will
have a front-end web app interfacing with Solr. Is there an easy way to
deploy Solritas as a
Just a fact of life with the Lucene query parser. You'll need to escape the +
with a backslash for this to work.
Erik
On Sep 29, 2011, at 12:31 , Shawn Heisey wrote:
The following query is failing:
((Google +))
This is ultimately reduced to 'google' by my analysis chain, but
Well ... DIH can.
And update processors can.
And of course client-side indexers.
But yeah... elbow grease required.
Erik
On Sep 25, 2011, at 16:32, Erick Erickson erickerick...@gmail.com wrote:
Not that I know of...
On Sun, Sep 25, 2011 at 11:15 AM, Jithin jithin1...@gmail.com
Hey, the more hammering on trunk the better!
On Sep 24, 2011, at 13:31 , Erick Erickson wrote:
Hmmm, why are you doing this? Why not use the latest
successful trunk build?
You can get a series of built artifacts at:
https://builds.apache.org//view/S-Z/view/Solr/job/Solr-trunk/
but I'm
conf/velocity by default. See Solr's example configuration.
Erik
On Sep 23, 2011, at 12:37, Fred Zimmerman w...@nimblebooks.com wrote:
ok, answered my own question, found velocity rw in solrconfig.xml. next
question:
where does velocity look for its templates?
Why create a custom facet component for this?
Simply add lines like this to your request handler(s):
str name=facet.fieldmanu_exact/str
either in defaults or appends sections.
Erik
On Sep 21, 2011, at 14:00 , Ravi Bulusu wrote:
Hi All,
I'm trying to write a custom
.
Great wok Solr team, and special thanks to Erik Hatcher.
*Pranav Prakash*
temet nosce
Twitter http://twitter.com/pranavprakash | Blog http://blog.myblive.com |
Google http://www.google.com/profiles/pranny
On Mon, Sep 19, 2011 at 15:54, Pranav Prakash pra...@gmail.com wrote:
Just
This doesn't seem like a vulnerability at all. What bad effect are you
implying here?
First of all, in those examples the XML that you injected is encoded in the
response, it's not actually part of the XML DOM.
And secondly, if you don't want the client to control hl.simple.pre/post you
can
On Sep 18, 2011, at 19:43 , Michael Sokolov wrote:
On 9/15/2011 8:30 PM, Scott Smith wrote:
2. Assuming that the answer to 1 is correct, then is there an easy
way to take a lucene query (with nested Boolean queries, filter queries,
etc.) and generate a SOLR query string with q and
On Sep 18, 2011, at 21:52 , scorpking wrote:
Hi Erik Hatcher-4
I tried index from your url. But i have a problem. In your case, you knew a
files absolute path (Dir.new(/Users/erikhatcher/apache-solr-3.3.0/docs).
So you can indexed it. In my case, i don't know a files absolute path. I
only
Reindexing is not necessary. Drop in 3.4 and go.
For this sort of scenario, it's easy enough to try using a copy of your
SOLR_HOME directory with an instance of the newest release of Solr. If the
release notes don't say a reindex is necessary, then it's not, but always a
good idea to try
From Solr's example schema.xml: omitTermFreqAndPositions attribute introduced,
true by default except for text fields (meaning TextField's)
And term vectors most definitely are false by default. Also from the example
schema.xml: termVectors: [false] set to true to store the term vector for a
Xue-Feng - 你好 －
You'll need to give us some more specifics. *:* will always work, but
searching on other strings is entirely dependent on your configuration and the
exact query. For us to help, you'll need to share your full query
(debugQuery=true helps here) and the related
It's for weblogic. Deleting it won't cause any issues (unless you're deploying
to weblogic, but you're not). give it a try.
On Sep 17, 2011, at 08:52 , Xue-Feng Yang wrote:
I have solr deployed in Glassfish 3.1.1. It has the error messages in the
following order at the starting up time.
Maybe this quick script will get you running?
http://www.lucidimagination.com/blog/2011/08/31/indexing-rich-files-into-solr-quickly-and-easily/
On Sep 15, 2011, at 00:44 , scorpking wrote:
Hi Erick Erickson,
Now, we have many files format(doc, ppt, pdf, ...), File's purpose serve to
On Sep 11, 2011, at 23:24 , William Bell wrote:
I am using 3.3 SOLR. I tried passing in -Denable.master=true and
-Denable.slave=true on the Slave machine.
Then I changed solrconfig.xml to reference each as per:
http://www.lucidimagination.com/blog/2011/09/12/learn-lucene/ - pasted below too
Hi everyone... I'm not usually much on advertising/hyping events where I speak
and teach, but I'm really interested in drumming up a solid attendance for our
Lucene training that I'll be teaching at Lucene EuroCon
If the only thing you're doing is indexing file content, then you can bypass
using the Data Import Handler altogether and use the ExtractingRequestHandler
(aka Solr Cell). And you can feed in a file from a URL using the stream.url
capability, like the stream.file example here:
How are you doing fielded search currently? End users using the lucene query
parser? Or using dismax/qf?
I'm just curious to drill into your needs here exactly in terms of
request/response and whether a simple application layer handling of the alias
need would suffice or this is something
It's not necessarily a bad idea... as long as you secure it properly such that
user requests cannot hit Solr, only requests from your application can do so.
Eventually, perhaps, scale would be an issue and you'd want/need to separate
the tiers, but as long as you've got security and scalability
The $page object is an instance of PageTool... which currently is constructed
this way:
public PageTool(SolrQueryRequest request, SolrQueryResponse response)
It doesn't work, currently, with the grouped stuff. It's just some simple math
to get the page size, etc. You can pretty easily
If your files are under Solr's conf/ directory, you can get them served up
using the ShowFileRequestHandler (see how the /browse serves up CSS and the
autocomplete JQuery library). But otherwise, Solritas doesn't give you any
capability to serve up files and the browsers aren't too happy about
There is no scheduling built into Solr. But many, including the search system
deployed on our (Lucid's) website, is powered by cron jobs kicking off indexers
of various varieties all the time.
Look into your operating systems scheduling capabilities and leverage those, is
my advice. Cron is
My educated guess is that you're using Java for your indexer, and you're (or
something below is) doing a toString on a Java object. You're sending over a
Java object address, not the string itself. A simple change to your indexer
should fix this.
Erik
On Aug 30, 2011, at 08:42 ,
I haven't followed the details, but what I'm guessing you want here is Lucene's
FieldCache. Perhaps something along the lines of how faceting uses it (in
SimpleFacets.java) -
FieldCache.DocTermsIndex si =
FieldCache.DEFAULT.getTermsIndex(searcher.getIndexReader(), fieldName);
Erik
?
On Mon, Aug 29, 2011 at 10:51 AM, Erik Hatcher erik.hatc...@gmail.com wrote:
I haven't followed the details, but what I'm guessing you want here is
Lucene's FieldCache. Perhaps something along the lines of how faceting uses
it (in SimpleFacets.java) -
FieldCache.DocTermsIndex si
Based on the date, this was a LucidWorks Enterprise distribution that predated
the addition of pseudo-fields to Solr for returning function values like that.
We have another release of LWE coming out, oh I dunno exactly, in a month or
so? It'll have the latest greatest Solr 4.0 (which is
search engine
doing the same query same machine 0.7 / 0.8 secs without cache . I am
confident we can do better in solr but couldnt find the way at the moment.
thanks for helping..
On Sat, Aug 27, 2011 at 2:46 AM, Erik Hatcher erik.hatc...@gmail.comwrote:
On Aug 26, 2011, at 17:49
looking for all suggestions.
On Sat, Aug 27, 2011 at 3:37 PM, Erik Hatcher erik.hatc...@gmail.comwrote:
Please confirm is this is caused by grouping. Turn grouping off, what's
query time like?
On Aug 27, 2011, at 07:27 , Lord Khan Han wrote:
On the other hand We couldnt use the cache
Is the field stored? Do you see it on documents when you do a q=*:* search?
How is that field defined and populated? (exact config/code needed here)
Erik
On Aug 25, 2011, at 23:07 , deniz wrote:
hi all...
i have added a new field to index... but now when i check solr admin, i see
501 - 600 of 1610 matches
Mail list logo
