[
https://issues.apache.org/jira/browse/CAMEL-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296462#comment-14296462
]
Kranti Parisa edited comment on CAMEL-8288 at 1/29/15 7:00 AM:
---------------------------------------------------------------
Initially, I thought the same. but after looking at the QUERY header param,
which is used by both lucene component and LuceneQueryProcessor, wanted to
follow the same. if we want to pass that via the param then we will need to
change the LuceneQueryProcessor constructor as well. do you think that's ok?
users might need to fix their implementations in case if they are using the
LuceneQueryProcessor.
was (Author: krantiparisa):
Initially, I thought the same. but after looking at the QUERY header param,
which is used both by the component and the lucenequeryprocessor, wanted to
follow the same.
> 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
> Reporter: Kranti Parisa
> Priority: Minor
> Fix For: 2.15.0
>
>
> 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
> {code}
> .setHeader("RETURN_LUCENE_DOCS",constant("true"))
> {code}
> 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)
