I'm writing a search extension that is needing to write results to an
external cache. So Solr will only return a handful of results to the user,
but it puts all the rest into this cache where the user can do other
operations on the results if they need to. The only thing that needs to go
into thi
That did fix my issue, thanks so much.
--
View this message in context:
http://lucene.472066.n3.nabble.com/java-lang-IllegalArgumentException-when-using-SolrJ-CloudSolrServer-tp4116585p4117279.html
Sent from the Solr - User mailing list archive at Nabble.com.
I'm using Solr 4.5.1 and trying to use the SolrCloud setup. I have Zookeeper
and Solr running on three machines. I have some Java code that does the
following.
SolrServer ss = new
CloudSolrServer("http://localhost:8983/solr/collection1";);
ss.deleteByQuery("*:*");
That gives me the following s
Ah, I see where I went wrong. I didn't define that dynamic field, it was in
the Solr default schema.xml file. I thought that adding a dynamic field
called *_coordinate would basically do the same thing for latitude and
longitudes as adding a dynamic field like *_i does for integers, i.e. index
it
I'm using solrj and attempting to index some latitude and longitudes. My
schema.xml has this dynamicField definition:
When I attempt to update a document like so
doc.setField("job_coordinate","40.7143,-74.006");
I get the following error:
Exception in thread "main"
org.apache.solr.client.solrj.
I completely agree. I would prefer to just rerun the search each time.
However, we are going to be replacing our rdb based search with something
like Solr, and the application currently behaves this way. Our users
understand that the search is essentially a snapshot (and I would guess many
prefe
I am in the process of setting up a search application that allows the user
to view paginated query results. The documents are highly dynamic but I
want the search results to be static, i.e. I don't want the user to click
the next page button, the query reruns, and now he has a different set of
se
