You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ryan McKinley (JIRA)" <ji...@apache.org> on 2011/03/10 00:08:59 UTC

[jira] Created: (SOLR-2417) Allow explain info directly to response documents

Allow explain info directly to response documents
-------------------------------------------------

                 Key: SOLR-2417
                 URL: https://issues.apache.org/jira/browse/SOLR-2417
             Project: Solr
          Issue Type: New Feature
            Reporter: Ryan McKinley
            Priority: Minor
             Fix For: 4.0


Currently explain information in displayed in the debugInfo part of the response.  This requires clients to build a Map and link results later if they want them displayed together.  It also does not nicely allow for multiple queries in one result.

As part of SOLR-1566, we can add the explain info directly to the result

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Resolved] (SOLR-2417) Allow explain info directly to response documents

Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley resolved SOLR-2417.
---------------------------------

    Resolution: Fixed
      Assignee: Ryan McKinley

> Allow explain info directly to response documents
> -------------------------------------------------
>
>                 Key: SOLR-2417
>                 URL: https://issues.apache.org/jira/browse/SOLR-2417
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ryan McKinley
>            Assignee: Ryan McKinley
>            Priority: Minor
>             Fix For: 4.0
>
>
> Currently explain information in displayed in the debugInfo part of the response.  This requires clients to build a Map and link results later if they want them displayed together.  It also does not nicely allow for multiple queries in one result.
> As part of SOLR-1566, we can add the explain info directly to the result

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046158#comment-13046158 ] 

Ryan McKinley commented on SOLR-2417:
-------------------------------------

Syntax changed to:
{code}
?fl=id,[explain]
{code}
{code}
?fl=id,[explain style=text]
{code}
{code}
?fl=id,[explain style=nl]
{code}

> Allow explain info directly to response documents
> -------------------------------------------------
>
>                 Key: SOLR-2417
>                 URL: https://issues.apache.org/jira/browse/SOLR-2417
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ryan McKinley
>            Assignee: Ryan McKinley
>            Priority: Minor
>             Fix For: 4.0
>
>
> Currently explain information in displayed in the debugInfo part of the response.  This requires clients to build a Map and link results later if they want them displayed together.  It also does not nicely allow for multiple queries in one result.
> As part of SOLR-1566, we can add the explain info directly to the result

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Ryan McKinley <ry...@gmail.com>.
> : As is, Transformers do not have access to SolrParams -- i think that
> : is OK, but we should discuss
> :
> : TransformerFactory could easily be changed to take SolrParams or
> : SolrQueryRequest.
>
> independent of whatever details get hashed out on the syntax to make it
> easy to specify  simple args inline, i think that any new plugin type (ie:
> TransformerFactory) where it's feasible to give access to the
> SolrQueryRequest, we should - so thta if it needs more robust runtime
> driven configuration it can get it.
>

agree -- r1086699 add this to the factory

syntax is different issue

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Chris Hostetter <ho...@fucit.org>.
: As is, it is not defined by a param, but via solrconfig:
: 
: <transformer name="explain"
: class="org.apache.solr.response.transform.ExplainAugmenterFactory" >
:   <str name="args">nl</str>
: </transformer>
: 
: As is, Transformers do not have access to SolrParams -- i think that
: is OK, but we should discuss
: 
: TransformerFactory could easily be changed to take SolrParams or
: SolrQueryRequest.

independent of whatever details get hashed out on the syntax to make it 
easy to specify  simple args inline, i think that any new plugin type (ie: 
TransformerFactory) where it's feasible to give access to the 
SolrQueryRequest, we should - so thta if it needs more robust runtime 
driven configuration it can get it.

having init params on the TransformerFactory in solrconfig.xml only gets 
you so far.  there will likely be other more complex things that we want 
to be able to specify at request time, or in the defaults for the 
request handlers (where each handler might want different default 
values when using the same Transformer), etc...


