[ 
https://issues.apache.org/jira/browse/CAMEL-12962?focusedWorklogId=384143&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-384143
 ]

ASF GitHub Bot logged work on CAMEL-12962:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Feb/20 21:28
            Start Date: 09/Feb/20 21:28
    Worklog Time Spent: 10m 
      Work Description: mcserra commented on pull request #3557: CAMEL-12962: 
camel-elasticsearch - Allow size/from on search
URL: https://github.com/apache/camel/pull/3557
 
 
   
   
   Signed-off-by: Miguel Serra <[email protected]>
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 384143)
    Remaining Estimate: 0h
            Time Spent: 10m

> camel-elasticsearch - Allow from and size for SearchSource / SearchRequest to 
> be set via URI
> --------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-12962
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12962
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-elasticsearch-rest
>    Affects Versions: 2.22.1
>            Reporter: Derek White
>            Priority: Minor
>             Fix For: Future
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is currently no straightforward way that I know of to request more than 
> the first 10 search results. Please allow from and size for SearchSource / 
> SearchRequest to be set via URI.
> To add, since the ElasticsearchActionRequestConverter actually pulls the root 
> node of the Query DSL, setting from and size in the request body string or 
> Map is actually ignored.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to