[teiid-issues] [JBoss JIRA] (TEIID-2371) Provide a callback when there are no results for a query incase of asynchronous queries

[Vineela Gampa (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751938#comment-12751938 ] 

Vineela Gampa commented on TEIID-2371:
--------------------------------------

Hi Steve,

Please take a look at com.ca.chorus.db.async.ExecuteAsyncContinously.continuouslyWhenData(). We have a feature called autoRefresh where the data is refreshed on UI every minute. So we dont close the statement until the user turns off autoRefresh(thats when we cancel the qeury and close the statement).

In my testcase  beforeNextExecution gets called in between the executions.

when the query is getting executed - 
1) onRow gets called 
2)beforeNextExecution gets called between the executions
2) next continous execution starts - on row gets triggered

So as beforeNextExecution gets called in between the executions this doesn't perfectly identify the empty result set.

To identify emptyResultset this is the approach iam planning on  - if on row is not called and beforeNextExecution gets called(for continous executions)/onComplete(incase of noncontinous) , then i treat it as an empty resultset. Do you think this would fail in any scenario ?
                
> Provide a callback when there are no results for a query incase of asynchronous queries
> ---------------------------------------------------------------------------------------
>
>                 Key: TEIID-2371
>                 URL: https://issues.jboss.org/browse/TEIID-2371
>             Project: Teiid
>          Issue Type: Feature Request
>            Reporter: Vineela Gampa
>            Assignee: Steven Hawkins
>         Attachments: EmptyResultSetAsyncTest.java, ExecuteAsyncContinously.java
>
>
> When a query doesn,t return results , please provide a callback method indicating end of results. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira