[jira] [Commented] (PHOENIX-2935) IndexMetaData cache can expire when a delete and or query running on server

["Ankit Singhal (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562050#comment-15562050 ] 

Ankit Singhal commented on PHOENIX-2935:
----------------------------------------

[~jamestaylor], in case of DELETE on server or UPSERT SELECT on server, how about sending indexMetaDataPtr in scan attribute(PFA, for the same) .  Problem could be a size of scan object become little large(by 2KB+ with 15-30 indexes) and RPC could be little slow which would be aggravated with large number of guidePosts or region in range for the query but not sure if this is huge side effect against failing the query on cache expiry.



> IndexMetaData cache can expire when a delete and or query running on server
> ---------------------------------------------------------------------------
>
>                 Key: PHOENIX-2935
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2935
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Ankit Singhal
>         Attachments: PHOENIX-2935.patch
>
>
> IndexMetaData cache can expire when a delete or upsert query is running on server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)