Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E59CE10B84 for ; Thu, 27 Mar 2014 22:39:32 +0000 (UTC) Received: (qmail 24442 invoked by uid 500); 27 Mar 2014 22:39:15 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 24378 invoked by uid 500); 27 Mar 2014 22:39:15 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 24367 invoked by uid 99); 27 Mar 2014 22:39:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2014 22:39:15 +0000 Date: Thu, 27 Mar 2014 22:39:14 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2570) Consider API additions to support non-batch oriented reads/writes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950045#comment-13950045 ] Josh Elser commented on ACCUMULO-2570: -------------------------------------- Oh, interesting -- didn't know about that one. Admittedly, I think there is a place for some better syntactic sugar here, and that was my primary thought. > Consider API additions to support non-batch oriented reads/writes > ----------------------------------------------------------------- > > Key: ACCUMULO-2570 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2570 > Project: Accumulo > Issue Type: Improvement > Components: client, tserver > Reporter: Josh Elser > > 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 (v6.2#6252)