: For both the SpellCheckComponent (SCC) and now for the new ClusteringComponent
: (SOLR-769) I think there are cases where the QueryComponent (QC) is not
: required. In the SpellCheckComponent case it is when building the spelling
: index. In the ClusteringComponent, it is possible to ask for d
Don't turn off the query component in those cases. In these cases,
the QC identifies what docs are to be used, just as in a user based
query. Just think of those other components as clients of the QC
output, and I think it makes sense. The application will know whether
it needs to deal w
hi Grant,
There may be cases where the user may not be interested in the
documents but there may be other components which are interested in
the search results. In 'tvrh' is an example. How do we take care of
that?
On Tue, Oct 21, 2008 at 8:59 PM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> FWIW,
FWIW, my last patch on SOLR-769 adds a check to see if QC is enabled,
with the default param set to true. Thus, you can send in
&query=false and it skips it.
On Oct 21, 2008, at 11:21 AM, Noble Paul നോബിള്
नोब्ळ् wrote:
+1
I can forsee a lot of components which does not need the
Query
+1
I can forsee a lot of components which does not need the
QueryComponent. SOLR-706 being one.
On Tue, Oct 21, 2008 at 8:39 PM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> On Oct 21, 2008, at 8:17 AM, Grant Ingersoll wrote:
>
>>
>> On Oct 20, 2008, at 11:35 PM, Otis Gospodnetic wrote:
>>
>>> T
On Oct 21, 2008, at 8:17 AM, Grant Ingersoll wrote:
On Oct 20, 2008, at 11:35 PM, Otis Gospodnetic wrote:
This is related to something I must have only day dreamed (dreamt?)
about, but not actually mentioned on solr-dev.
My feeling is we are moving Solr in a direction of a more general
we
unrelated to your question, but we should give a better error...
https://issues.apache.org/jira/browse/SOLR-435
On Oct 20, 2008, at 8:01 PM, Grant Ingersoll wrote:
For completeness, here's the NPE:
SEVERE: java.lang.NullPointerException
at org.apache.solr.common.util.StrUtils.splitSmar
On Oct 20, 2008, at 11:35 PM, Otis Gospodnetic wrote:
This is related to something I must have only day dreamed (dreamt?)
about, but not actually mentioned on solr-dev.
My feeling is we are moving Solr in a direction of a more general
web service that can host various NLP and ML components,
This is related to something I must have only day dreamed (dreamt?) about, but
not actually mentioned on solr-dev.
My feeling is we are moving Solr in a direction of a more general web service
that can host various NLP and ML components, and no longer only do IR/Lucene.
We see that with a few p
For completeness, here's the NPE:
SEVERE: java.lang.NullPointerException
at org.apache.solr.common.util.StrUtils.splitSmart(StrUtils.java:37)
at
org.apache.solr.search.OldLuceneQParser.parse(LuceneQParserPlugin.java:
104)
at org.apache.solr.search.QParser.getQuery(QParser.java
10 matches
Mail list logo