-Hoss

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Ryan McKinley <ry...@gmail.com>.
On Mon, Mar 28, 2011 at 9:36 PM, Chris Hostetter
<ho...@fucit.org> wrote:
>
> : On IRC, yonik suggested that the explain format should mimic follow what
> : the debugQuery parameter would use.
> :
> : I'm don't really agree -- long term I would even suggest dropping the
> : explain section from debug and letting you specify it as an inline
> : parameter.
>
> those seem like orthoginal issues:
>
> 1) (ryan) deprecate/remove the explain section from debug and
> tell people to use the "_explain_" psuedo field instead
>
> 2) (ryan) add options to the _explain_ psuedofield to let you pick
> an explanation style inline (ie: _explain:nl_)
>
> 3) (yonik) make the _explain_ psuedofield respect the
> debug.explain.structured param (or something like it)
>
> #1 & #2 don't preclude #3 ... if i always want to get the "nl" mode
> explanations, it would be nice to be able to hardcode something a param
> the defaults section for my handler so that adding the _explain_
> psuedofield just made it happen.
>

As is, it is not defined by a param, but via solrconfig:

<transformer name="explain"
class="org.apache.solr.response.transform.ExplainAugmenterFactory" >
  <str name="args">nl</str>
</transformer>

As is, Transformers do not have access to SolrParams -- i think that
is OK, but we should discuss

TransformerFactory could easily be changed to take SolrParams or
SolrQueryRequest.


ryan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Yonik Seeley <yo...@lucidimagination.com>.
On Tue, Mar 29, 2011 at 10:44 AM, Ryan McKinley <ry...@gmail.com> wrote:
> more complex details would be handled via standard parameters -- for
> highlighting, we would use the existing parameters to setup the
> highlighter.
>
> fl=id,[hl:title],[hl:body]&hl.fragsize=100
>
> We could even use the standard per-field stuff:
>
> fl=id,[hl:title],[hl:body]&hl.fragsize=100&f.title.fragsize=50

If we're still going to make such extensive use of the existing
parameters (which makes sense),
then wouldn't a simple "hl.inline=true" (or something like that) make sense?

-Yonik
http://www.lucenerevolution.org -- Lucene/Solr User Conference, May
25-26, San Francisco

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Ryan McKinley <ry...@gmail.com>.
On Tue, Mar 29, 2011 at 10:30 AM, Yonik Seeley
<yo...@lucidimagination.com> wrote:
> On Tue, Mar 29, 2011 at 10:20 AM, Ryan McKinley <ry...@gmail.com> wrote:
>>>>
>>>> Another key example would be inline highlighting:
>>>>
>>>> &id,_hl:title_,body
>>>
>>> If we're going to come up with another syntax, it needs to be fully fleshed out.
>>> This one already looks ambiguous in the context of "fl".
>>>
>>> For example, does that mean give me "id","title highlighted","body"
>>> or does it mean "id","title and body highlighted"?
>>>
>>
>> To get title and body highlighted, you would have:
>> &fl=id,_hl:title_,_hl:body_
>> In general, an fl value that starts and ends with _ tries to call a transformer.
>
> Oh, so the underscores are the delimiters themselves?
> id,_hl:title_,_hl:body_
>
> Whew... I dunno.  That definitely wasn't obvious when I first looked
> at it, due to underscore normally being part of an id.

something else seem more reasonable?  maybe id,[explain],[value:hello]

> What about named parameters (like say number of fragments or whatever)?
>

more complex details would be handled via standard parameters -- for
highlighting, we would use the existing parameters to setup the
highlighter.

fl=id,[hl:title],[hl:body]&hl.fragsize=100

We could even use the standard per-field stuff:

fl=id,[hl:title],[hl:body]&hl.fragsize=100&f.title.fragsize=50

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Jan Høydahl <ja...@cominvent.com>.
I'd prefer plain field names, even for "pseudo fields", in same way as "score".

Then do the config of what a pseudo field means outside of fl=

Example concept:
&fl=title,explain
&transformer.explain.field=explain
&f.explain.transformer.explain.type=text

&fl=title,myhltitle
&f.title.transformer.hl.field=myhltitle

This will give a 1:1 between what you ask for in fl and what you get in the result. End user only need to relate to plain names configured by the search admin and set as defaults in solrconfig.xml requesthandlers. This gives a nice logical separation of roles in a search project as well. I as search engineer set all the defaults, the API users select from a list of pseudo fields I have told them to use, and is happily ignorant of the implementation, or even whether it's a real field or a pseudo field.

