highlight_query短いバージョン: 結果を強調表示するために提供される機能を取得することは何とか可能inner_hitsですか?
長いバージョン: 次のマッピングを検討してください:
{
"settings": {
"number_of_replicas": 0,
"number_of_shards": 1
},
"mappings": {
"docs": {
"properties": {
"doctext": {
"type": "string",
"store": "yes"
},
"sentences": {
"type": "nested",
"properties": {
"text": {
"type": "string",
"store": "yes"
}
}
}
}
}
}
}
ご覧のとおり、doctextとsentencesフィールドがあります。アイデアは、ドキュメントのテキストを文に分割して、文ベースの検索を可能にするというものです。
これをドキュメントの例とします:
{
"doctext": "I will do a presentation. I talk about lions and show images of zebras. I hope it will be fun.",
"sentences": [
{
"text": "I will do a presentation."
},
{
"text": "I talk about lions and show images of zebras."
},
{
"text": "I hope it will be fun."
}
]
}
これで、テキスト全体と単一の文を検索でき、両方を強調表示することもできます。
{
"query": {
"bool": {
"should": [
{
"match": {
"doctext": "zebras"
}
},
{
"nested": {
"path": "sentences",
"query": {
"match": {
"sentences.text": "zebras"
}
},
"inner_hits": {
"highlight": {
"fields": {
"sentences.text": {}
}
}
}
}
}
]
}
},
"_source": false,
"highlight": {
"fields": {
"doctext": {
"highlight_query": {
"match": {
"doctext": "lions"
}
}
}
}
}
}
次のことはしないでください。
- 上の
nestedクエリsentences - その
inner_hitsクエリの部分 - の
highlight_query部分ではなく、秒highlightの部分inner_hits
このクエリを発行すると、次の応答が返されます。
"hits": [
{
"_index": "documents",
"_type": "docs",
"_id": "123456",
"_score": 0.6360315,
"highlight": {
"doctext": [
"I will do a presentation. I talk about <em>lions</em> and show images of zebras. I hope it will be fun."
]
},
"inner_hits": {
"sentences": {
"hits": {
"total": 1,
"max_score": 0.5291085,
"hits": [
{
"_index": "documents",
"_type": "docs",
"_id": "123456",
"_nested": {
"field": "sentences",
"offset": 1
},
"_score": 0.5291085,
"_source": {
"text": "I talk about lions and show images of zebras."
},
"highlight": {
"sentences.text": [
"I talk about lions and show images of <em>zebras</em>."
]
}
}
]
}
}
}
}
]
zebrasdoctextを検索したにもかかわらず、フィールドではlionsが強調表示されていることに注意してください。他に行うことを指定していないため、do はそれらを強調しています。しかし、ハイライトと同じように、内側のヒットでlionsをハイライトしたいです。inner_hitsdoctext
inner_hitsクエリの一部を次のように変更しようとしました
"inner_hits": {
"highlight": {
"fields": {
"text": {
"highlight_query": {
"match": {
"sentences.text": "lions"
}
}
}
}
}
}
ただし、これにより次の例外が発生します。
Failed to execute phase [query_fetch], all shards failed; shardFailures {[9-pMHRPsRiyITgsRNFnkEA][documents][0]: RemoteTransportException[[Fafnir][127.0.0.1:9300][indices:data/read/search[phase/query+fetch]]]; nested: SearchParseException[failed to parse search source [{
"query": {
"bool": {
"should": [
{
"match": {
"doctext": "fun"
}
},
{
"nested": {
"path": "sentences",
"query": {
"match": {
"sentences.text": "zebras"
}
},
"inner_hits": {
"highlight": {
"fields": {
"sentences.text": {
"highlight_query": {
"match": {
"doctext": "lions"
}
}
}
}
}
}
}
}
]
}
},
"_source": false,
"highlight": {
"fields": {
"doctext": {
"highlight_query": {
"match": {
"doctext": "lions"
}
}
}
}
}
}]]; nested: NullPointerException; }
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.onFirstPhaseResult( TransportSearchTypeAction.java:228)
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction$1.onFailure( TransportSearchTypeAction. java:174)
at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:46)
at org.elasticsearch.transport.TransportService$DirectResponseChannel.processException(TransportService.java:821)
at org.elasticsearch.transport.TransportService$DirectResponseChannel.sendResponse(TransportService.java:799)
at org.elasticsearch.transport.TransportService$4.onFailure(TransportService.java:361)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:42)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: ; nested: NullPointerException;
at org.elasticsearch.ElasticsearchException.guessRootCauses(ElasticsearchException.java:382)
at org.elasticsearch.action.search.SearchPhaseExecutionException.guessRootCauses(SearchPhaseExecutionException. java:152)
at org.elasticsearch.action.search.SearchPhaseExecutionException.getCause(SearchPhaseExecutionException.java:99)
at java.lang.Throwable.printStackTrace(Throwable.java:665)
at java.lang.Throwable.printStackTrace(Throwable.java:721)
at org.apache.log4j.DefaultThrowableRenderer.render(DefaultThrowableRenderer.java:60)
at org.apache.log4j.spi.ThrowableInformation.getThrowableStrRep(ThrowableInformation.java:87)
at org.apache.log4j.spi.LoggingEvent.getThrowableStrRep(LoggingEvent.java:413)
at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:313)
at org.apache.log4j.WriterAppender.append(WriterAppender.java:162)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
at org.apache.log4j.Category.callAppenders(Category.java:206)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.log(Category.java:856)
at org.elasticsearch.common.logging.log4j.Log4jESLogger.internalInfo(Log4jESLogger.java:125)
at org.elasticsearch.common.logging.support.AbstractESLogger.info(AbstractESLogger.java:90)
at org.elasticsearch.rest.BytesRestResponse.convert(BytesRestResponse.java:131)
at org.elasticsearch.rest.BytesRestResponse.<init>(BytesRestResponse.java:96)
at org.elasticsearch.rest.BytesRestResponse.<init>(BytesRestResponse.java:87)
at org.elasticsearch.rest.action.support.RestActionListener.onFailure(RestActionListener.java:60)
at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.raiseEarlyFailure( TransportSearchTypeAction.java:316)
... 10 more
Caused by: java.lang.NullPointerException
at org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(QueryParseContext.java:258)
at org.elasticsearch.index.query.BoolQueryParser.parse(BoolQueryParser.java:116)
at org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(QueryParseContext.java:257)
at org.elasticsearch.index.query.IndexQueryParserService.innerParse(IndexQueryParserService.java:303)
at org.elasticsearch.index.query.IndexQueryParserService.parse(IndexQueryParserService.java:206)
at org.elasticsearch.index.query.IndexQueryParserService.parse(IndexQueryParserService.java:201)
at org.elasticsearch.search.query.QueryParseElement.parse(QueryParseElement.java:33)
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:831)
at org.elasticsearch.search.SearchService.createContext(SearchService.java:651)
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:617)
at org.elasticsearch.search.SearchService.executeFetchPhase(SearchService.java:460)
at org.elasticsearch.search.action.SearchServiceTransportAction$SearchQueryFetchTransportHandler.messageReceived( SearchServiceTransportAction.java:392)
at org.elasticsearch.search.action.SearchServiceTransportAction$SearchQueryFetchTransportHandler.messageReceived( SearchServiceTransportAction.java:389)
at org.elasticsearch.transport.TransportService$4.doRun(TransportService.java:350)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
... 3 more
これを機能させる方法はありますか？これで DSL を間違えたのでしょうか? inner_hits強調表示が機能する状態のみに関するドキュメント( https://www.elastic.co/guide/en/elasticsearch/reference/2.1/search-request-inner-hits.html ) はありますが、詳細には触れていません。
読んでくれて、ヒントをくれてどうもありがとう！