[
https://issues.apache.org/jira/browse/SOLR-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406087#comment-15406087
]
Alexandre Rafalovitch commented on SOLR-7898:
---------------------------------------------
With latest Solr's default configurations, overrides, property sets, etc, the
only place the real query is known is deep within the bowls of Solr after
everything is resolved. And it is logged in some fashion if appropriate TRACE
is enabled.
And if that's enabled, the output goes to the log, which is displayed in the
Admin UI.
So, I think there is not much for the Admin UI specifically here.
What would be nice is to have somehow a debugging component that will log a
final query in a way that shows all the layers contributing to it. But that
would be a very different JIRA.
This one, I believe, can be closed.
> Administrative Interface Should Steam Incoming Queries and Results Per Core
> ---------------------------------------------------------------------------
>
> Key: SOLR-7898
> URL: https://issues.apache.org/jira/browse/SOLR-7898
> Project: Solr
> Issue Type: New Feature
> Components: web gui
> Affects Versions: 5.2.1
> Reporter: Aaron Greenspan
> Priority: Minor
>
> It would be helpful for debugging purposes (and kind of cool) to see the
> queries coming into Solr and the results found for each in a tail -f style
> streaming interface on the administrative web site. I'm pretty sure this
> information is logged anyway...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
