Tulsi wrote
> Can you post the managed schema and solrconfig content here ?
Schema for the 4.6 index (I omitted all non-relevant data):
Can you post the managed schema and solrconfig content here ?
Do try the solr admin analysis screen
once as well to see the behaviour for this field.
https://lucene.apache.org/solr/guide/7_6/index.html
On Sun, 27 Dec, 2020, 6:54 pm nettadalet, wrote:
> Thank you, that was helpful!
>
> For Solr
Hi,
thank for the comment, but I tried to use both "sow=false" and "saw=true"
and I still get the same result. For query (TITLE_ItemCode_t:KI_7) I still
see:
Solr 4.6: "parsedquery": "PhraseQuery(TITLE_ItemCode_t:\"ki 7\")"
Solr 7.5: "parsedquery":"+(+(TITLE_ItemCode_t:ki7 (+TITLE_ItemCode_t:ki
+TI
SOW default to false?
but this seems to be true right??
For Solr 7.5 I get
"parsedquery":"+(+(text1:ki7 (+text1:ki
+text1:7)))"
At 2020-12-28 01:13:29, "Tulsi Das" wrote:
>Hi ,
>Yes this look like related to sow (split on whitespace) param default
>behaviour change in solr 7.
>
>T
Hi ,
Yes this look like related to sow (split on whitespace) param default
behaviour change in solr 7.
The sow parameter (short for "Split on Whitespace") now defaults to
false, which allows support for multi-word synonyms out of the box.
This parameter is used with the eDismax and standard/"lucen
I added "defType=lucene" to both searches to make sure I use the same query
parser, but it didn't change the results.
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
I'm not sure how to check the implementation of the query parser, or how to
change the query parser that I use. I think I'm using the standard query
parser.
I use Solr Admin to run the queries. If I look at the URL, I see
Solr 4.6:
select?q=TITLE_ItemCode_t:KI_7&fl=TITLE_ItemCode_t
Solr 7.5:
selec
which query parser are you using? I think to answer your question, you need to
check the implementation of the query parser
At 2020-12-27 21:23:59, "nettadalet" wrote:
>Thank you, that was helpful!
>
>For Solr 4.6 I get
>"parsedquery": "PhraseQuery(TITLE_ItemCode_t:\"ki 7\")"
>
Thank you, that was helpful!
For Solr 4.6 I get
"parsedquery": "PhraseQuery(TITLE_ItemCode_t:\"ki 7\")"
For Solr 7.5 I get
"parsedquery":"+(+(TITLE_ItemCode_t:ki7 (+TITLE_ItemCode_t:ki
+TITLE_ItemCode_t:7)))"
So this is the cause of the difference in the search result, but I still
don't know wh
ch with both versions, I get different results, and I don't know why
>
> I have the following *field type definition in Solr 4.6*:
> positionIncrementGap="1000">
>
>
>
> words="s
Hello,
I have the the same field type defined in Solr 4.6 and Solr 7.5. When I
search with both versions, I get different results, and I don't know why
I have the following *field type definition in Sol
> : I am going to adjust my schema, re-index, and try again. See if that
> : doesn't fix this problem. I didn't know that having the uniqueKey be a
> : textField was a bad idea.
>
>
> https://lucene.apache.org/solr/guide/8_3/other-schema-elements.html#OtherSchemaElements-UniqueKey
>
> "The fieldTyp
: > whoa... that's not normal .. what *exactly* does the fieldType declaration
: > (with all analyzers) look like, and what does the declaration
: > look like?
: >
: >
:
:
:
NOTE: "text_general" != "text_gen_sort"
Assuming your "text_general" declaration looks like it does in the
_default
On Tue, Nov 12, 2019 at 12:18 PM Chris Hostetter
wrote:
>
> : > a) What is the fieldType of the uniqueKey field in use?
> : >
> :
> : It is a textField
>
> whoa... that's not normal .. what *exactly* does the fieldType declaration
> (with all analyzers) look like, and what does the declaration
>
: > a) What is the fieldType of the uniqueKey field in use?
: >
:
: It is a textField
whoa... that's not normal .. what *exactly* does the fieldType declaration
(with all analyzers) look like, and what does the declaration
look like?
you should really never use TextField for a uniqueKey ...
On Mon, Nov 11, 2019 at 8:32 PM Chris Hostetter
wrote:
>
> Based on the info provided, it's hard to be certain, but reading between
> the lines here are hte assumptions i'm making...
>
> 1) your core name is "dbtr"
> 2) the uniqueId field for the "dbtr" core is "debtor_id"
>
> ..are those assumpt
Based on the info provided, it's hard to be certain, but reading between
the lines here are hte assumptions i'm making...
1) your core name is "dbtr"
2) the uniqueId field for the "dbtr" core is "debtor_id"
..are those assumptions correct?
Two key pieces of information that doesn't seem to be
i am using this logic in perl:
my $decoded = decode_json( $solrResponse->{_content} );
my $numFound = $decoded->{response}{numFound};
$cursor = "*";
$prevCursor = '';
while ( $prevCursor ne $cursor )
{
my $solrURI = "\"http://[SOLR URL]:8983/solr/";
$solrURI .= $fdat{core};
$solrSort = (
earch bar, I get "."
> as the "*most interesting term*" boosted by the highest order usually. I
> can't figure out how to remove this from interesting terms without removing
> it from the field I am searching in.
>
> 2) I have 2 shards per collections on two nodes
his from interesting terms without removing
it from the field I am searching in.
2) I have 2 shards per collections on two nodes 8983 and 7574 in cloud
mode. I am getting different results for same query.
I have come to know through reading forums and documentation that this is
happening due to
d vs non-distributed return different results for this??
From: solr-user@lucene.apache.org At: 09/19/19 06:20:30To:
solr-user@lucene.apache.org
Subject: Solr query fetching different results
Hi all,
There is something "strange' happening in our Solr cluster. If I execute a
query from t
Multiple replicas of the same shard will execute their autocommits at
different wall clock times.
Thus there may be a _temporary_ time when newly-indexed document is
found by a query that
happens to get served by replica1 but not by replica2. If you have a
timestamp in the doc, and
a soft commit in
Hi all,
There is something "strange' happening in our Solr cluster. If I execute a
query from the server, via solarium client, I get one result. If I execute
the same or similar query from admin Panel, I get another result. If I go
to Admin Panel - Collections - Select Collection and click "Reloa
> lend themselves to being optimized what is the best approach for these?
>
> Thanks
>
> On Fri, Sep 8, 2017 at 9:47 AM, Shawn Heisey wrote:
>
>> On 9/7/2017 8:54 AM, Webster Homer wrote:
>> > I am not concerned about deleted documents. I am concerned that the s
gt; > search gives different results after each search. The top document seems
> to
> > cycle between 3 different documents
> >
> > I have an enhanced collections info api call that calls the core admin
> api
> > to get the index information for the replica.
>
On 9/7/2017 8:54 AM, Webster Homer wrote:
> I am not concerned about deleted documents. I am concerned that the same
> search gives different results after each search. The top document seems to
> cycle between 3 different documents
>
> I have an enhanced collections info api call
> This was not the first time. This particular situation was on a
> development
> >> system
> >>
> >> On Thu, Sep 7, 2017 at 10:04 AM, Webster Homer
> >> wrote:
> >>
> >>> the scores are not the same
> >>> Doc
> >>> 30534
rote:
>>
>>> the scores are not the same
>>> Doc
>>> 305340 432.44238
>>>
>>> On Thu, Sep 7, 2017 at 10:02 AM, David Hastings <
>>> hastings.recurs...@gmail.com> wrote:
>>>
>>>> "I am concerned that the same
>&
Sep 7, 2017 at 10:02 AM, David Hastings <
>> hastings.recurs...@gmail.com> wrote:
>>
>>> "I am concerned that the same
>>> search gives different results after each search. The top document seems
>>> to
>>> cycle between 3 different documents&
s.recurs...@gmail.com> wrote:
>
>> "I am concerned that the same
>> search gives different results after each search. The top document seems
>> to
>> cycle between 3 different documents"
>>
>>
>> if you do debug query on the search, are the s
the scores are not the same
Doc
305340 432.44238
On Thu, Sep 7, 2017 at 10:02 AM, David Hastings <
hastings.recurs...@gmail.com> wrote:
> "I am concerned that the same
> search gives different results after each search. The top document seems to
> cycle between 3 different
"I am concerned that the same
search gives different results after each search. The top document seems to
cycle between 3 different documents"
if you do debug query on the search, are the scores for the top 3 documents
the same or not? you can easily have three documents with the same
I am not concerned about deleted documents. I am concerned that the same
search gives different results after each search. The top document seems to
cycle between 3 different documents
I have an enhanced collections info api call that calls the core admin api
to get the index information for the
Whew! I haven't been lying to people for _years_..
On Thu, Sep 7, 2017 at 5:58 AM, Yonik Seeley wrote:
> On Thu, Sep 7, 2017 at 12:47 AM, Erick Erickson
> wrote:
>> bq: and deleted documents are irrelevant to term statistics...
>>
>> Did you mean "relevant"? Or do I have to adjust my thinki
On Thu, Sep 7, 2017 at 12:47 AM, Erick Erickson wrote:
> bq: and deleted documents are irrelevant to term statistics...
>
> Did you mean "relevant"? Or do I have to adjust my thinking _again_?
One can make it work either way ;-)
Whether a document is marked as deleted or not has no effect on term
bq: and deleted documents are irrelevant to term statistics...
Did you mean "relevant"? Or do I have to adjust my thinking _again_?
Erick
On Wed, Sep 6, 2017 at 7:48 PM, Yonik Seeley wrote:
> Different replicas of the same shard can have different numbers of
> deleted documents (really just mar
Different replicas of the same shard can have different numbers of
deleted documents (really just marked as deleted), and deleted
documents are irrelevant to term statistics (like the number of
documents a term appears in). Documents marked for deletion stop
contributing to corpus statistics when
I am using Solr 6.2.0 configured as a solr cloud with 2 shards and 4
replicas (total of 4 nodes).
If I run the query multiple times I see the three different top scoring
results.
No data load is running, all data has been commited
I get these three different hits with their scores:
copperiinitrat
Hi guys,
I have the Suggester configured using the FreeTextFactory. Noticed that if
I dont use quotation marks, I only get single term results. If i use
quotation marks around my query, then I only get results that are comprised
of multiple terms. There is no configuration that would return both t
e. If this is true, skip the rest of this message. I only
>>>> realized we may be using a different definition of "different hits"
>>>> part way through writing this reply.
>>>>
>>>>
>>>>
>>>> H
, you can do something
>>> very similar with wildcards and the like if it's a string that sorts
>>> the same way the timestamp would. And it's best if it's created
>>> upstream anyway that way it's guaranteed to be the same for the doc on
>>> al
t;> copyfield to a date field would do the trick.
>>
>> But there's no real reason to do any of that. Given that you see this
>> when there's no indexing going on then there's no point to those
>> tests, those were just for a way to examine your nodes whi
-consistent. That is, all the replicas for shardN on the source
> cluster show the same documents (M). All the replicas for shardN on
> the target cluster show the same number of docs (N). I'm not as
> concerned if M != N at this point. Note I'm looking at the number of
>
looking at the number of
hits here, not say the document ordering.
To do this you'll have to do the trick I mentioned where you query
each replica separately.
And are you absolutely sure that your different results are coming
from the _same_ cluster? If you're comparing a query from th
son
wrote:
> The commit points on different replicas will trip at different wall
> clock times so the leader and replica may return slightly different
> results depending on whether doc X was included in the commit on one
> replica but not on the second. After the _next_ commit interva
The commit points on different replicas will trip at different wall
clock times so the leader and replica may return slightly different
results depending on whether doc X was included in the commit on one
replica but not on the second. After the _next_ commit interval (2
seconds in your case), doc
We are using Solr Cloud 6.2
We have been noticing an issue where the index in a core shows as current =
false
We have autocommit set for 15 seconds, and soft commit at 2 seconds
This seems to cause two replicas to return different hits depending upon
which one is queried.
What would lead to the
Hi,
different results are obtained for a query separated by comma and one separated
by whitespace,
"q":"foo,bar",
"q":"foo bar",
although solr.StandardTokenizerFactory is utilized. The eDisMax Query Parser is
used.
Fields of interest are determine
: I have a fresh install of Solr 5.2.1 with about 3 million docs freshly
: indexed (I can also reproduce this issue on 4.10.0). When I use the Solr
: MorelikeThisHandler with content stream I'm getting different results per
: shard.
I haven't looked at the code recently but i'm 9
I have a fresh install of Solr 5.2.1 with about 3 million docs freshly
indexed (I can also reproduce this issue on 4.10.0). When I use the Solr
MorelikeThisHandler with content stream I'm getting different results per
shard.
I also looked at using a standard MLT query, but I need to be ab
Though I am interacting with Dawid (creator of Carrot2) on Carrot2 mailing
list however just wanted to post my problem to a wider audience.
I am using Solr 4.7 (on both windows and linux) and saved my
lingo-attributes.xml file from the workbench which I am using in Solr. Note
that for testing I am
ing house which gives
zero results.
It really took sometime to figure this out, I hope this will help someone
else.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Join-and-non-Join-query-give-different-results-tp4146922p4148131.html
Sent from the Solr - User mailing list arch
hat satisfy the given filter queries.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Join-and-non-Join-query-give-different-results-tp4146922.html
Sent from the Solr - User mailing list archive at Nabble.com.
get this to
work, but it works for now.
Thanks again to you all.
O. O.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Debug-different-Results-from-different-Request-Handlers-tp4141804p4142716.html
Sent from the Solr - User mailing list archive at Nabble.com.
s show which is the Query Parser? I can post more of my
> solrconfig.xml if necessary.
>
> I am curious where the Query Parser hands over the parameters to the Solr
> engine that would be common irrespective of Request Handler i.e. I am trying
> to put debugging statements in
ould be common irrespective of Request Handler i.e. I am trying
to put debugging statements into the common code so that these can dump out
intermediate results to the log.
Thanks again Erik.
O. O.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Debug-different-Results-from-dif
at 22:44, "O. Olson" wrote:
>
> Hi,
>
> In my solrcofig.xml I have one Request Handler displaying the results using
> Apache Velocity:
>
>
>
> And another with regular XML:
> class="org.apache.solr.handler.component.SearchHandler">
Hi,
In my solrcofig.xml I have one Request Handler displaying the results using
Apache Velocity:
And another with regular XML:
I am seeing different results when I use these two handlers.
Search Query: hp|lync (Or on the URL q=hp%7Elync)
I see 0 results when I use the first handler
Thanks Shawn and Jack,
I changed solrconfig to set defaul query field (qf) to field content. It
works fine now.
Erol Akarsu
On Mon, Dec 3, 2012 at 5:03 PM, Shawn Heisey wrote:
> On 12/3/2012 1:44 PM, Erol Akarsu wrote:
>
>> I tried as search query not "baş" but "features:baş" in field "q" in
On 12/3/2012 1:44 PM, Erol Akarsu wrote:
I tried as search query not "baş" but "features:baş" in field "q" in SOLR
GUI. And, I got result!
In the one document, I had some fields type of text_eng, text_general and
one field features type of text_tr. If I don't specify field name, SOLR use
Engli
r use a "df" request
parameter or change the "df" default value for the request handler in the
solrconfig.xml.
-- Jack Krupansky
-Original Message-
From: Erol Akarsu
Sent: Monday, December 03, 2012 3:44 PM
To: solr-user@lucene.apache.org
Subject: Re: Luke and SOLR searc
m "features" to "text". You use the
>> "text_tr" field type for "features", but probably not for the "text" field.
>>
>>
>> -- Jack Krupansky
>>
>> -Original Message- From: Erol Akarsu
>> Sent: Monday
type for "features", but probably not for the "text" field.
>
>
> -- Jack Krupansky
>
> -Original Message- From: Erol Akarsu
> Sent: Monday, December 03, 2012 1:06 PM
>
> To: solr-user@lucene.apache.org
> Subject: Re: Luke and SOLR search giving different r
quot;, but probably not for the "text" field.
-- Jack Krupansky
-Original Message-
From: Erol Akarsu
Sent: Monday, December 03, 2012 1:06 PM
To: solr-user@lucene.apache.org
Subject: Re: Luke and SOLR search giving different results
Jack,
I have already set tomcat server fr
also reports for index analysis.
>
> -- Jack Krupansky
>
> -Original Message- From: Erol Akarsu
> Sent: Monday, December 03, 2012 11:35 AM
>
> To: solr-user@lucene.apache.org
> Subject: Re: Luke and SOLR search giving different results
>
> Jack,
>
> Yes.
>
> I
for index analysis.
-- Jack Krupansky
-Original Message-
From: Erol Akarsu
Sent: Monday, December 03, 2012 11:35 AM
To: solr-user@lucene.apache.org
Subject: Re: Luke and SOLR search giving different results
Jack,
Yes.
I expect SOLR should give same search results as Luked does.
ight the problem for you or not? Is the term analyzed
> as you expected?
>
> -- Jack Krupansky
>
> From: Erol Akarsu
> Sent: Monday, December 03, 2012 8:44 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Luke and SOLR search giving different results
>
> Jack,
&
So, does that highlight the problem for you or not? Is the term analyzed as you
expected?
-- Jack Krupansky
From: Erol Akarsu
Sent: Monday, December 03, 2012 8:44 AM
To: solr-user@lucene.apache.org
Subject: Re: Luke and SOLR search giving different results
Jack,
Thanks for help.
I removed
eindex if you change ANYTHING in the schema fields
> or field types.
>
> -- Jack Krupansky
>
> From: Erol Akarsu
> Sent: Sunday, December 02, 2012 10:38 PM
> To: solr-user@lucene.apache.org
> Subject: Luke and SOLR search giving different results
>
> Hi,
>
> I
, December 02, 2012 10:38 PM
To: solr-user@lucene.apache.org
Subject: Luke and SOLR search giving different results
Hi,
I am trying to apply SOLR for Turkish Language for my research.
Instead of using language identification, I manually assigned Turkish language
for a sample test document. I have
is inserted to SOLR database.
But searching for raw Lucene index through Luke and SOLR 4.0 search though
GUI is giving different results. In picture Selection_006.png, the word "baş"
is listed as top term. I search the word "baş" in Luke and I got the result
result that is onl
you are right about wildcards and analysis stuff...
so any way of putting wildcards in for analysis?
-
Zeki ama calismiyor... Calissa yapar...
--
View this message in context:
http://lucene.472066.n3.nabble.com/synonyms-txt-different-results-on-admin-and-on-site-tp3318338p3322026.html
chains, synonym expansion errors, etc, but folks will likely
>> need more details to help you out.
>>
>> cheers,
>> rob
>>
>> On Wed, Sep 7, 2011 at 9:46 PM, deniz <denizdurmu...@gmail.com>
>> wrote:
>>> could it be related with analysis issue
with analysis issue about synonyms once again?
>>
>>
>>
>> -
>> Zeki ama calismiyor... Calissa yapar...
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/synonyms-txt-different-results-on-admin-and-on-site-tp3318338p3318464.html
>> Sent fr
:
> could it be related with analysis issue about synonyms once again?
>
>
>
> -
> Zeki ama calismiyor... Calissa yapar...
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/synonyms-txt-different-results-on-admin-and-on-site-tp3318338p331846
could it be related with analysis issue about synonyms once again?
-
Zeki ama calismiyor... Calissa yapar...
--
View this message in context:
http://lucene.472066.n3.nabble.com/synonyms-txt-different-results-on-admin-and-on-site-tp3318338p3318464.html
Sent from the Solr - User mailing
written in php, i got nothing when i
use one of the synonyms that i have added.
any ideas why this is happening?
-
Zeki ama calismiyor... Calissa yapar...
--
View this message in context:
http://lucene.472066.n3.nabble.com/synonyms-txt-different-results-on-admin-and-on-site-tp3318338p3318338
That was it! thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Searching-similar-values-for-same-field-results-in-different-results-tp2199269p2206087.html
Sent from the Solr - User mailing list archive at Nabble.com.
ase="true" expand="true"/>
> words="stopwords_dutch.txt"/>
> generateWordParts="1"
> generateNumberParts="1" catenateWords="0" catenateNumbers="0"
> catenateAll="0" splitOnCaseChange="1&
ield value: "Kasteel en Landgoed"
and schema.jsp, but I didnt see any weird results
Now, Im wondering what else it could be..
--
View this message in context:
http://lucene.472066.n3.nabble.com/Searching-similar-values-for-same-field-results-in-different-results-tp2199269p2205706.html
Sent from the Solr - User mailing list archive at Nabble.com.
%20en%20Landgoed%22&q=*:*&fl=id,title
> I get 0 results!!!
>
> why?!?
>
>
> definition in schema.xml:
>
>
> multiValued="true" />
> multiValued="true"/>
>
>
>
> Why are these results differing?
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Searching-similar-values-for-same-field-results-in-different-results-tp2199269p2199269.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
> uhm...how do I perform an optimize operation? :)
http://localhost:8983/solr/db/update/?optimize=true
uhm...how do I perform an optimize operation? :)
--
View this message in context:
http://lucene.472066.n3.nabble.com/Searching-similar-values-for-same-field-results-in-different-results-tp2199269p2199795.html
Sent from the Solr - User mailing list archive at Nabble.com.
> Something weird is happening.
>
> I have locations that can have 1 or more themes.
> A theme can be: "Kasteel en Landgoed", or a theme can be
> "Strand en Zee"
>
> I checked in the database, there are many locations that
> have 1 or more of
> these themes assigned to it.
>
> Also in the respon
ext:
http://lucene.472066.n3.nabble.com/Searching-similar-values-for-same-field-results-in-different-results-tp2199269p2199269.html
Sent from the Solr - User mailing list archive at Nabble.com.
--- On Wed, 12/22/10, satya swaroop wrote:
> From: satya swaroop
> Subject: Different Results..
> To: solr-user@lucene.apache.org
> Date: Wednesday, December 22, 2010, 10:44 AM
> Hi All,
> i am getting
> different results when i used with some escape keys..
>
i am getting different results when i used with some escape keys..
> for example:::
> 1) when i use this request
>http://localhost:8080/solr/select?q=erlang!ericson
> the result obtained is
>
>
> 2) when the request is
>
Hi All,
i am getting different results when i used with some escape keys..
for example:::
1) when i use this request
http://localhost:8080/solr/select?q=erlang!ericson
the result obtained is
2) when the request is
http://localhost
e
On 10/21/2010 04:47 PM, Mike Sokolov wrote:
I'm experiencing something really weird: I get different results
depending
on whether I specify wt=javabin, and retrieve using SolrJ, or
wt=xml. I
spent quite a while staring at query params to make sure everything
else is
the same, and they d
s?
-Mike
On 10/21/2010 04:47 PM, Mike Sokolov wrote:
I'm experiencing something really weird: I get different results depending
on whether I specify wt=javabin, and retrieve using SolrJ, or wt=xml. I
spent quite a while staring at query params to make sure everything else is
the sam
4:47 PM, Mike Sokolov wrote:
>
>> I'm experiencing something really weird: I get different results depending
>> on whether I specify wt=javabin, and retrieve using SolrJ, or wt=xml. I
>> spent quite a while staring at query params to make sure everything else is
>> the
Mike Sokolov wrote:
I'm experiencing something really weird: I get different results
depending on whether I specify wt=javabin, and retrieve using SolrJ,
or wt=xml. I spent quite a while staring at query params to make sure
everything else is the same, and they do seem to be. At first
I'm experiencing something really weird: I get different results
depending on whether I specify wt=javabin, and retrieve using SolrJ, or
wt=xml. I spent quite a while staring at query params to make sure
everything else is the same, and they do seem to be. At first I thought
the pr
I am interested in this as well ... Im also having the issue of understanding
if a result has been elevated by the QueryElevation component. It should like
SolrJ would need to know about some type of metadata contained within the docs
but I haven't seen SolrJ dealing w/ payloads specifically ye
I'm faceting with a two different query ranges while using addFacetQuery. I
wonder wether it's possible using SolrJ to extract the result of each query
range separately. Here's is an example:
addFacetQuery("price:[* TO 150]"); addFacetQuery("price:[151 TO 300]"); etc.
addFacetQuery("length:[* TO 5
I'm faceting with a two different query ranges while using addFacetQuery. I
wonder wether it's possible using SolrJ to extract the result of each query
range separately. Here's is my example:
addFacetQuery("price:[* TO 150]"); addFacetQuery("price:[151 TO 300]"); etc.
addFacetQuery("date:[* TO NOW
- Nutch
- Original Message
> From: Tushar_Gandhi
> To: solr-...@lucene.apache.org
> Sent: Wednesday, December 31, 2008 3:26:32 AM
> Subject: Different results return for capital and small letters.
>
>
> Hi,
>I am using solr 1.3.
> I am facing a problem with
97 matches
Mail list logo