Other usecase is  distance:
&fl=title,mydistance

...will give the distance from a geospatial calculation in the mydistance field. API users would treat it exactly the same as an ordinary field.

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

On 29. mars 2011, at 16.30, Yonik Seeley wrote:

> On Tue, Mar 29, 2011 at 10:20 AM, Ryan McKinley <ry...@gmail.com> wrote:
>>>> 
>>>> Another key example would be inline highlighting:
>>>> 
>>>> &id,_hl:title_,body
>>> 
>>> If we're going to come up with another syntax, it needs to be fully fleshed out.
>>> This one already looks ambiguous in the context of "fl".
>>> 
>>> For example, does that mean give me "id","title highlighted","body"
>>> or does it mean "id","title and body highlighted"?
>>> 
>> 
>> To get title and body highlighted, you would have:
>> &fl=id,_hl:title_,_hl:body_
>> In general, an fl value that starts and ends with _ tries to call a transformer.
> 
> Oh, so the underscores are the delimiters themselves?
> id,_hl:title_,_hl:body_
> 
> Whew... I dunno.  That definitely wasn't obvious when I first looked
> at it, due to underscore normally being part of an id.
> What about named parameters (like say number of fragments or whatever)?
> 
> -Yonik
> http://www.lucenerevolution.org -- Lucene/Solr User Conference, May
> 25-26, San Francisco
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Yonik Seeley <yo...@lucidimagination.com>.
On Tue, Mar 29, 2011 at 10:20 AM, Ryan McKinley <ry...@gmail.com> wrote:
>>>
>>> Another key example would be inline highlighting:
>>>
>>> &id,_hl:title_,body
>>
>> If we're going to come up with another syntax, it needs to be fully fleshed out.
>> This one already looks ambiguous in the context of "fl".
>>
>> For example, does that mean give me "id","title highlighted","body"
>> or does it mean "id","title and body highlighted"?
>>
>
> To get title and body highlighted, you would have:
> &fl=id,_hl:title_,_hl:body_
> In general, an fl value that starts and ends with _ tries to call a transformer.

Oh, so the underscores are the delimiters themselves?
id,_hl:title_,_hl:body_

Whew... I dunno.  That definitely wasn't obvious when I first looked
at it, due to underscore normally being part of an id.
What about named parameters (like say number of fragments or whatever)?

-Yonik
http://www.lucenerevolution.org -- Lucene/Solr User Conference, May
25-26, San Francisco

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Ryan McKinley <ry...@gmail.com>.
>>
>> Another key example would be inline highlighting:
>>
>> &id,_hl:title_,body
>
> If we're going to come up with another syntax, it needs to be fully fleshed out.
> This one already looks ambiguous in the context of "fl".
>
> For example, does that mean give me "id","title highlighted","body"
> or does it mean "id","title and body highlighted"?
>

To get title and body highlighted, you would have:
&fl=id,_hl:title_,_hl:body_

In general, an fl value that starts and ends with _ tries to call a transformer.

Are you thinking of something else?

For highlighting we *could* use all existing parameters, but that
leavs a lot of ambiguity -- how would I get title highlighted and not
highlighted?  In this syntax, it would be:

fl=id,title,_hl:title_

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Yonik Seeley <yo...@lucidimagination.com>.
On Tue, Mar 29, 2011 at 10:08 AM, Ryan McKinley <ry...@gmail.com> wrote:
>>>
>>> I was trying to think up what other real use cases actually where...
>>> because that really does have a bearing on if a new syntax should be
>>> developed, and what that syntax should look like.
>>>
>>
>> The use cases I can think of are either very simple or very complex.
>> I like this because it lets simple happen inline, and complex can
>> happen in Components/Handlers/elsewhere
>>
>
> Another key example would be inline highlighting:
>
> &id,_hl:title_,body

If we're going to come up with another syntax, it needs to be fully fleshed out.
This one already looks ambiguous in the context of "fl".

For example, does that mean give me "id","title highlighted","body"
or does it mean "id","title and body highlighted"?


