Hello Solr-dev folks,
I am having a doubt in implicit routing and didn't find much info about
this over the internet, so Please help me out on this.
*About environment:*
M/c 1: Zookeeper 1 and Solr 1
M/c 2: Zookeeper 2 and Solr 2
I am using clustered zookeeper and using "CloudSolrClient" from so
Hi,
I’m quite new to Solr and am interested in using spatial search for geospatial
data (Solr 7.1).
One problem is addressing feature density over a layer and using this to
determine if a layer would be a relevant result over a search extent. I’d like
to know is it feasible/possible to “split”
Hello All,
I am having a doubt in implicit routing and didn't find much info about
this over the internet, so Please help me out on this.
*About environment:*
M/c 1: Zookeeper 1 and Solr 1
M/c 2: Zookeeper 2 and Solr 2
I am using clustered zookeeper and using "CloudSolrClient" from solrJ
API in
On 1/9/2018 9:36 AM, Rick Leir wrote:
> A while ago the default was changed to StandardTokenizer from
> ClassicTokenizer. The biggest difference seems to be that Classic does not
> break on hyphens. There is also a different character pr(mumble). I prefer
> the Classic's non-break on hyphens.
T
: Might be the case as you mentioned Shawn. But there are no search requests
: triggered and might be that somehow a search query is getting fired to Solr
: end while indexing. Given the complete log information(solr.log) while the
: indexing is triggered.
the search request is triggered by a "ne
Might be the case as you mentioned Shawn. But there are no search requests
triggered and might be that somehow a search query is getting fired to Solr
end while indexing. Given the complete log information(solr.log) while the
indexing is triggered.
2018-01-09 15:42:25.292 INFO (qtp834133664-15) [
Thanks Shalin for sharing the link. However if I follow the thread then it
seems like there was no conclusive evidence found that the performance
degradation was due to the merge or index related metrics.
If that is the case then can we just get rid of the config and publish
these metrics by defaul
Thank you very much for all your help.
On Tue 9 Jan 2018, 16:32 Erick Erickson, wrote:
> One thing to be aware of is that the commit points on the replicas in a
> replica may (will) fire at different times. So when you're comparing the
> number of docs on the replicas in a shard you have to comp
Hi all
A while ago the default was changed to StandardTokenizer from ClassicTokenizer.
The biggest difference seems to be that Classic does not break on hyphens.
There is also a different character pr(mumble). I prefer the Classic's
non-break on hyphens.
What was the reason for changing this d
One thing to be aware of is that the commit points on the replicas in a
replica may (will) fire at different times. So when you're comparing the
number of docs on the replicas in a shard you have to compare before the
last commit interval. So say you have a soft commit of 1 minute. When
comparing t
On 1/9/2018 8:31 AM, padmanabhan wrote:
> I get the below error whenever an indexing is executed.. I didn't find enough
> clue on to where this field is coming from and how could i debug on to it..
> any help would be appreciated
> 2018-01-09 16:03:11.705 INFO
> (searcherExecutor-51-thread-1-pr
*Hello*
*The code which worked for me:*
SolrClient client = new HttpSolrClient.Builder("
http://localhost:8983/solr/shakespeare";).build();
SolrQuery query = new SolrQuery();
query.setRequestHandler("/select");
query.setQuery("text_entry:henry");
query.setFields("
To correct myself, querying "*" is allowed in the sense that asking for
all fields is done by assigning "*" to the fl parameter.
So the problem is possibly not that "*" is requested, but that the star
is used somewhere else, probably in the q parameter.
We can help you better when you pass the fu
First, you might want to index, but what Solr is executing here is a
search request.
Second, you're querying for a dynamic field "*" which is not defined in
your schema. This is quite obvious, the exception says right this.
So whatever is sending the query (some client, it seems) is doing the
wro
Thank you Erick, it worked.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
I get the below error whenever an indexing is executed.. I didn't find enough
clue on to where this field is coming from and how could i debug on to it..
any help would be appreciated
2018-01-09 16:03:11.705 INFO
(searcherExecutor-51-thread-1-processing-x:master_backoffice_backoffice_product_defa
FYI, This has been resolved.
Dinesh Sundaram
MBS Platform Engineering
Mastercard
[cid:image001.png@01D3892A.668B6700]
From: Sundaram, Dinesh
Sent: Monday, January 8, 2018 1:58 PM
To: solr-user
Subject: SSL configuration with Master/Slave
Team,
I'm facing an SSL issue while configuring Master/
On 1/8/2018 10:23 AM, Deepak Goel wrote:
> *I am trying to search for documents in my collection (Shakespeare). The
> code is as follows:*
>
> SolrClient client = new HttpSolrClient.Builder("
> http://localhost:8983/solr/shakespeare";).build();
>
> SolrDocument doc = client.getById("2");
> *However
Hi All,
Problem: Not able to build suggest data on all solr cluster nodes
Configured three solr using external zookeeper
Configured the requestHandler for auto-suggestion as below
true
5
Name
suggest
Name
name
name
AnalyzingInfixLookupFac
Hi Erick,
Apology for delay.
[This isn't what I meant. I meant to query each replica directly
_within_ the same shard. Your problem statement is that the leader and
replicas (I use "followers") have different document counts. How are
you verifying this? Through the admin UI? Using &distrib=false
On 1/7/2018 1:30 PM, Rick Leir wrote:
The easy solution is to put something like solr-security-proxy [1] in front of
a Solr/Velocity app, and this is working for me. However, this has a blacklist
for Solr parms and I think it should have a whitelist instead. Also, it does
not check ranges or f
On 1/8/2018 10:17 PM, kshitij tyagi wrote:
1. Does in place updates opens a new searcher by itself or not?
2. As the entire segment is rewriten, it means that frequent in place
updates are expensive as each in place update will rewrite the entire
segment again? Correct me here if my understanding
On Tue, Jan 9, 2018 at 11:37 AM, Shawn Heisey wrote:
> On 1/9/2018 2:42 AM, Robert Krüger wrote:
>
>> I am looking to upgrade an application that still uses version 4.6.1 to
>> latest solr (7.2) but realized that support for EmbeddedSolrServer seems
>> to
>> have vanished with 7.0 but I could fin
On 1/9/2018 2:42 AM, Robert Krüger wrote:
I am looking to upgrade an application that still uses version 4.6.1 to
latest solr (7.2) but realized that support for EmbeddedSolrServer seems to
have vanished with 7.0 but I could find no mention of it in the release
notes, which strikes me as odd for
Hi,
I am looking to upgrade an application that still uses version 4.6.1 to
latest solr (7.2) but realized that support for EmbeddedSolrServer seems to
have vanished with 7.0 but I could find no mention of it in the release
notes, which strikes me as odd for such a disruptive change. Is it
somewhe
25 matches
Mail list logo
