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 E55511002A for ; Tue, 22 Oct 2013 19:20:31 +0000 (UTC) Received: (qmail 96431 invoked by uid 500); 22 Oct 2013 19:19:23 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 96397 invoked by uid 500); 22 Oct 2013 19:19:16 -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 96308 invoked by uid 99); 22 Oct 2013 19:19:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 19:19:13 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lhartzman@gmail.com designates 209.85.220.44 as permitted sender) Received: from [209.85.220.44] (HELO mail-pa0-f44.google.com) (209.85.220.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 19:19:07 +0000 Received: by mail-pa0-f44.google.com with SMTP id fb1so6912014pad.31 for ; Tue, 22 Oct 2013 12:18:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=3YyNod3i3WBcngx52P/kHHJBgCHerYNiy1Do9UP4yuw=; b=a7HU5Ya8vQxGvdvMSlkXRlrKrs5WWd6oeqzrlV8Sx41zWYy15uDcHfDqeYnetkHD5b dZ8n/sEtf8AuSOPJlmxJsI8eVPCMv1y/c/fcovWO9IU/fChkufTeq5hZ8riwpvRka0Wx BmWM/ni3UA/nnAKv9OIh7tQ03mLh5iqEuhesxj4nPKVRdGfN3PTCq/kB8qtfVSqYAS4q qcfV51uMbQ9A8EbWeq+If5lSQOXKZNyGrlil8TPaQ/Njd/YIJ6SMTFmaZz/U4z/uYNTb G1pFzOImcUCTfldqRAfmIyglQVmf1P1l6a5CTn5G1QnIMuJsy5IO+4TXTrN9cROcc9wr K1sw== MIME-Version: 1.0 X-Received: by 10.66.7.68 with SMTP id h4mr25561843paa.0.1382469526173; Tue, 22 Oct 2013 12:18:46 -0700 (PDT) Received: by 10.70.67.102 with HTTP; Tue, 22 Oct 2013 12:18:46 -0700 (PDT) Date: Tue, 22 Oct 2013 12:18:46 -0700 Message-ID: Subject: Wide rows (time series data) and ORM From: Les Hartzman To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec520e91905406e04e95945cd X-Virus-Checked: Checked by ClamAV on apache.org --bcaec520e91905406e04e95945cd Content-Type: text/plain; charset=ISO-8859-1 As I'm becoming more familiar with Cassandra I'm still trying to shift my thinking from relational to NoSQL. Can Kundera work with wide rows in an ORM manner? In other words, can you actually design a POJO that fits the standard recipe for JPA usage? Would the queries return collections of the POJO to handle wide row data? I had considered using Spring and JPA for Cassandra, but it appears that other than basic configuration issues for Cassandra, to use Spring and JPA on a Cassandra database seems like an effort in futility if Cassandra is used as a NoSQL database instead of mimicking an RDBMS solution. If anyone can shed any light on this, I'd appreciate it. Thanks. Les --bcaec520e91905406e04e95945cd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
As I'm becoming more familiar with Cassandra I'm s= till trying to shift my thinking from relational to NoSQL.

Can Kundera work with wide rows in an ORM manner? In other words, can yo= u actually design a POJO that fits the standard recipe for JPA usage? Would= the queries return collections of the POJO to handle wide row data?

I had considered using Spring and JPA for Cassandra, bu= t it appears that other than basic configuration issues for Cassandra, to u= se Spring and JPA on a Cassandra database seems like an effort in futility = if Cassandra is used as a NoSQL database instead of mimicking an RDBMS solu= tion.

If anyone can shed any light on this, I'd appreciat= e it.

Thanks.

Les

--bcaec520e91905406e04e95945cd--