StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17961892
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-07-31T04:55:06.697
FavoriteCount
0
LastActivityDate
2013-07-31T19:56:39.603
LastEditDate
2013-07-31T19:56:39.603
LastEditorUserId
2452461
OwnerUserId
2452461
ParentId
17960966
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Take a look at this from <a href="http://www.elasticsearch.org/guide/reference/index-modules/analysis/ngram-tokenizer/" rel="nofollow">the es docs on nGram token filters</a>: <pre><code> "settings" : { "analysis" : { "analyzer" : { "my_ngram_analyzer" : { "tokenizer" : "my_ngram_tokenizer" } }, "tokenizer" : { "my_ngram_tokenizer" : { "type" : "nGram", "min_gram" : "2", "max_gram" : "3", "token_chars": [ "letter", "digit" ] } } } } </code></pre> A few things to note <ol> <li>You need to add <code>mynGram</code> to your analyzer or it won't be used. They way it works is like this. Each indexed field has an analyzer applied to it, an analyzer is one tokenizer followed by zero or more token filters. You have defined a nice nGram tokenizer (<code>mynGram</code>) to use, but you did not use it in <code>customAnalyzer</code>, it is using the <code>standard</code> tokenizer. (Basically you are just defining but never using <code>mynGram</code>.)</li> <li>You need to tell elasticsearch to use your <code>customAnalyzer</code> in your mapping: <code>"properties": {"string_field": {"type": "string", "index_analyzer": customAnalyzer" }}</code></li> <li>You should change the <code>maxGram</code> to a bigger number (maybe 10), otherwise 4 letter searches will not behave exactly as autocomplete (or could return nothing, depends on the search-time analyzer).</li> <li>Use the <code>_analyze</code> api endpoint to test your analyzer. Something line this should work. curl -XGET '<a href="http://yourserver.com:9200?index_name/_analyze?analyzer=customAnalyzer" rel="nofollow">http://yourserver.com:9200?index_name/_analyze?analyzer=customAnalyzer</a>' -d 'rlewis'</li> </ol> Good luck!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSpecifying and using a NGramTokenizer with the C# NEST client for Elastic Search
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USramseykhalaf
UserOwnerUserId
1. USramseykhalaf
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSpecifying and using a NGramTokenizer with the C# NEST client for Elastic Search
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COAnd as if by magic it works. I'll update the sample to show a fixed version for future reference. Thanks for the guidance.
 singulars
 PostPostId
 PO
 UserUserId
 USRLewis

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.