phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-783) In DeleteCompiler don't use context.isSingleRowScan() for optimizing delete
Date Fri, 02 May 2014 04:46:22 GMT

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

James Taylor resolved PHOENIX-783.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.0
                   4.0.0
                   3.0.0

> In DeleteCompiler don't use context.isSingleRowScan() for optimizing delete
> ---------------------------------------------------------------------------
>
>                 Key: PHOENIX-783
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-783
>             Project: Phoenix
>          Issue Type: Task
>    Affects Versions: 3.0-Release
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 3.0.0, 4.0.0, 5.0.0
>
>
> Instead we should use ScanUtil.isAllSingleRowScan(cnf, table.getRowKeySchema()) as is
done in WhereOptimizer, as this takes into account fully qualified statements with IN clauses.
> As a result, fix MetaDataClient.dropColumnMutations() too, as we really should only need
to execute a single IN query (which would be executed client-side once this is fixed).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message