phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vincentpoon <>
Subject [GitHub] phoenix pull request #290: PHOENIX-4130 Avoid server retries for mutable ind...
Date Mon, 29 Jan 2018 21:56:11 GMT
Github user vincentpoon commented on a diff in the pull request:
    --- Diff: phoenix-core/src/main/java/org/apache/phoenix/optimize/ ---
    @@ -312,6 +317,16 @@ private static QueryPlan addPlan(PhoenixStatement statement, SelectStatement
             return null;
    +    // returns true if we can still use the index
    +    // retuns false if we've been in PENDING_DISABLE too long - index should be considered
    +    private static boolean isUnderPendingDisableThreshold(PhoenixStatement statement,
PTable indexTable) {
    +        return EnvironmentEdgeManager
    +                .currentTimeMillis() - indexTable.getIndexDisableTimestamp() <= statement
    --- End diff --
    @JamesRTaylor So found out the problem is that for index tables that are disabled, in
MetaDataEndpointImpl we use the the indexDisableTimestamp for the mutationTime.  There's this
    "            // Freeze time for table at min non-zero value of INDEX_DISABLE_TIMESTAMP
                // This will keep the table consistent with index as the table has had one
                // batch applied to it."
    Is that still required?   I think I have to find another way to get the server time because
of this.


View raw message