Rafalovitch [mailto:arafa...@gmail.com]
Sent: Thursday, December 31, 2015 12:24 PM
To: solr-user
Subject: RE: Testing Solr configuration, schema, and other fields
Well, I guess NIH stands for Not Invented Here. No idea what NLM is for.
P.s. sorry, could not resist. I worked for orgs like that too :-
year, maybe not.
>
> -Original Message-
> From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
> Sent: Thursday, December 31, 2015 11:40 AM
> To: solr-user
> Subject: Re: Testing Solr configuration, schema, and other fields
>
> Makes sense.
>
> Answering
nd Glacier. Maybe we'll negotiate EC2 for dev
later this year, maybe not.
-Original Message-
From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
Sent: Thursday, December 31, 2015 11:40 AM
To: solr-user
Subject: Re: Testing Solr configuration, schema, and other fields
Makes sense.
beddedSolrServer.
>
> -Original Message-
> From: Erik Hatcher [mailto:erik.hatc...@gmail.com]
> Sent: Thursday, December 31, 2015 10:00 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Testing Solr configuration, schema, and other fields
>
> Dan - I’m a fan of the idea o
eking the
> wisdom of the crowd.
>
> -Original Message-
> From: Alexandre Rafalovitch [mailto:arafa...@gmail.com]
> Sent: Thursday, December 31, 2015 12:42 AM
> To: solr-user
> Subject: Re: Testing Solr configuration, schema, and other fields
>
> I might be just confu
.com]
Sent: Thursday, December 31, 2015 12:42 AM
To: solr-user
Subject: Re: Testing Solr configuration, schema, and other fields
I might be just confused here, but I am not sure what your bottle neck actually
is. You seem to know your critical path already, so how can we help?
Starting new
Message-
From: Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Thursday, December 31, 2015 10:00 AM
To: solr-user@lucene.apache.org
Subject: Re: Testing Solr configuration, schema, and other fields
Dan - I’m a fan of the idea of using EmbeddedSolrServer for the type of thing
you mention, but sin
Dan - I’m a fan of the idea of using EmbeddedSolrServer for the type of thing
you mention, but since you’re already using SolrCloud how about simply
upconfig’ing the configuration from the Git repo, create a temporary collection
using that configset and smoke test it before making it ready for e
I might be just confused here, but I am not sure what your bottle neck
actually is. You seem to know your critical path already, so how can we
help?
Starting new solr core from given configuration directory is easy. Catching
hard errors from that is probably just gripping logs or a custom logger.
ornin...@grayhairsoftware.com]
> Sent: Wednesday, December 30, 2015 3:25 PM
> To: solr-user@lucene.apache.org
> Subject: RE: Testing Solr configuration, schema, and other fields
>
> Daniel,
>
>
> Sounds almost like you're reinventing the wheel. Could you possibly aut
are.com]
> Sent: Wednesday, December 30, 2015 3:25 PM
> To: solr-user@lucene.apache.org
> Subject: RE: Testing Solr configuration, schema, and other fields
>
> Daniel,
>
>
> Sounds almost like you're reinventing the wheel. Could you possibly automate
> this through
[mailto:mhornin...@grayhairsoftware.com]
Sent: Wednesday, December 30, 2015 3:25 PM
To: solr-user@lucene.apache.org
Subject: RE: Testing Solr configuration, schema, and other fields
Daniel,
Sounds almost like you're reinventing the wheel. Could you possibly automate
this through puppet or
Daniel,
Sounds almost like you're reinventing the wheel. Could you possibly automate
this through puppet or Chef? With a VDI environment, then all you would need
to do is build a new VM Node based on original setup. Then you can just roll
out the node as one of the zk nodes.
Just a thought
13 matches
Mail list logo
