I finished to write FacetConverter, but I have a question:
How do I config facet.threads parameter in Json Facet Api?
I didn't find right syntax in the Confluence page.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-SOLR-version-facets-perfomance-regression-tp
I finished to write FacetConverter, but I have some questions:
1) How do I config facet.threads parameter in Json Facet Api?
2) How do I add facet.pivot to query? For example, I need
*q=*:*&facet=true&facet.pivot=A,B*
and I tried to write something like this:
What I meant is that :
"Components
If you define components, the default components (see above) will not be
executed, and first-components and last-components are disallowed:"
Anyway it is documented in the Confluence page.
If you don't override the default components, json facets will be there.
And still I have a question:
Is there some convertor from the legacy api to the new API?
Or a search component that converts from legacy api to json facet api?
I explained why I need it in my first post.
Thank you
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-SOL
Alessandro, it helped! Thank you.
But I asked which changes do we do in configuration and I think these things
must be documented in the reference guide.
About your question, first of all I don't override default componets. Second
of all, I add my own components and for many reasons (For example, I
The reason must to be found in the default list of components :
protected List getDefaultComponents()
{
ArrayList names = new ArrayList<>(8);
names.add( QueryComponent.COMPONENT_NAME );
names.add( FacetComponent.COMPONENT_NAME );
*names.add( FacetModule.COMPONENT_NAME );*
nam
I noticed if I don't write list of components in request handler it works
fine, but if I add something like
query
facet
Facets don't work...
How can you explian it?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-SOLR-version-facets-perfomance-regression-tp431
Tom, I already tried this syntax (and many another different syntax). It
still doesn't work. Are you sure that no need to change facet name in
request handler to something else?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-SOLR-version-facets-perfomance-regression
On Tue, Jan 31, 2017 at 5:49 AM, SOLR4189 wrote:
> But I can't run Json Facet API. I checked on SOLR-5.4.1.
> If I write:
> localhost:9001/solr/Test1_shard1_replica1/myHandler/q=*:*&rows=5&fl=*&wt=json&facet=true&facet.field=someField
> It works fine. But if I write:
> localhost:9001/solr/Test1_sh
But I can't run Json Facet API. I checked on SOLR-5.4.1.
If I write:
localhost:9001/solr/Test1_shard1_replica1/myHandler/q=*:*&rows=5&fl=*&wt=json&facet=true&facet.field=someField
It works fine. But if I write:
localhost:9001/solr/Test1_shard1_replica1/myHandler/q=*:*&rows=5&fl=*&wt=json&json.facet
You should not give up, starting from 5.5 uif should be there helping and
starting from 6.1 term enum is fixed as well.
There is still the logic of forcing a facet approach depending on your
config and request parameters [1].
It is not expected you don't solve your problem with docValues either ..
After failing with SOLR-5.4.1, we checked SOLR-5.5.2 also.
Most of our facet fields are multivalued.
I see that Json Facet API is experimental API and I can't find how to use it
(I am not speaking about syntax, I need to know how to use it from the point
of view of configurations and jars).
I came
After failining SOLR-5.4.1, we checked SOLR-5.5.2 also.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-SOLR-version-facets-perfomance-regression-tp4315027p4317804.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi,
Reading in here : https://issues.apache.org/jira/browse/SOLR-8466
It seems that uif has been introduced in Solr 5.5 ( you were using 5.4.1 ,
were't you?)
Furthermore, I would recommend to check if your field is/isn't multi-valued
( that could affect as well)
It is weird you don't get any benefi
Method uif: we used it also but it didn't help
Cardinality: high
Field Type: string, tdate
DocValued: yes, for all facet fields
Facet Method: fc (but tried fcs and enum)
Facet Params:
1. Mincount = 1
2. Limit = 11
3. Threads = -1
4. Query (on tdate field for each query)
My question: if Jso
Which kind of field are you faceting on ?
Cardinality ?
Field Type ?
Doc Valued ?
Which facet algorithm are you using ?
Which facet parameters ?
Cheers
--
View this message in context:
http://lucene.472066.n3.nabble.com/Upgrade-SOLR-version-facets-perfomance-regression-tp4315027p4317513.html
S
Are you using docvalues ? Try that it might help.
Bill Bell
Sent from mobile
> On Jan 26, 2017, at 10:38 AM, Bhawna Asnani wrote:
>
> Hi,
> I am experiencing a similar issue. We have tried method uif but that didn't
> help much. There is still some performance degradation.
> Perhaps some under
Hi,
I am experiencing a similar issue. We have tried method uif but that didn't
help much. There is still some performance degradation.
Perhaps some underlying changes in the lucene version its using.
Will switching to JSON facet API help in this case? We have 5 nodes/single
shard in our productio
Hi Solr,
I admit the issue you mentioned has not been transparently solved, and
indeed you would need to explicitly use the method=uif to get 4.10.1
behavior.
This is valid if you were using fc/fcs approaches with high cardinality
fields.
In the case you facet method is enum ( Term Enumeration),
19 matches
Mail list logo
