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

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2019/04/22 19:50:00 UTC

[jira] [Resolved] (ACCUMULO-39) Client session migration

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

Christopher Tubbs resolved ACCUMULO-39.
---------------------------------------
    Resolution: Won't Fix

This is quite old, complicated, and possibly unsafe (given the state of Java serialization). I'm closing this for now. If this is still an issue that we wish to pursue, please open an issue on GitHub, where we now track issues: https://github.com/apache/accumulo/issues

> Client session migration
> ------------------------
>
>                 Key: ACCUMULO-39
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-39
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Keith Turner
>            Priority: Major
>
> Make client Objects like BatchScanner and Scanner serializable.  The use case is to allow an iterator over a scanner or batch scanner to be persisted by clustered app servers.  This avoids having to restart user queries that are paging/scrolling when an app server fails.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)