-Yonik
http://www.lucenerevolution.org -- Lucene/Solr User Conference, May
25-26, San Francisco

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Ryan McKinley <ry...@gmail.com>.
>>
>> I was trying to think up what other real use cases actually where...
>> because that really does have a bearing on if a new syntax should be
>> developed, and what that syntax should look like.
>>
>
> The use cases I can think of are either very simple or very complex.
> I like this because it lets simple happen inline, and complex can
> happen in Components/Handlers/elsewhere
>

Another key example would be inline highlighting:

&id,_hl:title_,body

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Ryan McKinley <ry...@gmail.com>.
On Tue, Mar 29, 2011 at 7:36 AM, Yonik Seeley
<yo...@lucidimagination.com> wrote:
> On Mon, Mar 28, 2011 at 11:26 PM, Ryan McKinley <ry...@gmail.com> wrote:
>>>
>>> And I'm still on the fence - _explain_ alone does not justify a whole
>>> new syntax IMO... so we may need more usecase examples to figure out
>>> what problem we're actually trying to solve.
>>>
>>
>> The key use case I am thinking of is an easy way to add a value to the
>> the response.  In SQL:
>>
>> SELECT name,'hello' FROM ...
>>
>> With this syntax you can now use:
>>
>> fl=name,_value:hello_
>>
>> The existing syntax is totally ridiculous:
>>
>> fl=name,{!transformer name=value value=hello}
>
> That's not the existing syntax.  Or I guess you were just
> brainstorming about what using the existing localParams syntax would
> look like if you tried to apply it to transformers?

Ya, i was looking at an easy way to pass a simple argument to a
transformer.  LocalParams seems to be the way they are done, another
option would be &transformer._value_=hello  but I think i like the
inline bit.

> Or are you saying that localParams syntax is ridiculous and should be
> replaced by something different?
>

Not suggesting that, just saying it is overly complicated to pass a
single value to something.


>> I see a real need to be able to pass a simple value to a transformer.
>> Explain is just one of many examples.
>
> I was trying to think up what other real use cases actually where...
> because that really does have a bearing on if a new syntax should be
> developed, and what that syntax should look like.
>

The use cases I can think of are either very simple or very complex.
I like this because it lets simple happen inline, and complex can
happen in Components/Handlers/elsewhere

ryan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Yonik Seeley <yo...@lucidimagination.com>.
On Mon, Mar 28, 2011 at 11:26 PM, Ryan McKinley <ry...@gmail.com> wrote:
>>
>> And I'm still on the fence - _explain_ alone does not justify a whole
>> new syntax IMO... so we may need more usecase examples to figure out
>> what problem we're actually trying to solve.
>>
>
> The key use case I am thinking of is an easy way to add a value to the
> the response.  In SQL:
>
> SELECT name,'hello' FROM ...
>
> With this syntax you can now use:
>
> fl=name,_value:hello_
>
> The existing syntax is totally ridiculous:
>
> fl=name,{!transformer name=value value=hello}

That's not the existing syntax.  Or I guess you were just
brainstorming about what using the existing localParams syntax would
look like if you tried to apply it to transformers?
Or are you saying that localParams syntax is ridiculous and should be
replaced by something different?

> I see a real need to be able to pass a simple value to a transformer.
> Explain is just one of many examples.

I was trying to think up what other real use cases actually where...
because that really does have a bearing on if a new syntax should be
developed, and what that syntax should look like.

-Yonik

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Ryan McKinley <ry...@gmail.com>.
>
> And I'm still on the fence - _explain_ alone does not justify a whole
> new syntax IMO... so we may need more usecase examples to figure out
> what problem we're actually trying to solve.
>

The key use case I am thinking of is an easy way to add a value to the
the response.  In SQL:

SELECT name,'hello' FROM ...

With this syntax you can now use:

fl=name,_value:hello_

The existing syntax is totally ridiculous:

fl=name,{!transformer name=value value=hello}


I see a real need to be able to pass a simple value to a transformer.
Explain is just one of many examples.

