I may have provided too much background story for my question. What I am
trying to do at the core here, is an exact match on a single field. I do
this programmatically by reading the field value from the facet query and
setting it equal to the field name for a subsequent search.
if this is a
Shoot I just noticed the error in my original post which would certainly
cause confusion.
Instead of
query.addFacetField(fq);
I meant to write
query.setParam(fq, fg);
Sorry.
--
View this message in context:
I am trying to do SQL like aggregation (GROUP BY) with solr faceting. So I
use string fields for faceting - to try to get an exact match. However, it
seems like to run a facet query I have to surround the value with double
quotes. That poses issues when the field value is
green bath towels
-or-
That's a good suggestion, I hadn't checked that log file. What I found that
works, is hitting these methods on the SolrQuery object:
query.setGetFieldStatistics(true);
query.setParam(stats.field, MyStatsFieldName);
query.setParam(stats.facet, MyFacetFieldName);
Now I see the stats in the
Hi. I have a query that works just fine in the browser. It rolls up documents
by the facet field and gives me stats on the stats field:
http://localhost:8983/solr/corename/select?q=*:*stats=onstats.field=Spendstats.facet=Supplier
Posting this works just fine. However I cannot get stats from
Just looking for confirmation that the currency field is not supported for
stats. When I use a currency field as the stats.field I get his error:
http://localhost:8983/solr/corename/select?q=*:*stats=onstats.field=SpendAsCurrencystats.facet=Supplier
Field type
I need to index documents from a csv file that will have 1000s of rows and
100+ columns. To help the user loading the file I must return useful errors
when indexing fails (schema violations). I'm using SolrJ to read the files
line by line, build the document, and index/commit. This approach allows
Thank you. That's a useful link. Maybe not quite what I'm looking for, as it
appears to do with bulk loads of docs - returning an error for each bad doc.
My question is more about getting all the errors for a single doc. I'm
probably taking a performance hit by adding docs one at a time. I haven't
101 - 108 of 108 matches
Mail list logo
