[ 
https://issues.apache.org/jira/browse/NIFI-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Thomsen updated NIFI-4838:
-------------------------------
    Description: 
It shouldn't wait until the end to do a commit() call because the effect is 
that GetMongo looks like it has hung to a user who is pulling a very large data 
set.

It should also have an option for running a count query to get the current 
approximate count of documents that would match the query and append an 
attribute that indicates where a flowfile stands in the total result count. Ex:

query.progress.point.start = 2500

query.progress.point.end = 5000

query.count.estimate = 17,568,231

  was:It shouldn't wait until the end to do a commit() call because the effect 
is that GetMongo looks like it has hung to a user who is pulling a very large 
data set.

        Summary: Make GetMongo support multiple commits and give some progress 
indication  (was: Make GetMongo support multiple commits)

> Make GetMongo support multiple commits and give some progress indication
> ------------------------------------------------------------------------
>
>                 Key: NIFI-4838
>                 URL: https://issues.apache.org/jira/browse/NIFI-4838
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Mike Thomsen
>            Assignee: Mike Thomsen
>            Priority: Major
>
> It shouldn't wait until the end to do a commit() call because the effect is 
> that GetMongo looks like it has hung to a user who is pulling a very large 
> data set.
> It should also have an option for running a count query to get the current 
> approximate count of documents that would match the query and append an 
> attribute that indicates where a flowfile stands in the total result count. 
> Ex:
> query.progress.point.start = 2500
> query.progress.point.end = 5000
> query.count.estimate = 17,568,231



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to