ryan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Yonik Seeley <yo...@lucidimagination.com>.
On Mon, Mar 28, 2011 at 9:36 PM, Chris Hostetter
<ho...@fucit.org> wrote:
>
> : On IRC, yonik suggested that the explain format should mimic follow what
> : the debugQuery parameter would use.
> :
> : I'm don't really agree -- long term I would even suggest dropping the
> : explain section from debug and letting you specify it as an inline
> : parameter.
>
> those seem like orthoginal issues:
>
> 1) (ryan) deprecate/remove the explain section from debug and
> tell people to use the "_explain_" psuedo field instead
>
> 2) (ryan) add options to the _explain_ psuedofield to let you pick
> an explanation style inline (ie: _explain:nl_)
>
> 3) (yonik) make the _explain_ psuedofield respect the
> debug.explain.structured param (or something like it)
>
> #1 & #2 don't preclude #3 ... if i always want to get the "nl" mode
> explanations, it would be nice to be able to hardcode something a param
> the defaults section for my handler so that adding the _explain_
> psuedofield just made it happen.


I think we both agreed that _explain_ was a good thing.
The issue was more about this: if explain has different formatting,
how should it be controlled?
I pointed out there was already a parameter to control this.
Ryan had some alternate syntax proposals to allow passing parameters
to transformers (and I was on the fence due to syntax proliferation -
we already have localParams).

And I'm still on the fence - _explain_ alone does not justify a whole
new syntax IMO... so we may need more usecase examples to figure out
what problem we're actually trying to solve.

-Yonik
http://www.lucenerevolution.org -- Lucene/Solr User Conference, May
25-26, San Francisco

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Re: [jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by Chris Hostetter <ho...@fucit.org>.
: On IRC, yonik suggested that the explain format should mimic follow what 
: the debugQuery parameter would use.
: 
: I'm don't really agree -- long term I would even suggest dropping the 
: explain section from debug and letting you specify it as an inline 
: parameter.

those seem like orthoginal issues:

1) (ryan) deprecate/remove the explain section from debug and 
tell people to use the "_explain_" psuedo field instead

2) (ryan) add options to the _explain_ psuedofield to let you pick 
an explanation style inline (ie: _explain:nl_)

3) (yonik) make the _explain_ psuedofield respect the 
debug.explain.structured param (or something like it)

#1 & #2 don't preclude #3 ... if i always want to get the "nl" mode 
explanations, it would be nice to be able to hardcode something a param
the defaults section for my handler so that adding the _explain_ 
psuedofield just made it happen.


-Hoss

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011551#comment-13011551 ] 

Ryan McKinley commented on SOLR-2417:
-------------------------------------

On IRC, yonik suggested that the explain format should mimic follow what the debugQuery parameter would use.

I'm don't really agree -- long term I would even suggest dropping the explain section from debug and letting you specify it as an inline parameter.

As is, the options are to display it as text,named list or html
{code}?fl=id,_explain_{code}
{code}?fl=id,_explain:text_{code}
{code}?fl=id,_explain:nl_{code}
{code}?fl=id,_explain:html_{code}



> Allow explain info directly to response documents
> -------------------------------------------------
>
>                 Key: SOLR-2417
>                 URL: https://issues.apache.org/jira/browse/SOLR-2417
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ryan McKinley
>            Assignee: Ryan McKinley
>            Priority: Minor
>             Fix For: 4.0
>
>
> Currently explain information in displayed in the debugInfo part of the response.  This requires clients to build a Map and link results later if they want them displayed together.  It also does not nicely allow for multiple queries in one result.
> As part of SOLR-1566, we can add the explain info directly to the result

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[jira] [Commented] (SOLR-2417) Allow explain info directly to response documents

Posted by "Ryan McKinley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011381#comment-13011381 ] 

Ryan McKinley commented on SOLR-2417:
-------------------------------------

Added as part of SOLR-1566
{code}
?fl=id,_explain_
{code}
will add the explain info inline.

The final syntax is still in flux and will be determined in SOLR-2444


> Allow explain info directly to response documents
> -------------------------------------------------
>
>                 Key: SOLR-2417
>                 URL: https://issues.apache.org/jira/browse/SOLR-2417
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Ryan McKinley
>            Priority: Minor
>             Fix For: 4.0
>
>
> Currently explain information in displayed in the debugInfo part of the response.  This requires clients to build a Map and link results later if they want them displayed together.  It also does not nicely allow for multiple queries in one result.
> As part of SOLR-1566, we can add the explain info directly to the result

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org