Hello,
thank you for the detailed answer.
If a timeout between shard leader and replica can lead to a smaller rf value
(because replication has timed out), is it possible to increase this timeout in
the configuration?
Best Regards,
Martin Mois
Comments inline:
On Mon, Oct 12, 2015 at 1:31 PM
Thank you very much Erick.
Arcadius.
On 13 October 2015 at 22:04, Erick Erickson wrote:
> Just added you to the Solr Wiki contributors group, if you need to
> access the Lucene Wiki let us know.
>
> Best,
> Erick
>
> On Tue, Oct 13, 2015 at 1:57 PM, Arcadius Ahouansou
> wrote:
> > Hello Erick.
We want to use suggester but also want to show those results closest to my
lat,long... Kinda combine suggester and bq=geodist()
On Mon, Oct 12, 2015 at 2:24 PM, Salman Ansari
wrote:
> Hi,
>
> I have been trying to get the autocomplete feature in Solr working with no
> luck up to now. First I rea
Thank you Alessandro and Erick.
Will try out the SolrJ methond.
Regards,
Edwin
On 14 October 2015 at 00:00, Erick Erickson wrote:
> Here's a sample:
> https://lucidworks.com/blog/2012/02/14/indexing-with-solrj/
>
> On Tue, Oct 13, 2015 at 4:18 AM, Alessandro Benedetti
> wrote:
> > The most r
Great. Thanks Erick.
On 10/13/15 5:39 PM, Erick Erickson wrote:
More than expected, guaranteed. As long as at least one replica in a
shard is active, all queries should succeed. Maybe more slowly, but
they should succeed.
Best,
Erick
On Tue, Oct 13, 2015 at 4:25 PM, Rallavagu wrote:
It app
More than expected, guaranteed. As long as at least one replica in a
shard is active, all queries should succeed. Maybe more slowly, but
they should succeed.
Best,
Erick
On Tue, Oct 13, 2015 at 4:25 PM, Rallavagu wrote:
> It appears that when a node that is in "recovery" mode queried it would
It appears that when a node that is in "recovery" mode queried it would
defer the query to leader instead of serving from locally. Is this the
expected behavior? Thanks.
On Wed, Oct 7, 2015 at 9:42 AM, Ryan Josal wrote:
> I developed a join transformer plugin that did that (although it didn't
> flatten the results like that). The one thing that was painful about it is
> that the TextResponseWriter has references to both the IndexSchema and
> SolrReturnFields obje
Just added you to the Solr Wiki contributors group, if you need to
access the Lucene Wiki let us know.
Best,
Erick
On Tue, Oct 13, 2015 at 1:57 PM, Arcadius Ahouansou
wrote:
> Hello Erick.
> Thank you for the detailed info.
> My username is arcadius.
>
> Thanks.
>
>
> On 13 October 2015 at 16:58
Hello Erick.
Thank you for the detailed info.
My username is arcadius.
Thanks.
On 13 October 2015 at 16:58, Erick Erickson wrote:
> Create a user on the Wiki (anyone can), then tell us the user name
> you've created and we'll add you to the auth lists. There are separate
> lists for Solr and L
Hi,
Thanks for your response.
I did have a look at pivots, and they could work in a way. We're still on
Solr 4.3, so I'll have to wait for sub-facets - but they sure look pretty
cool!
Peter
On Tue, Oct 13, 2015 at 12:30 PM, Alessandro Benedetti <
benedetti.ale...@gmail.com> wrote:
> Can you mode
The main reason is that the updates are coming from some client
applications and it is not a controlled indexing process. The controlled
indexing process works fine (after spending some time to tune it). Will
definitely look into throttling incoming updates requests and reduce the
number of con
How heavy is heavy? The proverbial smoking gun here will be messages in any
logs referring to "leader initiated recovery". (note, that's the
message I remember seeing,
it may not be exact).
There's no particular work-around here except to back off the indexing
load. Certainly increasing the
thread
Also, we have increased number of connections per host from default (20)
to 100 for http thread pool to communicate with other nodes. Could this
have caused the issues as it can now spin many threads to send updates?
On 10/13/15 8:56 AM, Erick Erickson wrote:
Is this under a very heavy indexin
The heavy load of indexing is true. During this time, all other nodes
are under "recovery" mode and search queries are referred to leader and
it times out. Is there a temporary work around for this? Thanks.
On 10/13/15 8:56 AM, Erick Erickson wrote:
Is this under a very heavy indexing load? Th
Is this under a very heavy indexing load? There were some
inefficiencies that caused followers to work a lot harder than the
leader, but the leader had to spin off a bunch of threads to send
update to followers. That's fixed int he 5.2 release.
Best,
Erick
On Tue, Oct 13, 2015 at 8:40 AM, Rallava
Here's a sample:
https://lucidworks.com/blog/2012/02/14/indexing-with-solrj/
On Tue, Oct 13, 2015 at 4:18 AM, Alessandro Benedetti
wrote:
> The most robust and simple way to go is building your own Indexer.
> You can decide the platform you want, Solr has plenty of client API
> libraries.
>
> For
Create a user on the Wiki (anyone can), then tell us the user name
you've created and we'll add you to the auth lists. There are separate
lists for Solr and Lucene. We had to lock these down because we were
getting a lot of spam pages created.
The reference guide (CWiki) is restricted to committer
Please help me understand what is going on with this thread.
Solr 4.6.1, single shard, 4 node cluster, 3 node zk. Running on tomcat
with 500 threads.
There are 47 threads overall and designated leader becomes unresponsive
though shows "green" from cloud perspective. This is causing issues.
Performing a sequence of queries can help too. For example, if users
commonly search for a product name, you could do an initial query on just
the product name field which should be much faster than searching the text
of all product descriptions, and highlighting would be less problematic. If
that
Thanks Alessandro,
Certainly the use of the Analysis tool, along with debug query supplies a
lot of useful information.
I've found that a combination of using the ngram field, (as detailed
previously), along with the qf param of the edismax parser seems to be
working well.
>From there I can dynamic
Hello.
Please, can I have the right to edit the Wiki?
Thanks.
Arcadius.
Mark,
The older spellcheck implementations create an n-gram sidecar index, which is
why you're seeing your name split into 2-grams like this. See the IR Book by
Manning et al, section 3.3.4 for more information. Based on the results you're
getting, I think it is loading your file correctly.
I would be interested in seeing it in action. Do you have any documentation
available on what it does and how?
Thanks
From: r b
Sent: Friday, October 2, 2015 3:09 PM
To: solr-user@lucene.apache.org
Subject: are there any SolrCloud supervisors?
I've been
Sounds interesting...
On Tue, Oct 13, 2015 at 12:58 AM, Trey Grainger wrote:
> I'd be very interested in taking a look if you post the code.
>
> Trey Grainger
> Co-Author, Solr in Action
> Director of Engineering, Search & Recommendations @ CareerBuilder
>
> On Fri, Oct 2, 2015 at 3:09 PM, r b
Comments inline:
On Mon, Oct 12, 2015 at 1:31 PM, MOIS Martin (MORPHO)
wrote:
> Hello,
>
> I am running Solr 5.2.1 in a cluster with 6 nodes. My collections have been
> created with replicationFactor=2, i.e. I have one replica for each shard.
> Beyond that I am using autoCommit/maxDocs=1 an
Thanks guys, I was able to make it work using your articles. The key point
was mentioned in one of the articles which was that suggestion component is
preconfigured in techproducts sample. I started my work from there and
tweaked it to suit my needs. Thanks a lot!
One thing still remaining, I don'
We had the very exact issue and we solved as James suggested :)
To answer Susheel, the requirement is to provide users with the only
suggestions he should see.
It can seem a paranoid request but can happen that we don't want to show
any of the indexed data for different users.
In enterprise search
As Erick suggested you are reading a really old way to provide the
autocomplete feature !
Please take a read to the docs Erick linked and to my blog as well.
It will definitely give you more insight about the Autocomplete world !
Cheers
[1] http://alexbenedetti.blogspot.co.uk/2015/07/solr-you-com
Can you model your business domain with Solr nested Docs ? In the case you
can use Yonik article about nested facets.
Cheers
On 13 October 2015 at 05:05, Alexandre Rafalovitch
wrote:
> Could you use the new nested facets syntax?
> http://yonik.com/solr-subfacets/
>
> Regards,
>Alex.
>
The most robust and simple way to go is building your own Indexer.
You can decide the platform you want, Solr has plenty of client API
libraries.
For example if you want to write your Indexer app in Java, you can use
SolrJ..
Each client library will give you all the flexibility you need to index
s
Generally it is highly discouraged to build the spellcheck on startup.
In the case of big suggestion file, you are going to build the suggester
data structures ( basically FST in memory and then in disk) for a long
time, on startup.
You should build your spellchecker only when you change the file s
The first thing I would suggest you is the use of the Analysis tool, to
explore your analysis at query and index time.
This will be the first step to understand if you are actually tokenising
and token filtering as expected.
Then you should play with different fields ( in the case the original fie
Thanks to you all for those informed advices.
Thanks Trey for your very detailed point of view. This is now very clear to
me how a search on multiple fields can grow slower than a search on a
catchall field.
Our actual search model is problematic: we search on a catchall field, but
need to know w
Thanks Scot.
That is definitely moving things in the right direction
I have another question that relates to this. It is also requested to
implement a partial word search on the service name field.
However, each service also has a unique identifier (string). This field
requires exact string matchi
Hi,
I'm trying to use the JiebaTokenizerFactory to index Chinese characters in
Solr. It works fine with the segmentation when I'm using
the Analysis function on the Solr Admin UI.
However, when I tried to do the highlighting in Solr, it is not
highlighting in the correct place. For example, when
How odd, though I'm afraid this is reaching the limit of my knowledge at this
point (and I still can't find where that box is within the Admin UI!).
The only thing I'd say is to check that "logtext" is a defined named field
within your schema, and to double check how it's field type is defined.
Hi,
What is the best practice to do indexing in Solr for production system.I'm
using Solr 5.3.0.
I understand that post.jar does not have things like robustness checks and
retires, which is important in production, as sometimes certain records
might failed during the indexing, and we need to re-t
38 matches
Mail list logo
