[
https://issues.apache.org/jira/browse/IGNITE-10991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783140#comment-16783140
]
Vladimir Ozerov commented on IGNITE-10991:
------------------------------------------
[~tledkov-gridgain], looks good to me in general, but I am not quite understand
{{JdbcRequestHandler.OrderedBatchWorker#body}} method: why do we do {{peek}}
and then make {{poll}}? Can we just make one {{poll}} instead?
> JDBC thin: STREAMING mode fails on streamer reopen on not ordered mode
> ----------------------------------------------------------------------
>
> Key: IGNITE-10991
> URL: https://issues.apache.org/jira/browse/IGNITE-10991
> Project: Ignite
> Issue Type: Bug
> Components: jdbc, sql
> Affects Versions: 2.6
> Reporter: Ilya Kasnacheev
> Assignee: Taras Ledkov
> Priority: Major
> Fix For: 2.8
>
> Attachments: CacheSqlStreamingAllowOverwriteTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Please see attached test. Repeatedly overwriting same cache entries over and
> over in streaming mode with ALLOW_OVERWRITE ON will cause either:
> {code}
> java.sql.BatchUpdateException: Failed to INSERT some keys because they are
> already in cache [keys=[2054...]
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1052)
> ... 1 more
> {code}
> or
> {code}
> WARNING: Exception during batch send on streamed connection close
> java.sql.BatchUpdateException: class
> org.apache.ignite.IgniteCheckedException: Data streamer has been closed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1016)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Expecter behavior - no failures, all records overwritten.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
