solr4

I have a document with a field called uuids. This field is a list (multivalued) can have up to 100k values per document. I want to search for documents that match uuids that start with "5ff6115e" for instance. I can already do it successfully by using q=uuids:5ff6115e* : http://localhost:8983/solr/test1/select?q=uuids%3A5ff6115e *&rows=1&fl=uuids&wt=json&indent=true However, the resultant document brings me all 100k values for this field. What I want is not only filter the documents whose uuids field start with this value, but also filter the field values returned so that I will only receive

Let me take an example to explain the scenario. Suppose i have data indexed to Solr as : { "id" : "872919092", "filename" : "science_book", "path" : "/local/abc/" } Now i want to modify the data already indexed to Solr with id : 872919092 . I need to change the filename : science_book with filename : history_book and add new attribute topic : mughal to the same indexed data keeping path unchanged. I do not want to pass the path again as there is no change in that and already indexed to Solr. According to the documentation of Solr this is possible. How do i do that using nodejs solr-client

I've gone through the related questions on this site but haven't found a relevant solution. When querying my Solr4 index using an HTTP request of the form &facet=true&facet.field=country The response contains all the different countries along with counts per country. How can I get this information using SolrJ? I have tried the following but it only returns total counts across all countries, not per country: solrQuery.setFacet(true); solrQuery.addFacetField("country"); The following does seem to work, but I do not want to have to explicitly set all the groupings beforehand: solrQuery

I'm having issues generating a UUID using the dataImportHandler in Solr4. Im trying to import from an existing MySQL database. My schema.xml contains: <fields> <field name="uuid" type="uuid" indexed="true" stored="true" required="true" /> <field name="id" type="string" indexed="true" stored="true" required="true"/> <field name="address" type="text_general" indexed="true" stored="true"/> <field name="city" type="text_general" indexed="true" stored="true" /> <field name="county" type="string" indexed="true" stored="true" /> <field name="lat" type="text_general" indexed="true" stored="true" />

I'm using apache solr for the matching functionality of my webapp, and I encountered a problem of this scenario: I got three programmer, the skill field are their skills, "weight" means how well that skill he/she has: { name: "John", skill: [ {name: "java", weight: 90}, {name: "oracle", weight: 90}, {name: "linux", weight: 70} ] }, { name: "Sam", skill: [ {name: "C#", weight: 98}, {name: "java", weight: 75}, {name: "oracle", weight: 70}, {name: "tomcat", weight: 70}, ] }, { name: "Bob", skill: [ {name: "oracle", weight: 90}, {name: "java", weight: 85} ] } and I have a job seeking for

While attempting to upgrade from Solr 4.3.0 to Solr 4.4.0 I ran into this exception: java.lang.IllegalArgumentException: enablePositionIncrements=false is not supported anymore as of Lucene 4.4 as it can create broken token streams which led me to this issue . I need to be able to match queries irrespective of intervening stopwords (which used to work with enablePositionIncrements="true"). For instance: "foo of the bar" would find documents matching "foo bar", "foo of bar", and "foo of the bar". With this option deprecated in 4.4.0 I'm not clear on how to maintain the same functionality. The