Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
Message-ID: <56335631.8070903@orkash.com>
Date: Fri, 30 Oct 2015 17:06:17 +0530
From: "shweta.agrawal" <shweta.agrawal@orkash.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130330 Thunderbird/17.0.5
MIME-Version: 1.0
To: user@accumulo.apache.org
Subject: Transaction type query in accumulo
Content-Type: multipart/alternative;
 boundary="------------010201010305050906090903"

This is a multi-part message in MIME format.
--------------010201010305050906090903
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

Is transaction type facility available in Accumulo?
I have read about transaction in accumulo which says " Accumulo 
guarantees these ACID properties for a single mutation (a set of changes 
for a single row) but does not provide support for atomic updates across 
multiple rows"

In my case:
If one thread is updating the fields of a document then this document 
should be locked so that other thread cannot modify that document.

I am trying to achieve this by a query through conditional mutation. I 
am checking whether the particular entry exist or not  then updating. 
But the problem is I am doing this through 150 threads. If one thread 
finds and updating particular entry then other thread should not get it.

So is this the case in conditional write?

We are achieving same thing through mongoDB by find and modify feature.

If one thread get particular document to update from conditional write 
then other thread should get that particular document.

Please provide your inputs

Thanks
Shweta

--------------010201010305050906090903
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi,<br>
    <br>
    Is transaction type facility available in Accumulo?<br>
    I have read about transaction in accumulo which says "
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <span style="color: rgb(51, 51, 51); font-family: serif,
      DejaVuSerif; font-size: 16px; font-style: normal; font-variant:
      normal; font-weight: normal; letter-spacing: normal; line-height:
      26.390625px; orphans: auto; text-align: left; text-indent: 0px;
      text-transform: none; white-space: normal; widows: auto;
      word-spacing: 0px; -webkit-text-size-adjust: auto;
      -webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
      255); display: inline !important; float: none;">Accumulo
      guarantees these ACID properties for a single mutation (a set of
      changes for a single row) but does not provide support for atomic
      updates across multiple rows</span>"<br>
    <br>
    In my case:<br>
    If one thread is updating the fields of a document then this
    document should be locked so that other thread cannot modify that
    document.<br>
    <br>
    I am trying to achieve this by a query through conditional mutation.
    I am checking whether the particular entry exist or not&nbsp; then
    updating. But the problem is I am doing this through 150 threads. If
    one thread finds and updating particular entry then other thread
    should not get it. <br>
    <br>
    So is this the case in conditional write?<br>
    <br>
    We are achieving same thing through mongoDB by find and modify
    feature.<br>
    <br>
    If one thread get particular document to update from conditional
    write then other thread should get that particular document.<br>
    <br>
    Please provide your inputs<br>
    <br>
    Thanks <br>
    Shweta <br>
  </body>
</html>

--------------010201010305050906090903--