the next design question is, should each replica get its own instance?
What will give better performance, all replicas in one java instance or
having one instance for each replica?
Erick's reply is pretty complete. A shorter version: Unless the heap
required is huge, only run one Solr ins
nodes, replicas and so on.
> I have decided to begin with 5 hosts and want to setup 1 collection with 5
> shards.
> And start with 2 replicas per shard.
>
> But the next design question is, should each replica get its own instance?
>
> What will give better performance, all
Thanks Alessandro for the info.
I am currently in the phase to find the right setup with shards,
nodes, replicas and so on.
I have decided to begin with 5 hosts and want to setup 1 collection with 5
shards.
And start with 2 replicas per shard.
But the next design question is, should each
Unless you use recent Solt 7.x features where replicas can have different
properties[1], each replica is functionally the same at Solr level.
Zookeeper will elect a leader among them ( so temporary a replica will have
more responsibilities ) but (R1-R2-R3) does not really exist at Solr level.
It wi
Hi Shawn,
OK, got that.
Would shuffling or shifting the replicas bring any benfit or is it just wasted
time?
| | | | | |
shard1 | |r1| | | |r2| | | |r3| |
| | | | | |
|
Beyond failure/maintenance concerns, the first setup is not necessarily a
good distribution of the hosts' resources. Depending on the use case, it
could be much more prone to hot-spots in the cluster, especially if routing
or manual sharding is involved.
If for some reason, there are documents on
On 4/19/2018 6:28 AM, Bernd Fehling wrote:
How would you setup a SolrCloud an why?
shard1 shard2 shard3
| | | | | |
| |r1| | | |r1| | | |r1| |
| | | | | |
| | | | | |
|
How would you setup a SolrCloud an why?
shard1 shard2 shard3
| | | | | |
| |r1| | | |r1| | | |r1| |
| | | | | |
| | | | | |
| | | | | |
| |r2| |
Hi Deepthi,
I never tried case with multivalue field.
One note about join - your dictionary index must be single shard index and must
be replicated on all Solr nodes where your other index is.
Let us know how it worked out for you.
Thanks,
Emir
--
Monitoring - Log Management - Alerting - Anomaly
Hi Emir,
Thank you. The dictionary is static but the descriptions are long text. If
i denormalize each document will have 100+ descriptions and I have 8
million records in collection. There is lot of repetition of descriptions
and the index becomes large. I am trying to avoid that. Also data load
Hi Deepthi,
Is dictionary static? Can value for some id change? If static, and if query
performance matters to you, the best and also the simplest solution is to
denormalise data and store dictionary values with docs.
Alternative is to use join query parser:
https://lucene.apache.org/solr/guide
I have a dictionary of 2 ID's and their description which is in a
collection. There is another solr collection in which each document have 10
or more ID's(multi valued field). I would like to text search in the
dictionary and bring back the matched ID's and search these ID's in solr
collection.
I have a dictionary of 2 ID's and their description which is in a
collection. There is another solr collection in which each document have 10
or more ID's(multi valued field). I would like to text search in the
dictionary and bring back the matched ID's and search these ID's in solr
collection.
Why not copy the field values of category, title, features, spec into a
common text field and then search on that field. Otherwise use a edismax
query parser and search with user search string on all the above fields may
be by boosting title, category and specs field in order to get relevant
result
I understand.
Although I am not exactly sure how to solve this one, this should serve as
a helpful starting point:
https://lucidworks.com/resources/webinars/natural-language-search-with-solr/
On Wed, 6 Apr 2016, 11:27 Midas A, wrote:
> thanks Binoy for replying ,
>
> i am giving you few use case
thanks Binoy for replying ,
i am giving you few use cases
a) shoes in nike or nike shoes
Here "nike " is brand and in this case my query entity is shoe and entity
type is brand
and my result should only pink nike shoes
b) " 32 inch LCD TV sony "
32 inch is size , LCD is entity type a
Could you describe your problem in more detail with examples of your use
cases.
On Wed, 6 Apr 2016, 11:03 Midas A, wrote:
> i have to do entity and entity type mapping with help of search query
> while building solr query.
>
> how i should i design with the solr for search.
>
> Please guide me
i have to do entity and entity type mapping with help of search query
while building solr query.
how i should i design with the solr for search.
Please guide me .
Hi,
I have a general design question about federated search that I'd like to
get some thoughts on.
I have several line of business applications that manage their own data.
There is a need to search across these LOB apps, but each of them have
different authorization schemes in terms of all
="1"
> catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/>
>
>
>
>
>
>
>
> synonyms="pt_categories.txt" ignoreCase="true" expand="false"/>
> genera
ike grouping can be done on just 1 field.
> Maybe group.query could be used?
>
> Otis
> --
> Search Analytics - http://sematext.com/search-analytics/index.html
> Performance Monitoring - http://sematext.com/spm/index.html
>
>
> --
> If you repl
Hi,
On Thu, Nov 1, 2012 at 9:54 AM, fernando.beck wrote:
> David,
>
> appreciate the suggestion. Our current autocomplete feature is actually
> working pretty good.
> No perfomance issues; functionally is providing 100% results as expected.
> I checked sematext and also http://www.cominvent.com
y
too slow under load.
Best,
DQ
-Original Message-
From: fernando.beck [mailto:fernando.b...@gmail.com]
Sent: 01 November 2012 13:55
To: solr-user@lucene.apache.org
Subject: RE: Feature & design question: use autocomple?te to search on 2
different fields, and return 2 different da
, and given the presented schema, my question would be: is even
possible to get it done somehow? with 1 query, and "group" those results
while autocompleting on 2 different search fields?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Feature-design-question-use-aut
rand with product pictures to boot!
It's very, very quick in operation too.
Best,
DQ
-Original Message-
From: fernando.beck [mailto:fernando.b...@gmail.com]
Sent: 01 November 2012 13:40
To: solr-user@lucene.apache.org
Subject: Feature & design question: use autocomple?te to sea
calBusinessId
Thanks,
F
--
View this message in context:
http://lucene.472066.n3.nabble.com/Feature-design-question-use-autocomple-te-to-search-on-2-different-fields-and-return-2-different-dats-tp4017528.html
Sent from the Solr - User mailing list archive at Nabble.com.
thank you BOTH, Erick and Hos for the insight.
--
View this message in context:
http://lucene.472066.n3.nabble.com/faceted-searches-design-question-facet-field-not-part-of-qf-search-fields-tp3936509p3938080.html
Sent from the Solr - User mailing list archive at Nabble.com.
:
: The user as search terms like "my dog has fleas" and your query
: looks like
: q=my dog has fleas&fq=timestamp:[NOW/DAY TO NOW/DAY+1DAY]
: and the user sees all documents with those terms added since midnight
: last night. No confusion at all...
right ... wether the facets are useful or confu
gestions on itemDesc?
>
> just trying to understand how others approach this
>
> thanks
>
> default="false">
>
> edismax
> all
> 10
> itemNo^1.0 productType^.8 brand^.5
> *:*
>
>
>
>
> fals
this
thanks
edismax
all
10
itemNo^1.0 productType^.8 brand^.5
*:*
false
--
View this message in context:
http://lucene.472066.n3.nabble.com/faceted-searches-design-question-facet-field-not-part-of-qf-search-fields
(albums:query OR tracks:query) AND NOT(tracks:query -> albums:query)
Is this it? That last clause does sound like a join.
How do you shard? Is it possible to put all associated albums and
tracks in one shard? You can then do a join query against each shard
and merge the output yourself.
On Fri,
Thanks, but I don't want to exclude all tracks that are associated
with albums, I want to exclude tracks that are associated with albums
*which match the query* (tracks and their associated albums may have
different tags). I don't think your suggestion covers that.
On Fri, Apr 6, 2012 at 9:35 AM,
I'd consider a field like "associated_with_album", and a
field that identifies the kind of record this is "track or album".
Then you can form a query like -associated_with_album:true
(where '-' is the Lucene or NOT).
And then group by kind to get separate groups of albums and
tracks.
Hope this h
Apologies if this is a very straightforward schema design problem that
should be fairly obvious, but I'm not seeing a good way to do it.
Let's say I have an index that wants to model Albums and Tracks, and
they all have arbitrary tags attached to them (represented by
multivalue string type fields).
t;>
>>>>> a) Have 2 separate indexes. First one to store the information about all
>>>>> the cities and second one to store the retail stores information.
>>>>> Whenever user searches for a city then I return all the matching cities
>>>>> from firs
e matching cities from first
>>>> index and then do a spatial search on each of the matched city in the
>>>> second index. But this is too costly.
>>>>
>>>> b) Index only the cities which have a nearby store. Do all the
>>>> calculatio
gt;>>
>>>
>>> On Mar 1, 2012, at 7:59 AM, Dirceu Vieira wrote:
>>>
>>>> I believe that what you need is spatial search...
>>>>
>>>> Have a look a the documention: http://wiki.apache.org/solr/SpatialSearch
>>>>
>&
with this approach is that if a new retail store or a
>> city is added then I would have to re-index all the data again.
>>
>>
>> On Mar 1, 2012, at 7:59 AM, Dirceu Vieira wrote:
>>
>>> I believe that what you need is spatial search...
>>>
>&g
umention: http://wiki.apache.org/solr/SpatialSearch
>>
>> On Wed, Feb 29, 2012 at 10:54 PM, Venu Shankar
>> wrote:
>>
>>> Hello,
>>>
>>> I have a design question for Solr.
>>>
>>> I work for an enterprise which has a lot of retai
mention: http://wiki.apache.org/solr/SpatialSearch
>
> On Wed, Feb 29, 2012 at 10:54 PM, Venu Shankar
> wrote:
>
>> Hello,
>>
>> I have a design question for Solr.
>>
>> I work for an enterprise which has a lot of retail stores (approx. 20K).
>> These ret
I believe that what you need is spatial search...
Have a look a the documention: http://wiki.apache.org/solr/SpatialSearch
On Wed, Feb 29, 2012 at 10:54 PM, Venu Shankar wrote:
> Hello,
>
> I have a design question for Solr.
>
> I work for an enterprise which has a lot of retail
Hello,
I have a design question for Solr.
I work for an enterprise which has a lot of retail stores (approx. 20K).
These retail stores are spread across the world. My search requirement is
to find all the cities which are within x miles of a retail store.
So lets say if we have a retail Store
I admit I just glanced at your problem statement, but
three things come to mind...
1> have you looked at the "limited join" patch and would
that work?
2> try searching the list for "hierarchical", very similar
questions have been discussed before, although I
don't quite remember the answers
Hi there
I have a question regarding how to setup schema for some data. This data is
basically parent-child data for different types of records .. so
a bunch of records representing projects and subprojects where each
subproject has a parent project .. and a project has many child sub projects
an
, 2011 8:55 AM
To: solr-user@lucene.apache.org
Subject: Re: Schema Design Question
Of your first two options, I'd go with a multi-valued field for each book (1).
But kenf_nc's suggestion is a good one too.
On Sun, May 15, 2011 at 3:54 AM, kenf_nc wrote:
> create a separate document
edly or RDBMs orientedly. You need to think differently.
> Solr/Lucene find text and they find it very fast over huge amounts of data.
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Schema-Design-Question-tp2939045p2942809.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
with Solr schema design is thinking either
object orientedly or RDBMs orientedly. You need to think differently.
Solr/Lucene find text and they find it very fast over huge amounts of data.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Schema-Design-Question-tp2939045p2942809
ith a large number of values or should you pass a large number of values
in as a Boolean clause?
Zac
-Original Message-
From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com]
Sent: Friday, May 13, 2011 10:37 AM
To: solr-user@lucene.apache.org
Subject: Re: Schema Design Question
H
"solr-user@lucene.apache.org"
> Sent: Fri, May 13, 2011 12:28:35 PM
> Subject: Schema Design Question
>
> Let's say I have a data model that involves books and bookshelves. I have
> tens
>of thousands of books and thousands of bookshelves. There is a
Let's say I have a data model that involves books and bookshelves. I have tens
of thousands of books and thousands of bookshelves. There is a many-many
relationship between books & bookshelves. All of the books are indexed by SOLR.
I need to be able to query SOLR and get all the books for a give
Thank you. These are good general suggestion.
Regarding the optimization for indexing vs. querying: are there any specific
recommendations for each of those cases available somewhere. A link, for
example, would be fabulous.
I'm also still curious about solutions that go further.
For example,
from
what I've seen. Having 2 Solr instances, one optimized for Indexing (the
master) and one optimized for querying (the slave) with replication, would
help minimize the problem.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Index-Design-Question-tp2523811p2524424.html
We are indexing documents with several associated fields for search and
display,
some of which may change with a much higher frequency than the document
content.
As per my understanding, we have to resubmit the entire gamut of fields with
every update.
If the reindexing of the documents beco
: - We are indexing CSV files and generating field names dynamically from the
: "header" line.
: User should be able to *list all the possible header names* (i.e. dynamic
: field names), and filter results based on some of the field names.
: - Also, list* all possible values* associated to for a g
First Thanks for the response.
Yes, mostly likely we want to optimize to one index file. I think it is
possible, coming from the RDBMS world we might be over complicating the
solution.
*Requirement:*
- We are indexing CSV files and generating field names dynamically from the
"header" line.
User
On Sat, Jan 16, 2010 at 3:33 AM, Kumaravel Kandasami <
kumaravel.kandas...@gmail.com> wrote:
> Need to your suggestion in best designing the following requirement.
>
> - We have two indexes.
> Index 1: "name_index",
> Fields:
> "id" - indexed, not stored
> "field_name" - indexed, stored.
>
> Ind
Need to your suggestion in best designing the following requirement.
- We have two indexes.
Index 1: "name_index",
Fields:
"id" - indexed, not stored
"field_name" - indexed, stored.
Index 2: "trans_index',
Fields(Dynamic Schema):
"id" - indexed, not stored
"*" - indexed, stored.
(Dynamic field
I have documents that represent Companies. Each company has a field "Internet"
which is a boolean field, True means the company is an Internet company.
There's also another field "location" which is the city the company is located
in, eg. "Austin" or "Houston".
A company can be both an Internet
uary 20, 2009 3:14 PM
To: solr-user@lucene.apache.org
Subject: Re: New to Solr/Lucene design question
Hi Todd,
I think I see what you are saying here.
In our schema.xml we can define it like this:
and then add data like this:
Yogesh
Chawla
myMiddleName
on,
Yogesh
- Original Message
From: "Feak, Todd"
To: solr-user@lucene.apache.org
Sent: Tuesday, January 20, 2009 4:49:56 PM
Subject: RE: New to Solr/Lucene design question
A third option - Use dynamic fields.
Add a dynamic field call "*_stash". This will allow new fields for
Original Message-
From: Yogesh Chawla - PD [mailto:premiergenerat...@yahoo.com]
Sent: Tuesday, January 20, 2009 2:30 PM
To: solr-user@lucene.apache.org
Subject: New to Solr/Lucene design question
Hello All,
We are using SOLR/Lucene as the search engine for an application
we are designing.
Hello All,
We are using SOLR/Lucene as the search engine for an application
we are designing. The application is a workflow application that can
receive different types of documents.
For example, we are currently working on getting booking documents but
will also accept arrest documents later thi
62 matches
Mail list logo
