accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Medinets (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-2570) Consider API additions to support non-batch oriented reads/writes
Date Tue, 22 Apr 2014 00:46:18 GMT


David Medinets updated ACCUMULO-2570:

    Priority: Trivial  (was: Major)

Reducing priority due to "better syntactic sugar" wording.

> Consider API additions to support non-batch oriented reads/writes
> -----------------------------------------------------------------
>                 Key: ACCUMULO-2570
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client, tserver
>            Reporter: Josh Elser
>            Priority: Trivial
> Primary Read API : Scanner and BatchScanner
> Primary Write API: BatchWriter
> Both the Read calls are oriented to a scanning a collection of key-values (unless someone
knows of the Range.exact method), and have internals that are focused on multiple, repeated
fetching of batches.
> For writes, Mutations are buffered internally and are focused around sending batches
of updates.
> While these classes do support pointed accesses (write a single Mutation, get the Value
from a single Key), the API is not succinct and may incur unnecessary penalty due to the implementation
also needing to support batch operations.
> It would be nice to consider some new access patterns that are more focused around very
pointed accesses that reduce the API complexity for simple cases. Extremely hypothetical example
> {code}
>   Value v = connector.get("tableName", new Key("row", "cf", "cq", "viz");
>   connector.put("tableName", new Key("row", "cf", "cq", "viz"), new Value("value"));
> {code}
> The implementation could focus on specifically handling this pointed accesses in the
most efficient way without worrying about also handling batch operations.

This message was sent by Atlassian JIRA

View raw message