So, the stopwords.txt file is different between the two systems - the first
has stop words but the second does not. Did you expect stop words to be
removed, or not?
-- Jack Krupansky
-Original Message-
From: Stavros Delsiavas
Sent: Wednesday, October 16, 2013 5:02 PM
To: solr-user
, or some field type analyzers can
use the stop filter and some would not have it. This does mean that you
would have to use different field types for fields that want different stop
word processing.
-- Jack Krupansky
-Original Message-
From: Stavros Delisavas
Sent: Thursday, October 17
ction against simple name fields is a misuse of the language detection
feature. I mean, it is designed for larger blocks of text, not very short
phrases.
See some examples in my e-book.
-- Jack Krupansky
-Original Message-
From: vibhoreng04
Sent: Friday, October 18, 2013 2:01 PM
To: solr
that the update log be enabled using
.
-- Jack Krupansky
-Original Message-
From: Brent Ryan
Sent: Friday, October 18, 2013 4:59 PM
To: solr-user@lucene.apache.org
Subject: SOLRJ replace document
How do I replace a document in solr using solrj library?
Sorry, but Latin is not on the list of supported languages:
https://code.google.com/p/language-detection/wiki/LanguageList
-- Jack Krupansky
-Original Message-
From: vibhoreng04
Sent: Friday, October 18, 2013 3:07 PM
To: solr-user@lucene.apache.org
Subject: Re: Issues with Language
By all means please do file a support request with DataStax, either as an
official support ticket or as a question on StackOverflow.
But, I do think the previous answer of avoiding the use of a Map object in
your document is likely to be the solution.
-- Jack Krupansky
-Original Message
the generated
class, org.apache.solr.parser.SolrQueryParserBase.java.
Good luck! Happy hunting!
-- Jack Krupansky
-Original Message-
From: YouPeng Yang
Sent: Monday, October 21, 2013 2:57 AM
To: solr-user@lucene.apache.org
Subject: Class name of parsing the fq clause
Hi
I search the solr with fq clause,which is like:
fq=BEGI
Did you completely reindex your data after emptying the stop words file?
-- Jack Krupansky
-Original Message-
From: Stavros Delisavas
Sent: Monday, October 21, 2013 10:05 AM
To: solr-user@lucene.apache.org
Subject: Re: Local Solr and Webserver-Solr act differently ("and" tre
Take a look at the unit tests for various "value sources", and find a Jira
that added some value source and look at the patch for what changes had to
be made.
-- Jack Krupansky
-Original Message-
From: JT
Sent: Monday, October 21, 2013 1:17 PM
To: solr-user@lucene.apache.o
Hopefully at the end of the week.
-- Jack Krupansky
-Original Message-
From: fudong li
Sent: Monday, October 21, 2013 1:45 PM
To: solr-user@lucene.apache.org
Subject: Re: Custom FunctionQuery Guide/Tutorial (4.3.0+) ?
Hi Jack,
Do you have a date for the new version of your book
quot;catid:{123}"? If you are simply trying
to pass the braces as literal characters for a string field, either escape
them with backslash or enclose the entire term in quotes:
catid:\{123\}
catid:"{123}"
-- Jack Krupansky
-Original Message-
From: Peter Kirk
Sent: We
Not in just a few words. Do you have specific questions? I mean none of that
relates to parsing of fq, the topic of this particular email thread, right?
-- Jack Krupansky
-Original Message-
From: Sandeep Gupta
Sent: Wednesday, October 23, 2013 3:58 AM
To: solr-user@lucene.apache.org
ution? Either
way, it may be reasonably satisfactory, but some clarity would help. Thanks!
-- Jack Krupansky
-Original Message-
From: Otis Gospodnetic
Sent: Wednesday, October 23, 2013 1:28 PM
To: solr-user@lucene.apache.org
Subject: New query-time multi-word synonym expander
Hi,
Heads up
Trailing wildcard should work fine for strings, but "a23*" will not match
"A23*" due to case. You could use the keyword tokenizer plus the lower case
filter.
-- Jack Krupansky
-Original Message-
From: Bruno Mannina
Sent: Wednesday, October 23, 2013 1
Yes, that blog post appears to use the proper technique for case insensitive
string fields.
The so-called "keyword" tokenizer merely treats the whole string value as a
single token (AKA keyword) and does NOT do any further tokenization.
-- Jack Krupansky
-Original Message-
that uses the keyword tokenizer to maintain a single token but also applies
a regex filter to strip special characters and applies a lower case filter
and give that an intermediate boost.
-- Jack Krupansky
-Original Message-
From: johnmu...@aol.com
Sent: Thursday, October 24, 2013 9
Download redirects to 4.5.0
Is there a typo in the server path?
On Thu, Oct 24, 2013 at 9:14 AM, Mark Miller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> October 2013, Apache Solr™ 4.5.1 available
>
> The Lucene PMC is pleased to announce the release of Apache Solr 4.5.1
>
> Solr
Use a different server than default gets 4.5.1
On Thu, Oct 24, 2013 at 9:35 AM, Jack Park wrote:
> Download redirects to 4.5.0
> Is there a typo in the server path?
>
> On Thu, Oct 24, 2013 at 9:14 AM, Mark Miller wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash:
packet:: clientPath:null
serverPath:null finished:false header:: 1,3 replyHeader:: 1,541,0
request:: '/clusterstate.json,F response::
s{20,522,1382659358606,1382660557980,19,0,0,0,1072,0,20}
There seem to be several issues:
address family not supported
Unable to locate a login configuration
Does any of that ring any bells?
Many thanks in advance
Jack
rties file in
the conf subdirectory of the core.
-- Jack Krupansky
-Original Message-
From: marotosg
Sent: Friday, October 25, 2013 11:26 AM
To: solr-user@lucene.apache.org
Subject: Re: Global User defined properties - solr.xml from Solr 4.4 to Solr
4.5
Hi Erik. thanks for your help
returned on queries. You could use a regex replacement or write a
JavaScript script with a stateless script update processor to do more
extensive mapping.
-- Jack Krupansky
-Original Message-
From: Bruno Mannina
Sent: Friday, October 25, 2013 11:08 AM
To: solr-user@lucene.apache.org
Subject
Nothing of great significance that I have heard of, yet. Solr 4.x has lots
of ongoing significant improvements and will likely to have a lot more in
the months ahead. Ditto with Lucene improvements - lots of ongoing work to
enhance 4.x.
-- Jack Krupansky
-Original Message-
From
My e-book does describe all of the "configuration elements" of solrconfig in
some detail.
-- Jack Krupansky
-Original Message-
From: Amit Aggarwal
Sent: Friday, October 25, 2013 6:19 AM
To: solr-user@lucene.apache.org
Subject: Please explain SolConfig.xml in terms of Solr
Yes, it is unfortunate that the "properties" property was removed.
-- Jack Krupansky
-Original Message-
From: marotosg
Sent: Friday, October 25, 2013 12:52 PM
To: solr-user@lucene.apache.org
Subject: Re: Global User defined properties - solr.xml from Solr 4.4 to Solr
4.5
But a lot of that big yellow elephant stuff is in 4.x anyway.
(Otis: I was afraid that you were going to say that the next big thing in
Solr is... Elasticsearch!)
-- Jack Krupansky
-Original Message-
From: Otis Gospodnetic
Sent: Friday, October 25, 2013 2:43 PM
To: solr-user
. Neither
installation shows a log4j log file anywhere.
I have reason to believe I followed all the instructions in the
ZooKeeper Getting Started page accurately. Still, no real cigar...
Java on windoz is 1.6.0_31; on ubuntu it is 1.7.0_40
Thanks in advance for any hints.
On Thu, Oct 24, 2013 at
.
-- Jack Krupansky
-Original Message-
From: neerajp
Sent: Saturday, October 26, 2013 12:50 PM
To: solr-user@lucene.apache.org
Subject: Indexing on plain text data and base64 encode data in a single HTTP
POST request
Hi,
I am using Solr for searching my email data. My application is in C
place in the
desired field. And finally remove any temporary fields.
-- Jack Krupansky
-Original Message-
From: David Anthony Troiano
Sent: Monday, October 28, 2013 4:47 PM
To: solr-user@lucene.apache.org
Subject: Single multilingual field analyzed based on other field values
Hello
There are some detailed examples in my e-book as well.
-- Jack Krupansky
-Original Message-
From: Erwin Gunadi
Sent: Tuesday, October 29, 2013 8:21 AM
To: solr-user@lucene.apache.org
Subject: RE: Solr Highlighting Best Practices Guideline
Hi Furkan,
thanks for the reply.
I was
You need some parentheses:
title:john doe^30 OR description:john doe^10
should be:
title:(john doe)^30 OR description:(john doe)^10
-- Jack Krupansky
-Original Message-
From: michael.boom
Sent: Tuesday, October 29, 2013 7:20 AM
To: solr-user@lucene.apache.org
Subject: Phrase query
cores for the bulk data
for each tenant, but have a single common collection with a subset of tenant
data which your admin application can use to do searches across tenants for
common metadata.
-- Jack Krupansky
-Original Message-
From: Alejandro Calbazana
Sent: Tuesday, October 29
e.org/solr/4_5_1/solr-core/org/apache/solr/update/processor/UniqFieldsUpdateProcessorFactory.html
My e-book has more examples as well.
-- Jack Krupansky
-Original Message-
From: Anupam Bhattacharya
Sent: Wednesday, October 30, 2013 6:05 AM
To: solr-user@lucene.apache.org
Subject: Atomic
dated for 4.5 yet, but the gist of
the examples is the same.)
-- Jack Krupansky
-Original Message-
From: Jack Krupansky
Sent: Wednesday, October 30, 2013 9:03 AM
To: solr-user@lucene.apache.org
Subject: Re: Atomic Updates in SOLR
Unfortunately, atomic "add" is add to a "l
Escape any special characters with a backslash, or put the full term in
quotes.
-- Jack Krupansky
-Original Message-
From: jihyun suh
Sent: Wednesday, October 30, 2013 6:28 AM
To: solr-user@lucene.apache.org
Subject: query with colon in bq
I have a question about query with colon in
e.
fl=id,name,my-func(field1),my-func(field2)
-- Jack Krupansky
-Original Message-
From: Alejandro Calbazana
Sent: Wednesday, October 30, 2013 10:10 AM
To: solr-user@lucene.apache.org
Subject: Computing Results So That They are Returned in Search Results
I'd like to throw out a desi
example of exactly what you want.
-- Jack Krupansky
-Original Message-
From: Alejandro Calbazana
Sent: Wednesday, October 30, 2013 12:46 PM
To: solr-user@lucene.apache.org
Subject: Re: Computing Results So That They are Returned in Search Results
Sounds really close to what I'm lookin
Maybe your schema has "omitted" position information for the "text" field
which is required to query phrases. That would throw an exception on every
server for a distributed query. Still, that does seem like an odd exception
for a simple query problem.
-- Jack Krupansky
-
.
Fascinating, what? This must be a common beginner's question, not
well covered in web-search for my context. Does it ring any bells?
Many thanks.
Jack
the simple one-box
3-node cloud test, and used the test code from the Lucidworks course
to send over and read some documents. That failed with this:
Unknown document router '{name=compositeId}'
Lots more research.
Closer...
On Thu, Oct 31, 2013 at 5:44 PM, Jack Park wrote:
> Latest zo
you using?
>
> Alan Woodward
> www.flax.co.uk
>
>
> On 1 Nov 2013, at 04:19, Jack Park wrote:
>
>> After digging deeper (slow for a *nix newbee), I uncovered issues with
>> the java installation. A step in installation of Oracle Java has it
>> that you -ins
ection reset by peer would suggest something in my code, but my
code is a clone of code supplied in a Solr training course. Must be
good. Right?
I also have no clue what is /127.0.0.1:39065 -- that's not one of my nodes.
The quest continues.
On Fri, Nov 1, 2013 at 9:21 AM, Jack Park wrote
,
because those servers actually exist, to the test harness, at
10.1.10.178, and if I access any one of them from the browser,
/solr/collection1 does not work, but /solr/#/collection1 does work.
On Fri, Nov 1, 2013 at 10:34 AM, Jack Park wrote:
> /clusterstate.json seems to clearly state that al
-cloud mode.
Thanks
Jack
On Fri, Nov 1, 2013 at 11:12 AM, Shawn Heisey wrote:
> On 11/1/2013 12:07 PM, Jack Park wrote:
>>
>> The top error message at my test harness is this:
>>
>> No live SolrServers available to handle this request:
>> [http://127.0.1.1:8983/solr
"document " + i);
doc.addField( "details", "This is document " + i);
server.add(doc);
The error is thrown at server.add(doc)
Many thanks in advance for any observations or suggestions.
Cheers
Jack
everything work.
On Sun, Nov 3, 2013 at 12:04 PM, Jack Park wrote:
> I now have a single ZK running standalone on 2121. On the same CPU, I
> have three nodes.
>
> I used a curl to send over two documents, one each to two of the three
> nodes in the cloud. According to a web query, th
Is it possible that you added stored="true" later, after some of the
documents were already indexed? Then the older documents would not have the
stored values. If so, you need to reindex the older documents.
-- Jack Krupansky
-Original Message-
From: gohome190
Sent: Monday
;resourceURL:*" will find all of them, but there is this question:
What does the query look like to find that specific URL?
Of course, "resourceURL:http://someotherserver.org/"; doesn't work
This one
resourceURL=http%3A%2F%2Fsomeotherserver.org%2F
fails as well.
What am I overlooking?
Many thanks in advance.
Jack
Spoke too soon. Hacking rocks!
Finally landed on this heuristic, and it works:
resourceURL:"http://someotherserver.org/";
On Thu, Nov 7, 2013 at 9:52 AM, Jack Park wrote:
> Figuring out a google query to gain an answer seems difficult given
> the ambiguity;
>
> I have
Thanks for the plug Erick, but my deep dive doesn't go quite that deep
(yet.)
But I'm sure a 2,500 page book on how to develop all manner of custom Solr
plugin would indeed be valuable though.
But I do have plenty of example of using the many builtin Solr analysis
filters.
easier to master.
-- Jack Krupansky
-Original Message-
From: Ryan Cutter
Sent: Monday, November 11, 2013 10:18 AM
To: solr-user@lucene.apache.org
Subject: Re: Unit of dimension for solr field
I think Upayavira's suggestion of writing a filter factory fits what you're
Any kind of cross-field processing is best done in an update processor.
There are a lot of built-in update processors as well as a JavaScript script
update processor.
-- Jack Krupansky
-Original Message-
From: Dileepa Jayakody
Sent: Tuesday, November 12, 2013 1:31 AM
To: solr-user
se is
already in Java, why do you need JSON? The real purpose of a JSON response
is usually simply to more easily map it to Java (or JavaScript.)
-- Jack Krupansky
-Original Message-
From: Dharmendra Jaiswal
Sent: Tuesday, November 12, 2013 4:54 AM
To: solr-user@lucene.apache.org
Subject: H
of config settings.
-- Jack Krupansky
From: Abhijith Jain -X (abhijjai - DIGITAL-X INC at Cisco)
Sent: Tuesday, November 12, 2013 7:22 PM
To: solr-user@lucene.apache.org
Subject: Modify the querySearch to q=*:*
Hello,
I upgraded Solr to 4.4.0(previous Solr version was 3.5). After the full
see how the parameters are
being processed.
-- Jack Krupansky
-Original Message-
From: Abhijith Jain -X (abhijjai - DIGITAL-X INC at Cisco)
Sent: Tuesday, November 12, 2013 8:03 PM
To: solr-user@lucene.apache.org
Subject: RE: Modify the querySearch to q=*:*
Thanks for the quick reply. I
ments that
have a value in the default search field. In many cases this would give
identical results to a *:* query, but in some apps it might not.
Still it would be nice to know who originated this suggestion to use *\*
instead of *:* - or even simply *.
-- Jack Krupansky
-Original Me
I believe it is the TZ column from this table:
http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
Yeah, it's on my TODO list for my book.
I suspect that "tz" will not affect "NOW", which is probably UTC. I suspect
that "tz" only affects literal date
is complaining that there is no matching .
-- Jack Krupansky
-Original Message-
From: Marcello Lorenzi
Sent: Thursday, November 14, 2013 9:26 AM
To: solr-user@lucene.apache.org
Subject: Solr xml img parsing exception
Hi,
I have installed a Solr 4.3 instance and we have configured ma
the update processor as a JavaScript script. The
simplest approach to the query side would be to expand the special query
syntax in your application layer.
-- Jack Krupansky
-Original Message-
From: giridhar
Sent: Thursday, November 14, 2013 10:45 AM
To: solr-user@lucene.apache.org
S
s/work/word/
"word delimiter filter"
-- Jack Krupansky
-Original Message-----
From: Jack Krupansky
Sent: Thursday, November 14, 2013 11:34 AM
To: solr-user@lucene.apache.org
Subject: Re: Query on multi valued field
I suppose you could define the field as tokenized text wit
You could use an update processor to map non-ASCII codes to SGML entities.
You could code it as a JavaScript script and use the stateless script update
processor.
-- Jack Krupansky
-Original Message-
From: Developer
Sent: Tuesday, November 19, 2013 5:46 PM
To: solr-user
ly, you don't really not to AND with a
sub-query, so make it:
-endtime:"1970-01-01T01:00:00Z"
And then it is simply a clause of the Boolean query.
-- Jack Krupansky
-Original Message-
From: vishalgupta084
Sent: Wednesday, November 20, 2013 7:31 AM
To: solr-user@lucene.a
Any analysis filtering affects the indexed value only, but the stored value
would be unchanged from the original input value. An update processor lets
you modify the original input value that will be stored.
-- Jack Krupansky
-Original Message-
From: Uwe Reh
Sent: Wednesday
AFAICT, it's not an "extremely bad idea" - using SGML/HTML as a format for
storing text to be rendered. If you disagree - try explaining yourself.
But maybe TM should be encoded as "™". Ditto for other named SGML
entities.
-- Jack Krupansky
-Original Message
t; the query in the manner that you're describing.
Or, simply settle for a "heuristic" approach that may give you 70% of what
you want using only existing Solr features on the server side.
-- Jack Krupansky
-Original Message-
From: Mirko
Sent: Thursday, November
and a better description.
-- Jack Krupansky
-Original Message-
From: Ahmet Arslan
Sent: Thursday, November 21, 2013 11:40 AM
To: solr-user@lucene.apache.org
Subject: Re: search with wildcard
Hi Adnreas,
If you don't want to use wildcards at query time, alternative way is to use
N
But all of this begs the question of the original question: "I need to store
the HTML Entity (decimal) equivalent value (i.e. ™) in SOLR rather
than storing the original value."
Maybe the original poster could clarify the nature of their need.
-- Jack Krupansky
-Original Message-
e for basic display, and one for "detail"
display.
I'm more of a "platform" guy than an "app-specific" guy - give the app
developer tools that they can blend to meet their own requirements (or
interests or tastes.)
But Solr users should make no mistake, SGML e
"Would you store "a" as "A" ?"
No, not in any case.
-- Jack Krupansky
-Original Message-
From: Michael Sokolov
Sent: Thursday, November 21, 2013 8:56 AM
To: solr-user@lucene.apache.org
Subject: Re: How to index X™ as ™ (HTML decimal entity)
I have to a
it is completely safe to use and save Lucene document IDs, but
only as long as no merging of segments is performed. Even one tiny merge and
all subsequent saved document IDs are invalidated. Be careful with your
merge policy - normally merges are happening in the background,
automatically.
-
consumed by
an application.
-- Jack Krupansky
-Original Message-
From: kumar
Sent: Tuesday, November 26, 2013 3:31 AM
To: solr-user@lucene.apache.org
Subject: Re: Storing solr results in excel
If we specify wt=csv then results appear like csv format but i need to store
them in seperate
round it with an update processor that copied the field and
massaged the multiple values into what you really want the language
detection to see. You could even implement that processor as a JavaScript
script with the stateless script update processor.
-- Jack Krupansky
-Original Me
Just bite the bullet and do the query at your application level. I mean,
Solr/Lucene would have to do the same amount of work internally anyway. If
the perceived performance overhead is too great, get beefier hardware.
-- Jack Krupansky
-Original Message-
From: Thomas Scheffler
Sent
That information would be included in the debugQuery output as well.
-- Jack Krupansky
-Original Message-
From: Jamie Johnson
Sent: Wednesday, November 27, 2013 9:32 AM
To: solr-user@lucene.apache.org
Subject: Term Vector Component Question
I am interested in retrieving the tf
is used, it won't tell you which term matched -
although a tf value of 0 basically tells you that.
-- Jack Krupansky
-Original Message-
From: Jamie Johnson
Sent: Wednesday, November 27, 2013 11:38 AM
To: solr-user@lucene.apache.org
Subject: Re: Term Vector Component Question
Jack,
To be honest, this kind of question comes up so often, that it probably is
worth a Jira to have a more customized or parameterized "explain".
Function queries in the "fl" list give you a lot more control, but not at
the level of actual terms that matched.
-- Jack Krup
What do you really want to do/accomplish? I mean, for what purpose?
You can turn on the Lucene infostream for logging of index writing.
See:
https://cwiki.apache.org/confluence/display/solr/IndexConfig+in+SolrConfig
Set to "true".
There are some examples in my e-book.
-- Jack
If you have chosen to use improper field names, then in the fl parameter you
need to reference them using the "field" function:
fl=id,field(01text)
The basic concept is that Solr doesn't ban improper field names, but that
they don't work in all contexts.
-- Jack Krup
Yeah, purely negative sub-queries have had problems, so rewrite:
fq = (access:Allow*) OR (-access:*)
as
fq = (access:Allow*) OR (*:* -access:*)
-- Jack Krupansky
-Original Message-
From: Thomas Kurz
Sent: Thursday, November 28, 2013 10:34 AM
To: solr-user@lucene.apache.org
Subject
Any chance that you had already indexed some data before your finalized
these configuration settings? That pre-existing data would need to be
manually reindexed for the update processor to be effective.
-- Jack Krupansky
-Original Message-
From: Dishanker Raj
Sent: Friday, November
The edismax (ExtendedDisMax) query parser is the best, overall. There are
other specialized query parsers with features that edismax does not have
(e.g., surround for span queries, and complex phrase for wildcards in
phrases.)
-- Jack Krupansky
-Original Message-
From: elmerfudd
he classic query parser.
-- Jack Krupansky
-Original Message-
From: Karsten R.
Sent: Tuesday, December 03, 2013 1:24 AM
To: solr-user@lucene.apache.org
Subject: Using the flexible query parser in Solr instead of classic
Hi folks,
last year we built a 3.X Solr-QueryParse
Ah... although the lower case filtering does get applied properly in a
"multiterm" analysis scenario, stemming does not. What stemmer are you
using? I suspect that "swimming" normally becomes "swim". Compare the debug
output of the two queries.
-- Jack Kr
Note that the synonym filter accepts a comma-separated list of synonym
files, so you can split your huge synonym file into two or more smaller
files.
-- Jack Krupansky
-Original Message-
From: gf80
Sent: Wednesday, December 11, 2013 5:21 PM
To: solr-user@lucene.apache.org
Subject
Just use the edismax query parser with bigrams and trigrams enabled and the
default operator set to OR. That will select all sentences even vaguely
similar and will more highly score sentences that have a greater number of
words and phrases that match.
-- Jack Krupansky
-Original Message
Do a proof of concept implementation and see for yourself if you find the
performance acceptable.
I mean, performance should be reasonably decent.
-- Jack Krupansky
-Original Message-
From: Jayni
Sent: Friday, December 13, 2013 12:22 PM
To: solr-user@lucene.apache.org
Subject: Re
top-level query typically defaults to matching all documents, or
"*:*", so if you want that effect, use:
docKey:*:*
Two other possibilities:
docKey:* -- all documents with a value in the field
*:* -docKey:* -- all documents with no value in the field
-- Jack Krupansky
-Origin
That's a feature of the standard tokenizer. You'll have to use a field type
which uses the white space tokenizer to preserve special characters.
-- Jack Krupansky
-Original Message-
From: suren
Sent: Thursday, December 19, 2013 10:56 AM
To: solr-user@lucene.apache.org
Su
to have multiple documents
with the same unique ID (which is now no longer unique.)
Tell us a little more about your data model and why you chose it.
-- Jack Krupansky
-Original Message-
From: neerajp
Sent: Friday, December 20, 2013 12:57 AM
To: solr-user@lucene.apache.org
Subject
Wouldn't it be better or at least easier to simply filter out the
unacceptable phrases before you send them to Solr for indexing?
-- Jack Krupansky
-Original Message-
From: Jorge Luis BetancourtGonzález
Sent: Saturday, December 21, 2013 3:05 AM
To: solr-user@lucene.apache.org
Su
on those four fields with a boost,
although I'm not sure a boost will be of any value in the case of a dismax
which is providing an exact match anyway.
-- Jack Krupansky
-Original Message-
From: rashi gandhi
Sent: Tuesday, December 31, 2013 8:15 AM
To: solr-user@lucene.apach
The defType parameter applies only to the q parameter, not to fq, so you
will need to explicitly give the query parser for fq:
fq={!queryparsername}filterquery
-- Jack Krupansky
-Original Message-
From: suren
Sent: Thursday, January 02, 2014 7:32 PM
To: solr-user@lucene.apache.org
Or just use the internal document ID: fl=*,[docid]
Granted, the docID may change if a segment merge occurs and earlier
documents have been deleted, but it may be sufficient for your purposes.
-- Jack Krupansky
-Original Message-
From: Upayavira
Sent: Friday, January 03, 2014 5:58
for both scaling of query response
and availability if nodes go down.
-- Jack Krupansky
-Original Message-
From: rashmi maheshwari
Sent: Tuesday, January 28, 2014 11:36 AM
To: solr-user@lucene.apache.org
Subject: Solr & Nutch
Hi,
Question1 --> When Solr could parse html, documen
ince
they are on different machines.)
-- Jack Krupansky
-Original Message-
From: Susheel Kumar
Sent: Sunday, January 26, 2014 10:54 AM
To: solr-user@lucene.apache.org
Subject: RE: Solr server requirements for 100+ million documents
Thank you Erick for your valuable inputs. Yes, we have t
not
match.
-- Jack Krupansky
-Original Message-
From: Aleksander Akerø
Sent: Wednesday, January 29, 2014 9:55 AM
To: solr-user@lucene.apache.org
Subject: Re: KeywordTokenizerFactory - trouble with "exact" matches
update:
Guessing that this has nothing to do with the tokenizer
What field type and analyzer/tokenizer are you using?
-- Jack Krupansky
-Original Message-
From: Thomas Michael Engelke
Sent: Wednesday, January 29, 2014 10:45 AM
To: solr-user@lucene.apache.org
Subject: Not finding part of fulltext field when word ends in dot
Hello everybody
Thank you for taking a look.
2014-01-29 Jack Krupansky
What field type and analyzer/tokenizer are you using?
-- Jack Krupansky
-Original Me
!field f=myfield}Foo Bar
See:
http://wiki.apache.org/solr/QueryParser
You can also pre-configure the field query parser with the defType=field
parameter.
-- Jack Krupansky
-Original Message-
From: Srinivasa7
Sent: Thursday, January 30, 2014 6:37 AM
To: solr-user@lucene.ap
,
it would treat "26KA" as "26" AND "KA" AND "26KA", which requires that
"26KA" (without the trailing dot) to be in the index.
It seems counter-intuitive, but the attributes of the index and query word
delimiter filters need to be slightly asymm
Lucene's default scoring should give you much of what you want - ranking
hits of low-frequency terms higher - without any special query syntax - just
list out your terms and use "OR" as your default operator.
-- Jack Krupansky
-Original Message-
From: svante karlsson
601 - 700 of 2693 matches
Mail list logo
