StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSOLR generates phrase queries on punctuation
primarykey
Id
15314460
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-09T18:39:17.947
FavoriteCount
1
LastActivityDate
2013-03-09T18:39:17.947
LastEditDate
LastEditorUserId
0
OwnerUserId
1315900
ParentId
0
PostTypeId
1
Score
2
ViewCount
469
LastEditorDisplayName
text
Body
I have the following analyzer chain in my SOLR 3.5 instance (although we don't have luceneMatch version set up): <pre><code><fieldtype name="text_pt" class="solr.TextField" positionIncrementGap="100" autoGeneratePhraseQueries="false"> <analyzer type="index"> <tokenizer class="solr.StandardTokenizerFactory" /> <filter class="solr.ASCIIFoldingFilterFactory" protected="protwords.txt" /> <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" preserveOriginal="1" catenateWords="1" catenateNumbers="1" catenateAll="0" /> <filter class="solr.LowerCaseFilterFactory" /> <filter class="solr.StopFilterFactory" ignoreCase="false" words="portugueseStopWords.txt" /> <filter class="solr.BrazilianStemFilterFactory" /> <filter class="solr.RemoveDuplicatesTokenFilterFactory" /> </analyzer> <analyzer type="query"> <tokenizer class="solr.StandardTokenizerFactory" /> <filter class="solr.ASCIIFoldingFilterFactory" protected="protwords.txt" /> <filter class="solr.SynonymFilterFactory" ignoreCase="true" synonyms="portugueseSynonyms.txt" expand="true" /> <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="0" preserveOriginal="1" catenateNumbers="0" catenateAll="0" protected="protwords.txt" /> <filter class="solr.LowerCaseFilterFactory" /> <filter class="solr.StopFilterFactory" ignoreCase="false" words="portugueseStopWords.txt" /> <filter class="solr.BrazilianStemFilterFactory" /> <filter class="solr.RemoveDuplicatesTokenFilterFactory" /> </analyzer> </fieldtype> </code></pre> Notice how we have the autoGeneratePhraseQueries="false". Apparently this should prevent the query parser from generating a phrase query when finding a punctuation symbol. However this is not happening. Look at the output of the &debugQuery: <pre><code><str name="querystring">title_search_pt:(looking,for peugeot)</str> <str name="parsedquery">+PhraseQuery(title_search_pt:"looking for") +title_search_pt:peugeot</str> </code></pre> As you can see that comma, although being tokenized correctly, now ends up as a phrase query. Lots of people copy paste text for searching (with punctuation), and under my logic punctuation should not mean "do a phrase query with that". How can I disable/prevent this from happening? The StandardTokenizer understands dots and commas perfectly and splits only when necessary (keeping hostnames, numbers, etc), so replacing all the punctuation on the client before querying SOLR is not an option, as I'd be loosing some important information. Thanks
Tags
<solr><lucene>
Title
SOLR generates phrase queries on punctuation
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFermin Silva
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POSOLR generates phrase queries on punctuation
 UserUserId
 USFermin Silva
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POSOLR generates phrase queries on punctuation
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.