[ 
https://issues.apache.org/jira/browse/SOLR-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18045178#comment-18045178
 ] 

Eric Pugh commented on SOLR-7913:
---------------------------------

I am looking at the current state of stream.url and stream.file with an eye to 
removing them.   It appears that MLT though requires or wants them?  

 

The docs that I see for this feature are at 
[https://solr.apache.org/guide/solr/latest/query-guide/morelikethis.html#query-parser-for-external-content.]
   Would it be possible to get a more complete example and I don't get from 
reading it how you substitute exteranl content in...   

I see the text "find docs similar to an external content absent in index in 
SolrCloud mode like {{/mlt}} handler and content streams" but it isn't quite 
clicking.   Would we instead use a streaming expression?

 

I also think that having a replacement for the global stream.body that was 
specific to this feature would be perfectly fine.  mlt.stream.body?

> Add stream.body support to MLT QParser
> --------------------------------------
>
>                 Key: SOLR-7913
>                 URL: https://issues.apache.org/jira/browse/SOLR-7913
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Anshum Gupta
>            Priority: Major
>         Attachments: SOLR-7913.patch, SOLR-7913.patch, SOLR-7913.patch, 
> SOLR-7913.patch, SOLR-7913_fix-unit-test-setup.patch, 
> SOLR-7913_fixTests.patch, SOLR-7913_negative-tests.patch, 
> SOLR-7913_tag_7.5.0.patch, SOLR-7913_tag_lucene-solr-8.7.0.patch
>
>
> Continuing from 
> https://issues.apache.org/jira/browse/SOLR-7639?focusedCommentId=14601011&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14601011.
> It'd be good to have stream.body be supported by the mlt qparser.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to