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

ASF GitHub Bot commented on CAMEL-8288:
---------------------------------------

GitHub user krantiparisa opened a pull request:

    https://github.com/apache/camel/pull/382

    CAMEL-8288 Attach Lucene Documents to the Results(Hits) if header contains 
RETURN_LUCENE_DOCS=true

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/krantiparisa/camel master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/382.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #382
    
----
commit 29601ac78cb8a043ea537893b510ea5f248e924d
Author: Kranti Parisa <[email protected]>
Date:   2015-01-28T00:22:27Z

    CAMEL-8288 Attach Lucene Documents to the Results(Hits) if header contains 
RETURN_LUCENE_DOCS=true

----


> Attach Lucene Documents to the Results(Hits) if header contains 
> RETURN_LUCENE_DOCS=true
> ---------------------------------------------------------------------------------------
>
>                 Key: CAMEL-8288
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8288
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-lucene
>    Affects Versions: 2.14.2, 2.15.0
>            Reporter: Kranti Parisa
>            Priority: Minor
>
> Current Hits result only contains the lucene docId, score and assuming there 
> will be a field with the name "contents". 
> This feature will allow specifying a new header value "RETURN_LUCENE_DOCS" to 
> "true" and return the actual lucene documents part of the Hits for further 
> processing. This will allow us to retrieve any field from the actual lucene 
> document. 
> Both Lucene component and LuceneQueryProcessor should support this new header.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to