[
https://issues.apache.org/jira/browse/PHOENIX-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563474#comment-15563474
]
Enis Soztutar commented on PHOENIX-2935:
----------------------------------------
bq. 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.
Agreed, however, it should be acceptable I think given that this is for UPSERT
SELECT kind of queries where the expected runtime of the query is already high
to offset the extra cost in serialization of index metadata.
+1 for the patch.
> 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
> Assignee: Ankit Singhal
> Labels: index
> Fix For: 4.9.0
>
> 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)
