SON facets have support for specifying the number of threads.
> > In the above request, the range facet is computed over 2 years with a gap
> > of 1 hour. By reducing the number of buckets, computation should become
> > much faster
> >
> > Regards,
> > Munendra S N
> >
Hi,
Currently, JSON facets have support for specifying the number of threads.
In the above request, the range facet is computed over 2 years with a gap
of 1 hour. By reducing the number of buckets, computation should become
much faster
Regards,
Munendra S N
On Thu, Dec 3, 2020 at 1:52 PM
add-distinct is similar to add but does contains check before adding the
value. In general, performance overhead should be minimal
Regards,
Munendra S N
On Fri, Oct 30, 2020 at 7:29 PM Srinivas Kashyap
wrote:
> Thanks Munendra, this will really help me. Are there any performance
> ov
Srinivas,
For atomic updates, you could use add-distinct operation to avoid
duplicates -
https://lucene.apache.org/solr/guide/8_6/updating-parts-of-documents.html
This operation is available from Solr 7.3
Regards,
Munendra S N
On Thu, Oct 29, 2020 at 10:27 PM Walter Underwood
wrote:
> Si
b796063ffdcef08047/solr/core/src/java/org/apache/solr/response/transform/ChildDocTransformer.java#L201-L209
but
not sure
Regards,
Munendra S N
On Sun, Aug 23, 2020 at 7:53 PM Alexandre Rafalovitch
wrote:
> Thank you Nunedra,
>
> That was very helpful. I am looking forward to that docum
olrInputDocument child1 = new SolrInputDocument();
>
> parent1.addField("sometag", Arrays.asList(child1));
> child1.addField("id", "c1");
> child1.addField("name", "child1");
> child1.addField("class", "foo.bar.child1"
Currently, Doc transformers are not supported while exporting the results.
The document covers the field requirements for the export handler. I hope
this helps.
https://lucene.apache.org/solr/guide/8_5/exporting-result-sets.html#field-requirements
Regards,
Munendra S N
On Wed, Jun 17, 2020 at
While checking this, I encountered a bug in master. Since you have
mentioned that it works in Solr 8, the bug might be unrelated to your issue.
I have raised a ticket to track this
https://issues.apache.org/jira/browse/SOLR-14550 to track the bug
Regards,
Munendra S N
On Mon, Jun 8, 2020 at 9
his
> { "responseHeader":{ "status":0, "QTime":1, "params":{
> "q":"author:\"William
> Shakespeare\"", "fq":"{!collapse field=title}", "expand": "true", "_":
> "1
o not get error . The strange thing is that I get exactly the same
> response with fq={!collapse field=title} versus fq={!collapse
> field=title}&expand=true.
> Collapse works properly as a standalone fq but expand has no impact. How
> can I have access to the "hidden" do
Hey,
Could you please share the stacktrace or error message you received?
On Mon, Mar 30, 2020, 7:58 PM Szűcs Roland
wrote:
> Hi All,
>
> I manage to use edismax queryparser in solr 8.4.1 with collapse without any
> problem. I tested it with the SOLR admin GUI. So fq={!collapse field=title}
> wo
would be more performant
Regards,
Munendra S N
On Tue, Mar 10, 2020 at 7:51 PM GTHell wrote:
> But the fq can't use the alias field call score. Anyway, is the performance
> the same if I just sort the dist() function and get only 3 results?
>
>
>
> --
> Sent from
If you are looking to filter out all those products with greater than or
equal to 0.5, you could use
https://lucene.apache.org/solr/guide/8_4/other-parsers.html#function-range-query-parser
Function range query with the upper limit being 0.5 which could be added as
fq
Regards,
Munendra S N
On
>
> Notice the lists, within lists, within lists. Where the keys are adjacent
> items in the list. Is there a reason this isn't a JSON dictionary?
>
I think this is because of NamedList. Have you tried using json.nl=map as a
query parameter for this case?
Regards,
Munendra S N
Currently, it is not supported yet. Related JIRA -
https://issues.apache.org/jira/browse/SOLR-10567
Regards,
Munendra S N
On Thu, Dec 12, 2019 at 4:58 PM Mel Mason
wrote:
> Hi,
>
> I'm trying to have a range facet on a field of type solr.DateRangeField.
> As far as I can
Tokenizer is required
Regards,
Munendra S N
On Fri, Dec 6, 2019 at 4:14 PM Bernd Fehling
wrote:
> Hi Munendra S N,
>
> thanks for the hint about Tokenizer.
> Could I omit Tokenizer at all or is it needed by LowerCaseFilterFactory?
>
> The field "firstname"
>
> What should I use for numeric search.
numeric search or numeric sorting?
I tried with pint also, but the result was the same.
It should have worked. please make sure data is reindexed after fieldType
changes
Regards,
Munendra S N
On Fri, Dec 6, 2019 at 4:10 PM Anuj Bhargava
y out-of-the-box update processors to convert
the value to lowercase but implementing one should be easy. Other approach
is to convert the value in the preprocessing phase before sending it Solr.
Regards,
Munendra S N
On Fri, Dec 6, 2019 at 2:45 PM Bernd Fehling
wrote:
> Dear list,
>
Hi Anuj,
As the field type is String, lexicographical sorting is done, not numeric
sorting.
Regards,
Munendra S N
On Fri, Dec 6, 2019 at 3:12 PM Anuj Bhargava wrote:
> When I sort desc on posting_id sort=posting_id%20desc, I get the following
> result
> "posting_id":&quo
This change was done in Solr-7.2. SOLR-11501
<https://issues.apache.org/jira/browse/SOLR-11501> has the details about
the change
Regards,
Munendra S N
On Mon, Sep 9, 2019 at 1:16 PM Enna Raerinne (TAU)
wrote:
> Hi!
>
> I've been using block join queries with Solr version
S N
On Sat, Jun 1, 2019 at 4:01 AM Mandava, Rahul wrote:
> Hi,
>
>
> I am using SOLR 6.6.0 and real-time get to retrieve documents. Randomly I
> am seeing nullpointer exceptions in solr log files which in turn breaks the
> application workflow. Below is the stack trace
>
21 matches
Mail list logo
