[
https://issues.apache.org/jira/browse/CALCITE-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435393#comment-15435393
]
Josh Elser commented on CALCITE-1301:
-------------------------------------
bq. The other changes are not part of this bug, but are needed by Calcite for
related stuff, so I thought it would be OK to include them in the same commit.
Ok, great that's fine. I didn't have enough context and thought they were
totally unrelated :)
bq. I think the commit is OK now. If you agree, +1 and I'll squash and push to
master.
Yup. Looks great. Thanks!
> Add cancel flag to AvaticaResultSet
> -----------------------------------
>
> Key: CALCITE-1301
> URL: https://issues.apache.org/jira/browse/CALCITE-1301
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Labels: avatica
> Fix For: avatica-1.9.0
>
>
> Add cancel flag to AvaticaResultSet. The flag was added to CalciteResultSet
> as part of CALCITE-1227, but would be useful in the Avatica base class.
> It is currently of type {{CancelFlag}} but maybe it should become
> {{AtomicBoolean}}.
> To complete implementation of java.sql.Statement#cancel we would need a
> Cancel command; that is out of scope of this case, and would be covered by
> CALCITE-520.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
