Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 415007596 for ; Sat, 30 Jul 2011 22:28:40 +0000 (UTC) Received: (qmail 83789 invoked by uid 500); 30 Jul 2011 22:28:38 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 83638 invoked by uid 500); 30 Jul 2011 22:28:37 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 83630 invoked by uid 99); 30 Jul 2011 22:28:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Jul 2011 22:28:37 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.139.212.181] (HELO nm22.bullet.mail.bf1.yahoo.com) (98.139.212.181) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 30 Jul 2011 22:28:27 +0000 Received: from [98.139.212.148] by nm22.bullet.mail.bf1.yahoo.com with NNFMP; 30 Jul 2011 22:28:06 -0000 Received: from [98.139.212.231] by tm5.bullet.mail.bf1.yahoo.com with NNFMP; 30 Jul 2011 22:28:06 -0000 Received: from [127.0.0.1] by omp1040.mail.bf1.yahoo.com with NNFMP; 30 Jul 2011 22:28:06 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 124636.84039.bm@omp1040.mail.bf1.yahoo.com Received: (qmail 85929 invoked by uid 60001); 30 Jul 2011 22:28:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1312064885; bh=hv0FrGG+4gzH1lKAwFWwqKrDLOPQpBBDc19sgYPV0IQ=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=PBq0ii9v/By1DjaEG40hmZieuedhdlj2pAG63dDX8zvZ9z2PR94KHReZm4oEpG8NCv7gykbXJN+DlABADzhGRmcbjJm0jSub1tHLCnkm0srZRQIAdb/gY+KMEBu6mzCVDKKI0asf1WmFb0tPckiueCROndd+z8UB+Wnc8Sbs2iM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=y1bne8EiAZasSqtinAqP3mYRkF5j5SlmmOUECwRzWUHZDdNdtE+SURCzIvPFIiaFUPfm62Zap5Sg7GMtLwjjkO6cTHpA4FWToLfGFwggEV2bMl5XgDgMjz4/cmGsSmzg0oA+B82I6EbnpAPwEO/HTcW+ce/yryo6yzK5hLJPM2s=; X-YMail-OSG: exG7BZcVM1nnNTE3PFrI3IrtCAdfGxZBId8qWuIg0ujpScO rmMdXJKlhmDyUr2oCHhoS.z2fcFXHjxfSVpGoZ8pR7hi13gLwzpXBg5qHYtu 74bwKQj09DxnGCZy7cBlgdLDY3ULtHDizR6S4KKKARGVAIvCoQjx6wlvF6Eo KEtkwSZRHf9_6KVsZvDlfGQKoyR5oYbLjXNu2.z9i1ZTpseSVN4KKuiQtmIL v7_y94.e3Elkm_7HvSKIcDIxTHudxZuF8J.m0I33jmhHPbhLzsqx6OZN8awt WH6UsQyooK4drHFdXGyOP9.CZIBxe96wJG_nDy9PBb8rGovJdOn9MQvQapKm A1_5P0E0ENP6oK9y1bzbQtqsee0clgkDA4XO8ueA40nJOJgZHnvIs87y75tv ZEJqrZytCRDHXTg-- Received: from [189.107.249.3] by web130123.mail.mud.yahoo.com via HTTP; Sat, 30 Jul 2011 15:28:05 PDT X-Mailer: YahooMailWebService/0.8.113.313619 References: Message-ID: <1312064885.82889.YahooMailNeo@web130123.mail.mud.yahoo.com> Date: Sat, 30 Jul 2011 15:28:05 -0700 (PDT) From: Rafael Almeida Reply-To: Rafael Almeida Subject: Re: Kundera 2.0.2 Released To: "user@cassandra.apache.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org On Saturday, July 30, 2011, Amresh Singh wrote: > We are happy to announce release of Kundera 2.0.2 > > > Kundera is a JPA 2.0 compliant, Object-Datastore Mapping Library for > NoSQL Datastores. The idea behind Kundera is to make working with > NoSQL Databases drop-dead simple and fun. It currently supports > Cassandra, HBase and MongoDB. New features added in this release are: > > > 1. Kundera is now JPA 2.0 compliant. Interesting. I thought that, in order to be JPA compilant, you must support transactions. Does Kundera implement transactions on top of cassandra? I could be mixing things up, I have worked with EJB and Hibernate inside an EJB environment. Maybe the transaction requirement came from the EJB part of specification, not JPA. If I recall correctly, JPA is just a part of EJB specification, right? Also, you got the entire HQL to work with Cassandra, MongoDB and HBase? That's impressive!