: Using EmbeddedSolrServer is a client side way of communicating with
: Solr via the file system. Solr has to still be up and running before
: that. My question is more along the lines of how to put the server
Eh ... no it isn't. EmbeddedSolrServer is an abstraction that lets
applications writte
Pulkit Singhal wrote:
Using EmbeddedSolrServer is a client side way of communicating with
Solr via the file system. Solr has to still be up and running before
that. My question is more along the lines of how to put the server
jars that perform the core functionality and bundle them to start up
wi
Using EmbeddedSolrServer is a client side way of communicating with
Solr via the file system. Solr has to still be up and running before
that. My question is more along the lines of how to put the server
jars that perform the core functionality and bundle them to start up
within a war which is also
On 2/18/2010 4:22 PM, Pulkit Singhal wrote:
Hello Everyone,
I do NOT want to host Solr separately. I want to run it within my war
with the Java Application which is using it. How easy/difficult is
that to setup? Can anyone with past experience on this topic, please
comment.
thanks,
- Pulkit
Yeah I have been pitching that but I want all the functionality of
Solr in a small package because it is not a concern given the
specifically limited data set being searched upon. I understand that
the # of users is still another part of this equation but there just
aren't that many at this time an
Why would you want to? Surely having it seperate increases scalablity?
On 18 Feb 2010, at 22:23, "Pulkit Singhal"
wrote:
> Hello Everyone,
>
> I do NOT want to host Solr separately. I want to run it within my war
> with the Java Application which is using it. How easy/difficult is
> that to se
