StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17484544
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-07-05T08:36:03.890
FavoriteCount
0
LastActivityDate
2014-01-08T08:10:22.530
LastEditDate
2014-01-08T08:10:22.530
LastEditorUserId
633239
OwnerUserId
633239
ParentId
17467135
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I would suggest you to look at your requirements regarding boosting, since your current script doesn't make much sense. Also, have a look at the documentation for the elasticsearch <a href="http://www.elasticsearch.org/guide/reference/query-dsl/" rel="nofollow">query DSL</a>. It provides either compound queries and simple ones, which you can combine together. As the error says, you can't put a filter inside a custom score query. You can either use a <a href="http://www.elasticsearch.org/guide/reference/query-dsl/filtered-query/" rel="nofollow">filtered query</a> inside the custom score query: <pre><code>{ "query": { "custom_score": { "query": { "filtered" : { "query" : { "match": { "xxx": { "query": "foobar" } } }, "filter" : { "and": [ { "query": { "match": { "yyyy": { "query": "barfoo" } } } } ] } } }, "script": "_score * doc['_score']" } } } </code></pre> or use a top level <a href="http://www.elasticsearch.org/guide/reference/api/search/filter/" rel="nofollow">filter</a> like this: <pre><code>{ "query": { "custom_score": { "query": { "match": { "xxx": { "query": "foobar" } } }, "script": "_score * doc['_score']" } }, "filter": { "and": [ { "query": { "match": { "yyyy": { "query": "barfoo" } } } } ] } } </code></pre> The difference between the two options is that the top level filter is not considered if you make facets too in your search request, while if you put the filters within the query they are considered. One other thing to look at: you don't need an and filter if you have only a single clause. Also, it usually doesn't make sense to put a full-text search within a filter, since filters are cacheable and given that full-text searches are free and pretty much unpredictable it would be a waste to cache them.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO_score while doing indexing in elasticsearch
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USjavanna
UserOwnerUserId
1. USjavanna
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PO_score while doing indexing in elasticsearch
 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. 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.