phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (Jira)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-5224) Repeated SQL in Tests should use PreparedStatement
Date Mon, 09 Sep 2019 18:00:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-5224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Geoffrey Jacoby updated PHOENIX-5224:
-------------------------------------
    Summary: Repeated SQL in Tests should use PreparedStatement  (was: Iteratively executing
the same SQL query will greatly damage the performance)

> Repeated SQL in Tests should use PreparedStatement
> --------------------------------------------------
>
>                 Key: PHOENIX-5224
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5224
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: bd2019us
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: 1.patch
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Locations: 
> (1) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexRebuildIncrementDisableCountIT.java:170
> (2) phoenix-core/src/it/java/org/apache/phoenix/tx/TxCheckpointIT.java:108
> (3) phoenix-core/src/it/java/org/apache/phoenix/end2end/DeleteIT.java:794,858
> (4) phoenix-core/src/it/java/org/apache/phoenix/end2end/UpsertSelectAutoCommitIT.java:240
> (5) phoenix-core/src/it/java/org/apache/phoenix/end2end/DropTableIT.java:35
> At these locations, the java.sql.Statement is intensively used in a loop and executing
the same SQL query, which will highly damage the performance of database access. In such cases,
java.sql.PreparedStatement should be used to enable the database compiling the SQL command
ahead of time, which has a much better performance compared with Statement.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message