I'm updating from a basic Solr Client to the ConcurrentUpdateSolrClient and
I'm hitting a really strange error. I cannot share the code but the snippet
is like:
try (ConcurrentUpdateSolrClient solrUpdateClient =
> new ConcurrentUpdateSolrClient("
>
Karthik:
The Apache mailing list is pretty aggressive about removing
attachments. Could you possibly open a JIRA and attach the file as a
patch? If at all possible a patch file with just the diffs would be
best.
One problem is that it'll be a two-step process. The JIRAs have been
being hit with
Slow down a bit ;)...
First, just to cover the bases, you have done a commit, right? The
index generation on the UI screen is a bit misleading as replicas in
SolrCloud don't necessarily have the same generation, that's normal.
The "master/slave" bits are cruft from the older non-cloud days.
So
Joe this might be _version_ as in Solr's optimistic concurrency used in
atomic updates, etc
http://yonik.com/solr/optimistic-concurrency/
On Fri, Apr 22, 2016 at 5:24 PM Joe Lawson <
jlaw...@opensourceconnections.com> wrote:
> I'm updating from a basic Solr Client to the
I think I just added the right person, let us know if you don't have
access and/or if you need access to the LUCENE JIRA.
Erick
On Fri, Apr 22, 2016 at 5:17 PM, Karthik Ramachandran
wrote:
> Eric
> I have created a JIRA id (kramachand...@commvault.com). Once I
Eric
I have created a JIRA id (kramachand...@commvault.com). Once I get
access I will create the JIRA and submit the patch.
With Thanks & Regards
Karthik Ramachandran
CommVault
Direct: (732) 923-2197
P Please don't print this e-mail unless you really need to
On 4/22/16, 8:04 PM, "Erick
I'm confused. Are you sharding or not? Sharding is used when your
index is too big to fit on one Solr, so your docs go to separate Solr
nodes. That is, if shard1 contains the doc with id=12, shard2 will NOT
have that doc.
If you're not sharding (i.e. each slave has all the docs in your
Hey,
I'm using solr 5.2.1 and yesterday I started migrating to SolrCloud so I
might be quite noobish with it. The thing is that I could create 3
collections with not so many inconvenients, but when trying to create
another collection it throws a timeout and inside solr log it says "Could
not get
Hello guys,
I use solr 6 for indexing data with points and polygons.
I have a question about indexing polygons from csv file. I have configured
type:
and field
I have tried to import this csv:
Hi guys,
How can I set the defaultOperator to be AND?
If I add the following line to the schema.xml, even if I do a search
'title:"test" OR author:"me"', it will returns documents matching
'title:"test" AND author:"me"':
solr version: 6.0
I know that I can overwrite the query with q.op,
sessionVariables=group_concat_max_len=. in the connection URL works as
expected.
Thank you very much!
Bye
Zaccheo
Il giorno gio 21 apr 2016 alle ore 01:14 Alexandre Rafalovitch <
arafa...@gmail.com> ha scritto:
> The driver documentation talks about "sessionVariables" that might be
>
Yes Jan, I'm using edismax.
This is (a part of) my requestHandler:
false
explicit
10
title,abstract,authors,doi
edismax
title^1.0 author^1.0
[...]
Is there anything I should do to improve/fix it?
Kind regards,
Bastien
On 22/04/2016 12:42,
Hi
Which query parser are you using? If using edismax yo may be hitting a recent
bug concerning default operator and explicit boolean operators.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 22. apr. 2016 kl. 11.26 skrev Bastien Latard - MDPI AG
>
Hi Alisa,
This was a bit too hard for me to grok on a first pass... then I saw
your related blog post which includes the actual sample data and makes
it more clear.
More comments inline:
On Wed, Apr 20, 2016 at 2:29 PM, Alisa Z. wrote:
> Hi all,
>
> I have been stretching
Hi Yonik,
Thanks a lot for your response.
I have discussed this with Mikhail Khludnev already and tried this suggestion.
Here's what I've got:
sentiment: positive
author: Bob
text: Great post about Solr
2.blog-posts.comments-id: 10735-23004 //this is a new
I used SolrJ and wrote a test to confirm that the max query length supported by
Solr (by default) was 8192 in Solr 5.3.1
Based on the default Jetty settings
jetty.xml:
The test would not work however until I had used a max size of 4096 (so the
query passes at 4095 and returns a
Are you using get instead of post?
https://dzone.com/articles/solr-select-query-get-vs-post
On Fri, Apr 22, 2016 at 8:12 PM, Kelly, Frank wrote:
> I used SolrJ and wrote a test to confirm that the max query length
> supported by Solr (by default) was 8192 in Solr 5.3.1
I'm not sure, may be this should work :
QueryResponse response = solr.query(q, METHOD.POST);
Let's wait for others response.
On Fri, Apr 22, 2016 at 8:51 PM, Kelly, Frank wrote:
> I am using the SolrJ library - does it have a way to specify one variant
> (POST) over
Have you added this new processor chain to update handler that you are
using(as shown below)?
myChain
https://wiki.apache.org/solr/UpdateRequestProcessor#Selecting_the_UpdateChain_for_Your_Request
On Thu, Apr 21, 2016 at 2:59 PM, vrajesh wrote:
> to concatenating two
I am using the SolrJ library - does it have a way to specify one variant
(POST) over the other (GET)?
-Frank
On 4/22/16, 11:13 AM, "Reth RM" wrote:
>Are you using get instead of post?
>
>https://dzone.com/articles/solr-select-query-get-vs-post
>
>
>
>On Fri, Apr 22,
On Fri, Apr 22, 2016 at 12:26 PM, Alisa Z. wrote:
> Hi Yonik,
>
> Thanks a lot for your response.
>
> I have discussed this with Mikhail Khludnev already and tried this
> suggestion. Here's what I've got:
>
>
>
> sentiment: positive
> author: Bob
> text: Great post about Solr
>
Hey guys,
I am trying to implement Distributed search with Master Slave server. Search
requests goes to Slave Servers. I am planning to have a load balancer before
the Slave servers. So here is the custom search handler which is defined.
*:*
I have a SolrCloud setup with v5.2.1 - just two hosts. A ZK ensemble of 3
hosts. Just today, customers searching in one specific collection reported
seeing varying results with the same search. I could confirm this by looking
at the logs - same search with different hits by the solr host. In the
Solved it - had to make sure default requestHander was configured for
spellcheck.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Making-managed-schema-unmutable-correctly-tp4264051p4272235.html
Sent from the Solr - User mailing list archive at Nabble.com.
24 matches
Mail list logo