How does the SolrParams fill up directly? Shouldn't it be SolrQueryRequest
and not SolrParams, if I am not mistaken?
--
View this message in context:
http://lucene.472066.n3.nabble.com/embedding-solr-tp476484p2566785.html
Sent from the Solr - User mailing list archive at Nabble.com.
ng a search engine, but want to shift to SOLR to
> implement its inbuilt faceting feature.
>
> Any pointers in this regards would be really helpful.
>
> regards,
> Sumita
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Embedding-SOLR-in-Dot-NET-
your
application.You have to parse response and use into your application
-
Grijesh
--
View this message in context:
http://lucene.472066.n3.nabble.com/Embedding-SOLR-in-Dot-NET-Application-tp2197589p2197653.html
Sent from the Solr - User mailing list archive at Nabble.com.
static Singletons i (and many others i suspect) would be
> extremely gratefull .. both for how much it would improve hte reusability
> of Solr in embedded situatiosn like this, but also for how it would
> (hopefully) make hte code eaier to follow for future developers.
>
>
> -Hoss
>
>
>
--
View this message in context:
http://www.nabble.com/Embedding-Solr-vs-Lucene%2C-multiple-Solr-cores--tf3572324.html#a10020669
Sent from the Solr - User mailing list archive at Nabble.com.
: but does not want to deal with the application itself, leaving the 'business
: users' side administer it. Even if there is a dedicated Tomcat for the main
: app, IT will not let the 'business users' install other applications (scope
: of responsibility, code versus data, validation procedures, e
r performance hit is not
something I should be afraid of.
For the sake of completeness, instead of embedding Solr in that single
instance, I thought about using several Solr instances running in different
webapp instances & use them as 'coprocessors' for the main application; thi
destepping your stated requirements, but I'd take a long look
at that one.
BTW, We cut over from an embedded Lucene instance to Solr about 4 months
ago, and are very happy that we did.
Tom
On 4/13/07, Henrib <[EMAIL PROTECTED]> wrote:
I'm trying to choose between embedding Luce
On 4/13/07, Henrib <[EMAIL PROTECTED]> wrote:
I'm trying to choose between embedding Lucene versus embedding Solr in one
webapp.
In Solr terms, functional requirements would more or less lead to multiple
schema & conf (need CRUD/generation on those) and deployment constraints
i
I'm trying to choose between embedding Lucene versus embedding Solr in one
webapp.
In Solr terms, functional requirements would more or less lead to multiple
schema & conf (need CRUD/generation on those) and deployment constraints
imply one webapp instance. The choice I'm trying t
: core.execute( handler, sreq, rsp );
:
: IndexReader reader = sreq.getSearcher().getReader();
: DocListAndSet response = (DocListAndSet)rsp.getValues().get( "response" );
: DocIterator iter = response.docList.iterator();
: while( iter.hasNext() ) {
: Document doc = reader.document( i
That is good to hear. I guess I was overly worried when I saw your
mention of having trouble getting the field values with the correct
types. I will be taking a look at this later this week.
Thank you very much for your prompt response.
On 4/10/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Ther
There is nothing particularly magic to it. It is just fills up
SolrParams directly (see any of the tests) calling the requestHandler,
then walking through the Documents. Something like:
SolrRequestHandler handler = core.getRequestHandler( "" ); // gets
the standard one
SolrQueryResponse rsp
Ryan,
Do you have any of this code you could share? I am currently using
Solr to perform thousands of queries in a batch, and eliminating the
HTTP overhead is something I'd love to do if it isn't complicated. We
need several of the extra features Solr provides, which is why we are
trying to use
Yonik and Ryan,
Thank you for the quick and helpful responses. I'll have to do some
hacking from here on out and see where I get to, but I'm happy to
know I'm in good company and that what I'm attempting is on a path
already slightly worn. :)
Erik
On Apr 2, 2007, at 9:55 PM, Ry
I have embedded solr skipping HTTP transport altogether. It was
remarkably easy to link directly to request handlers skipping the
dispatch filter and using the DocList and associated data in the
SolrQueryResponse directly.
Assuming the existing TCP/IP interface is sending strings around,
filling
On 4/2/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
I have a client need to embed Solr behind an already built custom TCP/
IP interface (currently for Lucene, but want to swap in Solr to
benefit from its additional goodness of course). Have folks already
done this? Experiences? Or perhaps th
I have a client need to embed Solr behind an already built custom TCP/
IP interface (currently for Lucene, but want to swap in Solr to
benefit from its additional goodness of course). Have folks already
done this? Experiences? Or perhaps there are some thoughts on why
this may or may n
Certainly running a load balanced solr cluster will be our first
approach, I was just wondering if there were
any glaring problems with running solr embedded in each webapp node.
Sounds like there are not.
As for the secondary db lookup, those will be cached, and are necessary
to filter resul
On 6/7/06, Joachim Martin <[EMAIL PROTECTED]> wrote:
We are looking at running read-only solr nodes embedded in our webapp
nodes. This would give us the
additional features of solr over lucene, but would keep it in memory and
reduce the overhead of http/xml
transport of results.
Looks like we w
Hi,
We are looking at running read-only solr nodes embedded in our webapp
nodes. This would give us the
additional features of solr over lucene, but would keep it in memory and
reduce the overhead of http/xml
transport of results.
Looks like we would just create a request handler and call
h
20 matches
Mail list logo
