Thanks for your reply! Yes, it turned out to be an issue with the way the
request was being sent, which was cURL that required special handling and
escaping of spaces and special characters. Using another client cleared
this issue and the request below worked perfectly now.
Best,
A.
On Thu, Jul 4
Shawn,Erick,
Thank you for the explanation. The merge scheduler params make sense now.
Thanks,
Rahul
On Wed, Jul 3, 2019 at 11:30 AM Erick Erickson
wrote:
> Two more tidbits to add to Shawn’s explanation:
>
> There are heuristics built in to ConcurrentMergeScheduler.
> From the Javadocs:
> * If
Hi,
You can use the "Analysis" page in the Solr Admin UI to input your value
and test the output, and see how the tokenizersand various filters does to
your value.
Regards,
Edwin
On Thu, 4 Jul 2019 at 17:28, Yasufumi Mizoguchi
wrote:
> Hi,
>
> EdgeNGramFilterFactory seems to drop tokens shorte
Hi. I'm using solrj (7.3.1).
I encountered an error for delete queries that fail on an unauthorized
exception. I noticed other requests succeed.
I managed to track it down to NTLM authentications.
org.apache.http.impl.execchain.MainClientExec (line 315) will remove
authentication headers befor
On 7/3/2019 4:07 AM, Talvinder Matharu wrote:
I have created a new core via the admin console, also tried via the API, and
notice that after a restart it fails to pick up the cores that were created.
To overcome this, I have to recreate the core again using the admin console to
allow me to us
On 7/3/2019 1:36 AM, Avi Steiner wrote:
We had some cases with customers (Solr 5.3.1, one search node, one shard) with
huge tlog files (more than 1 GB).
With 30 seconds on the autoCommit, that should not be happening.
When a hard commit fires, the current tlog is closed and a new one
starts.
On 7/4/2019 9:14 AM, Prince Manohar wrote:
I am using Solr version *6.4.2*. I got your answers.
I have another question. Can we use a *Range query* on point field?
I am trying to do something like
*fq=abc.pqr_d:[ 1500 TO 2000 ]*
Is it a valid filter?
Yes. In fact, range queries are one of
1. Frustrating when this happens.
2. yes.The impact depends on how aggressively you autowarm, i.e. what your
autowarm counts are. Whether users _notice_ or not is an open question. Since
searches are served from the old searcher until the new one’s autowarming is
complete, if you have some spar
The admin/analysis page is very valuable for this kind of question.
Your edgengram filter has a mingram size of 3 so it’s throwing out 72.
Best,
Erick
> On Jul 4, 2019, at 1:27 AM, Shamik Bandopadhyay wrote:
>
> autoGeneratePhraseQueries="true"> "solr.WhitespaceTokenizerFactory" /> "solr.
Thanks for the answers.
I am using Solr version *6.4.2*. I got your answers.
I have another question. Can we use a *Range query* on point field?
I am trying to do something like
*fq=abc.pqr_d:[ 1500 TO 2000 ]*
Is it a valid filter?
On Thu, Jul 4, 2019 at 1:47 PM Yasufumi Mizoguchi
wrote:
It’s very difficult to even guess unless you provide more details than “I tried
something and it didn’t work”.
Exactly _how_ did you try to create the core?
What are you trying to accomplish? What does the Solr log say on startup, there
should be a message about where it starts looking for core
Might be a formatting error with my mail client, but the very first line is not
well formed.
q: * is incorrect
q=*:*
I do not see that example on the page either. Looks like you took the bit
that starts with stats=true and mis-typed the q clause.
Best,
Erick
> On Jul 3, 2019, at 5:08 AM, Ah
Hi,
EdgeNGramFilterFactory seems to drop tokens shorter than minGramSize param.
Check the example of minGramSize="4" maxGramSize="6" case in below page.
https://lucene.apache.org/solr/guide/8_1/filter-descriptions.html#edge-n-gram-filter
So, you should set minGramSize=2 or 1 if you want to keep 7
Hi,
I'm using EdgeNGramFilterFactory to support partial search. Here's my
field definition.
I run into an issue when I'm trying a numeric terms in search. For e.g. if
I search for "72 hours", EdgeNGramFilterFactory ignores 72 and only stores
hou and hour in index. Since
Hi,
I have created a new core via the admin console, also tried via the API, and
notice that after a restart it fails to pick up the cores that were created.
To overcome this, I have to recreate the core again using the admin console to
allow me to use the search index. Do you have any idea why
Hi,
As per the documentation recommendation of using pivot with stats component
instead (
https://lucene.apache.org/solr/guide/8_1/faceting.html#combining-stats-component-with-pivots),
replacing the stats options that were previously used with the newer pivot
options as follows:
q: *
stats=true
s
Hi,
I'm using EdgeNGramFilterFactory to support partial search. Here's my
field definition.
<
filter class="solr.KeywordMarkerFilterFactory" protected="protwords.txt" />
I run into an issue when I'm trying a numeric terms in search. For e.g. if
I search for *72 hours*, Ed
Hi,
I'm using EdgeNGramFilterFactory to support partial search. Here's my
field definition.
I run into an issue when I'm trying a numeric terms in search. For e.g. if
I search for "72 hours", EdgeNGramFilterFactory ignores 72 and only stores
hou and hour in index. Since
Hi,
Which version of Solr are you using?
And what is the field settings?
Reference guide says that sorting with single valued *PointType fields
requires docValues="true" option in field settings.
https://lucene.apache.org/solr/guide/8_1/field-types-included-with-solr.html#field-types-included-wit
19 matches
Mail list logo
