Re: Specifying dynamic field type without polluting actual field names with type indicators

t; > 2. On the query side, eDisMax can perform aliasing so that user-specified > field names in queries get mapped to one or more indexed fields: look for > “alias” in < > https://cwiki.apache.org/confluence/display/solr/The+Extended+DisMax+Query+Parser > >. > > -- > Steve &

Creating dynamic field, but strip the type indicator postfix from the name

Hi Everyone, I am wondering if it is possible to store dynamic fields without the type indicator postfix. In our Solr environment, I would like to 1.) use dynamic fields ("data drivern collections" with no fixed fields specified in advance) 2.) be able to specify the field type, but without

Re: Specifying dynamic field type without polluting actual field names with type indicators

t; > -- > Steve > www.lucidworks.com > > > On May 17, 2016, at 11:05 AM, Horváth Péter Gergely < > peter.gergely.horv...@gmail.com> wrote: > > > > Hi All, > > > > By default Solr allows you to define the type of a dynamic field by > > appending a pos

Specifying dynamic field type without polluting actual field names with type indicators

Hi All, By default Solr allows you to define the type of a dynamic field by appending a post-fix to the name itself. E.g. creating a color_s field instructs Solr to create a string field. My understanding is that if we do this, all queries must refer the post-fixed field name as well. So instead

Specifying dynamic field type without polluting actual field names with type indicators

Hi All, By default Solr allows you to define the type of a dynamic field by appending a post-fix to the name itself. E.g. creating a color_s field instructs Solr to create a string field. My understanding is that if we do this, all queries must refer the post-fixed field name as well. So instead

Re: Fwd: Solr Cloud 6.0.0 hangs when creating large amount of collections and node fails to recover after restart

2016-05-12 20:30 GMT+02:00 Shawn Heisey <apa...@elyograg.org>: > On 5/12/2016 9:08 AM, Horváth Péter Gergely wrote: > > As part of benchmark, I attempted to create about 2500 collections to > > see how well that would work for us. Unfortunately, the experiment > >

Planning and benchmarking Solr: resource consumption (RAM, disk, CPU, number of nodes)

Hi All, I am wondering if there is any recommendation or convention regarding planning and benchmarking a Solr node / Solr Cloud cluster infrastructure. I am looking for a somewhat more structured approach than trying with our forecast data volumes and keep adding more resources (CPU, RAM, disk

Re: Re-indexing in SolRCloud while keeping the collection online -- Best practice?

gt; to point "hot" to "col2". Now you can delete col1. There are > no restrictions on where these collections live, so this > allows you to move your collections around as you want. Plus > this keeps a better separation of old and new data... > > Best

Re-indexing in SolRCloud while keeping the collection online -- Best practice?

Hi Everyone, I am wondering if there is any best practice regarding re-indexing documents in SolrCloud 6.0.0 without making the data (or the underlying collection) temporarily unavailable. Wiping all documents in a collection and performing a full re-indexing is not a viable alternative for us.