[
https://issues.apache.org/jira/browse/DRILL-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453401#comment-15453401
]
Jacques Nadeau commented on DRILL-4869:
---------------------------------------
For those that are interested, the old code actually ran the full query on
prepare. This caused a number of weird externalities when tools were executing
prepare without necessarily executing queries (especially some query editors).
This brings the JDBC and ODBC behavior into alignment. Once we move the ODBC
prepare operations to the server from the client, we can optimize the handling
on the server to minimize the work across operations.
> Some queries sent via JDBC get executed twice.
> ----------------------------------------------
>
> Key: DRILL-4869
> URL: https://issues.apache.org/jira/browse/DRILL-4869
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.8.0
> Reporter: Oscar Morante
>
> This didn't happen before the prepared statement changes so I guess it has
> something to do with that:
> {noformat}
> 2016-08-31 11:00:20,520 [2839716a-9615-25a2-a285-cf38a187784e:foreman] INFO
> o.a.drill.exec.work.foreman.Foreman - Prepared statement query for QueryId
> part1: 2898472537788065186
> part2: -6735749825527580594
> : select * from (values(1))
> {noformat}
> The query appears twice on the web interface but the second one doesn't have
> the query text:
> http://i.imgur.com/QB0FOdz.png
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
