This article shouldn't flat out make the decision for you, but these concerns
raised by the guys at StackOverflow (over SQL Server 2008) helped guide us
toward Solr:
http://www.infoq.com/news/2008/11/SQL-Server-Text
--
Hector
On Dec 7, 2011, at 2:17 AM, Mersad wrote:
> hi Everyone,
>
Hi Shiv,
For me, a combination of the following has helped me learn a lot about Solr in
a short period of time:
* Apache Solr 3 Enterprise Search Server:
http://www.packtpub.com/apache-solr-3-enterprise-search-server/book
* Solr Wiki: http://wiki.apache.org/solr/
* Pretty much every single pos
Hi,
Has anyone had success with multicore single node Solr configurations that have
one core acting solely as a dispatcher for the other cores? For example, say
you had 4 populated Solr cores – configure a 5th to be the definitive endpoint
with `shards` containing cores 1-4.
Is there any ad
of randomly querying a shard, because we will
> get randomly different results.
>
> ShlomiJ
>
> On Tue, Jan 10, 2012 at 2:15 AM, Hector Castro wrote:
>
>> Hi,
>>
>> Has anyone had success with multicore single node Solr configurations that
>> have one c
ecide in which shard to index a document, using a
> plugable hashing method.
>
> What do you think?
>
> ShlomiJ
>
> On Tue, Jan 10, 2012 at 6:15 PM, Shawn Heisey wrote:
>
>> On 1/9/2012 5:15 PM, Hector Castro wrote:
>>
>>> Hi,
>>>
&g
t seems to
suggest that you're better off setting rows=5000 instead of chunking by 100.
Is that correct?
--
Hector
On Wednesday, January 11, 2012 at 7:10 PM, Ken Krugler wrote:
> Hi Hector,
>
> On Jan 9, 2012, at 4:15pm, Hector Castro wrote:
>
> > Hi,
> >
&g
As Tommaso said, adding a field to the schema.xml gives you an automatic
timestamp set at index time. The default schema.xml with Solr 3.5.0 has a
commented example:
--
Hector
On Jan 20, 2012, at 8:15 AM, Tommaso Teofili wrote:
> Hi Alex,
> you can create a field in the schema.xml o
