You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Ankit Singhal (JIRA)" <ji...@apache.org> on 2016/05/19 16:38:13 UTC

[jira] [Commented] (PHOENIX-2915) Dropping of Index can still leave some non-replayed writes in WAL

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

Ankit Singhal commented on PHOENIX-2915:
----------------------------------------

Suggestion came while discussing internally([~enis],[~chrajeshbabu32@gmail.com],[~sergey.soldatov]) that we can simply ignore these edits if table is not found.


> Dropping of Index can still leave some non-replayed writes in WAL
> -----------------------------------------------------------------
>
>                 Key: PHOENIX-2915
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2915
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Ankit Singhal
>
> It could be possible , that there are some index writes in WAL which are not replayed and the index is dropped.
> And, now the table is not there, these writes cannot be replayed which result in data table regions also to not come up.



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