Hi
A noobie question. I am uncertain what is the best way to design for my
requirement which the following.
I want to allow another client in solrj to query solr with a query that is
handled with a custom handler
localhost:9090/solr/tokenSearch?tokens{!dismax
qf=content}pear,apples,oyster,kin
: did you, Hoss, not say that components are referred to by name? How
: could the search result be read from the query mySpecialQueryComponent
: if it cannot be named? Simply through the pool of SolrParams?
in the example i gave, "mySpecialQueryComponent" *is* the name of some
component you ha
Erm,
did you, Hoss, not say that components are referred to by name?
How could the search result be read from the query mySpecialQueryComponent if
it cannot be named? Simply through the pool of SolrParams?
If yes, that's the great magic of solr.
paul
Le 8 mars 2011 à 23:19, Chris Hostetter a
: So how do I define, for a given request-handler, a special query component?
: I did not find in this in the schema.
you mean solrocnfig.xml, again.
Taken directly from the SearchHandler URL i sent you...
> If you want to have a custom list of components (either omitting
> defaults or adding
A request handler can have first-components and last-components and also just
plain components. List all your stuff in components and voila. Don't forget to
also add debug, facet and other default components if you need them.
> Le 8 mars 2011 à 23:03, Chris Hostetter a écrit :
> > : in my schema
Le 8 mars 2011 à 23:03, Chris Hostetter a écrit :
> : in my schema I have
>
> First off, a bit of terminoligy clarification: Search COmponents are
> declarred in the solrconfig.xml file. schema.xml is where you define
> what, inherently, the data in your index *is*. solrocnfig.xml is where
: in my schema I have
First off, a bit of terminoligy clarification: Search COmponents are
declarred in the solrconfig.xml file. schema.xml is where you define
what, inherently, the data in your index *is*. solrocnfig.xml is where
you define how you want people to be able to interact with t
hello list,
in my schema I have
which, as I understand it, allows all requestHandlers to use my
query-component. That is useful but I wonder if there's a way for me to have
one request-handler that uses my query-component and another to use the default
one?
Formulated, differently, my
