[jira] [Commented] (SOLR-12569) Document SignificantTermsQParserPlugin
[ https://issues.apache.org/jira/browse/SOLR-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573782#comment-16573782 ] Joel Bernstein commented on SOLR-12569: --- The functionality is fully baked to work with the significantTerms Streaming Expression. It was never intended to be a customer facing query parser. > Document SignificantTermsQParserPlugin > -- > > Key: SOLR-12569 > URL: https://issues.apache.org/jira/browse/SOLR-12569 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Alexandre Rafalovitch >Assignee: Alexandre Rafalovitch >Priority: Major > Attachments: SOLR-12569.patch > > > SignificantTermsQParserPlugin was introduced at the same as significantTerms > stream source, but only the stream source was documented. > QParser should be documented too, especially since it can be used in > non-cloud mode and has to be used as fq (otherwise, it throws exception). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12569) Document SignificantTermsQParserPlugin
[ https://issues.apache.org/jira/browse/SOLR-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573464#comment-16573464 ] Joel Bernstein commented on SOLR-12569: --- Possibly but not in its current form. I think we'd need to think it through about what is the best approach for exposing this functionality in non-SolrCloud mode. > Document SignificantTermsQParserPlugin > -- > > Key: SOLR-12569 > URL: https://issues.apache.org/jira/browse/SOLR-12569 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Alexandre Rafalovitch >Assignee: Alexandre Rafalovitch >Priority: Major > Attachments: SOLR-12569.patch > > > SignificantTermsQParserPlugin was introduced at the same as significantTerms > stream source, but only the stream source was documented. > QParser should be documented too, especially since it can be used in > non-cloud mode and has to be used as fq (otherwise, it throws exception). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12569) Document SignificantTermsQParserPlugin
[ https://issues.apache.org/jira/browse/SOLR-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573280#comment-16573280 ] Alexandre Rafalovitch commented on SOLR-12569: -- Streaming Expressions are just for SolrCloud mode though, right? Does this not make sense at all for a standalone setup, still a very popular choice? > Document SignificantTermsQParserPlugin > -- > > Key: SOLR-12569 > URL: https://issues.apache.org/jira/browse/SOLR-12569 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Alexandre Rafalovitch >Assignee: Alexandre Rafalovitch >Priority: Major > Attachments: SOLR-12569.patch > > > SignificantTermsQParserPlugin was introduced at the same as significantTerms > stream source, but only the stream source was documented. > QParser should be documented too, especially since it can be used in > non-cloud mode and has to be used as fq (otherwise, it throws exception). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12569) Document SignificantTermsQParserPlugin
[ https://issues.apache.org/jira/browse/SOLR-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573111#comment-16573111 ] Joel Bernstein commented on SOLR-12569: --- I think we want people to consume this functionality through the significantTerms streaming expression. > Document SignificantTermsQParserPlugin > -- > > Key: SOLR-12569 > URL: https://issues.apache.org/jira/browse/SOLR-12569 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Alexandre Rafalovitch >Assignee: Alexandre Rafalovitch >Priority: Major > Attachments: SOLR-12569.patch > > > SignificantTermsQParserPlugin was introduced at the same as significantTerms > stream source, but only the stream source was documented. > QParser should be documented too, especially since it can be used in > non-cloud mode and has to be used as fq (otherwise, it throws exception). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-12569) Document SignificantTermsQParserPlugin
[ https://issues.apache.org/jira/browse/SOLR-12569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573095#comment-16573095 ] Alexandre Rafalovitch commented on SOLR-12569: -- Documentation patch is attached. As it is my first one and for somebody else's code, I would appreciate a review ([~ctargett], [~joel.bernstein]). > Document SignificantTermsQParserPlugin > -- > > Key: SOLR-12569 > URL: https://issues.apache.org/jira/browse/SOLR-12569 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation >Reporter: Alexandre Rafalovitch >Assignee: Alexandre Rafalovitch >Priority: Major > Attachments: SOLR-12569.patch > > > SignificantTermsQParserPlugin was introduced at the same as significantTerms > stream source, but only the stream source was documented. > QParser should be documented too, especially since it can be used in > non-cloud mode and has to be used as fq (otherwise, it throws exception). -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
