[
https://issues.apache.org/jira/browse/IGNITE-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323886#comment-16323886
]
Roman Kondakov commented on IGNITE-6022:
----------------------------------------
[~al.psc]
1. Ok, I'll get rid of it.
2. We do not fail on non-SQL exception due to JDBC specs 14.1.3 Handling
Failures during Execution. Briefly: driver should process *all* queries in the
batch despite of any of them failed with *any* reason. If query failed, we mark
it as {{Statement.EXECUTE_FAILED}} at
{{BatchUpdateException.getUpdateCounts}}. So we have to process all queries
even if some of they fail with any exception, and return results of processing
back to the client.
3. Ok, I'll fix it.
4. Ok, I'll fix it.
5. Ok, I'll fix it..
6. Actually, I don't see any reasons for this check in
{{UpdatePlanBuilder.checkPlanCanBeDistributed}}. I'll remove it. [~vozerov], is
it safe to remove it?
7. Ok, I'll fix it.
8. Ok, I'll fix it.
9. Could you please point on such kind of violations? I haven't found any.
10. I agree, I'll add comments.
11. Ok, I'll fix it.
> SQL: add native batch execution support for DML statements
> ----------------------------------------------------------
>
> Key: IGNITE-6022
> URL: https://issues.apache.org/jira/browse/IGNITE-6022
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.1
> Reporter: Vladimir Ozerov
> Assignee: Roman Kondakov
> Labels: iep-1, performance
> Fix For: 2.4
>
>
> We have batch execution support for JDBC and ODBC drivers. This decreases
> number of network hops. However, we do not have any batch execution support
> on the server side. It means that for batch of N similar statements, every
> statement will go through the whole execution chain - parsing, splitting,
> communication with servers. And while parsing and splitting might be avoided
> with help of statement cache, the most heavy part - network communication -
> is still there.
> We need to investigate how to optimize the flow for batch updates. Possible
> improvements:
> 1) Execute statements with certain degree of parallelism;
> 2) Send several query execution requests to the server at once;
> 3) Ensure that caches are used properly for batching - we should not parse
> the same request multiple times.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
