Hi Solr-Users,
I am trying to better understand the solr capabilities, how one can
formulate queries in JSON format as well as tweak parameters. Currently I
have a logs collection (ca 6GB large) with a dozen of attributes running in
single server mode (F:\solr_deployment\solr-8.7.0\bin\solr.cmd st
Hi Solr Team,
I am trying to check how I can formulate facet queries using JSON format. I
can successfully formulate query, range, term queries, as well as nested
term queries. How can I formulate a nested facet query involving "query" as
well as "range" formulations? The following does not work:
Hi!
I run a three nodes Solr 8.5.1 cluster and experienced a bug when
updating the index: (adding document)
{
"responseHeader":{
"rf":3,
"status":500,
"QTime":22938},
"error":{
"msg":"Task queue processing has stalled for 20205 ms with 0 remaining
elements to process.",
"
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 Artur
Exactly _how_ are you indexing? In particular, how often are commits happening?
If you’re committing too often, Solr can block until some of the background
merges are complete. This can happen particularly when you are doing hard
commits in rapid succession, either through, say, committing from
Dave:
Yeah, every time there’s generic advice, there’s some situations where it’s not
the best choice ;).
In your situation, you’re trading of some space savings for moving up to 450G
all at once. Which sounds like it is worthwhile to you, although I’d check perf
numbers sometime
You may
Arturas,
I think your syntax is wrong for the range subfacet? -- the configuration
of the range facet should be directly under the `tt` key, rather than
nested under `t_buckets` in the request. (The response introduces a
"buckets" attribute that is not part of the request syntax).
Michael
On Thu,
Is there any way to apply facet to the partial search result?
For ex, we have 10m return by "dog" and like to apply facet to first 10K.
Possible?
Jae
Dear Community Members,
I am planning to use Term vector component for one of the use cases, as per
below solr documentation link solrj not supporting Term Vector Component,
do you have any other suggestions to use TVC in java application?
https://lucene.apache.org/solr/guide/8_4/the-term-vector-
Hi Michael,
Thanks for helping me to figure this out.
If I fire:
{
"query" : "*:*",
"limit" : 0,
"facet": {
"aip": { "query": "cfname2:aip", }
}
}
I get
"response": { "numFound": 20560849, "start": 0, "numFoundExact": true,
"docs": [] }, "facets": { "count": 205608
On 12/3/2020 9:55 AM, Jae Joo wrote:
Is there any way to apply facet to the partial search result?
For ex, we have 10m return by "dog" and like to apply facet to first 10K.
Possible?
The point of facets is to provide accurate numbers.
What would it mean to only apply to the first 10K? If ther
On 12/3/2020 10:20 AM, Deepu wrote:
I am planning to use Term vector component for one of the use cases, as per
below solr documentation link solrj not supporting Term Vector Component,
do you have any other suggestions to use TVC in java application?
https://lucene.apache.org/solr/guide/8_4/the
I think the first "error" case in your set of examples above is closest to
being correct. For "query" facet type, I think you want to explicitly
specify `"type":"query"`, and specify the query itself in the `"q"` param,
i.e.:
{
"query" : "*:*",
"limit" : 0,
"facet": {
"aip":
Hello All,
I am writing a custom function query that requires to parse a multivalued
field. I am getting this exception : org.apache.solr.common.SolrException: can
not use FieldCache on multivalued field
The function query works as expected with single-valued field.
How can I parse a multi-valu
Hi Michael,
I wish I were able to do a percent of what you are doing. Where does your
inspiration come from? It is not from the manuals, cause I've checked
those. How do you come up with this piece of art? Did you check this from
the source code? Which lines revealed these secrets? I am eternally
Hi Munedra,
This is great that I can get things faster by reducing the gap and by
increasing the number of threads. How to reduce gaps I know: one can
replace "gap": "+1HOUR" with "gap": "+1MONTH" What should I change
in the text below to increase the number of threads from one to 20?
Che
Hi Jae,
No, it’s not smarter than explicitly defining, for example enum for a
low-cardinality field.
Think of “smart” as a default path, and explicit definitions as some “hints”.
You can see that default path in this function:
https://github.com/apache/lucene-solr/blob/master/solr/core/src/jav
> On 3 Dec 2020, at 20:18, Shawn Heisey wrote:
>
> On 12/3/2020 9:55 AM, Jae Joo wrote:
>> Is there any way to apply facet to the partial search result?
>> For ex, we have 10m return by "dog" and like to apply facet to first 10K.
>> Possible?
>
> The point of facets is to provide accurate numb
Wild shot here: two Solr instances started on the same data directory?
Best regards,
Radu
--
Sematext Cloud - Full Stack Observability - https://sematext.com
Solr and Elasticsearch Consulting, Training and Production Support
> On 1 Dec 2020, at 06:25, sambasivarao giddaluri
> wrote:
>
> when c
Hi Mark,
I don’t really get your use-case. Maybe you can provide another example?
In either case, maybe the surround query parser would help?
https://lucene.apache.org/solr/guide/8_4/other-parsers.html#surround-query-parser
Or span queries in general via the XML query parser?
https://lucene.ap
20 matches
Mail list logo
