I was doing some research on different NoSQL DBs and found this article at
Datastax, https://academy.datastax.com/planet-cassandra/what-is-nosql
In it it states that Cassandra is a key-value store and not a column
(wide-column) store. So my question is why? Is the document in error or is
there som
tion, but... it’s best to
>> first step back and look at the big picture of what the data actually looks
>> like as well as how you want to query it.
>>
>> -- Jack Krupansky
>>
>> *From:* Les Hartzman
>> *Sent:* Friday, September 19, 2014 5:46 PM
>&
My company is using an RDBMS for storing time-series data. This application
was developed before Cassandra and NoSQL. I'd like to move to C*, but ...
The application supports data coming from multiple models of devices.
Because there is enough variability in the data, the main table to hold the
de
a Varahala <
hadoopandcassan...@gmail.com> wrote:
> Hello,
>
> You can implement relations in couple of ways, JSON/XML and CQL
> collection Classes.
>
> Thanks
> Chandra
>
>
> On Tue, Jan 21, 2014 at 8:58 PM, Les Hartzman wrote:
>
>> True. Fortunately though in th
to read out the data each time you want to do an update.
>
> Cheers,
> Patricia
>
>
> On Tuesday, January 21, 2014, Les Hartzman wrote:
>
>> Hi,
>>
>> I'm looking to move from a relational DB to Cassandra. I just found that
>> there are intra-ta
Hi,
I'm looking to move from a relational DB to Cassandra. I just found that
there are intra-table relationships in one table where the ids of the
related rows are saved in a 'parent' row.
How can these kinds of relationships be handled in Cassandra? I'm thinking
that if the individual rows need
ad (which is the driver
> default really).
>
> --
> Sylvain
>
>
> On Thu, Oct 31, 2013 at 6:01 PM, Les Hartzman wrote:
>
>> I'm running Cassandra 2.0.1 on Ubuntu in a VirtualBox VM. I'm using the
>> Datastax Java driver, 1.0.4, and am trying to co
I'm running Cassandra 2.0.1 on Ubuntu in a VirtualBox VM. I'm using the
Datastax Java driver, 1.0.4, and am trying to connect to 127.0.0.1, port
9160.
I'm getting the NoHostAvailable exception and on the TransportException it
states [127.0.0.1] Channel has been closed.
The server is running. I ca
ts
>
>
> I am working as a core commitor in Kundera, please do let me know if you
> have any query.
>
> Sincerely,
> -Vivek
>
>
>
> On Wed, Oct 23, 2013 at 10:41 PM, Les Hartzman wrote:
>
>> Hi Vivek,
>>
>> What I'm looking for are a couple
http://buffalosw.com/wiki/patterns-page/
>
> From: Les Hartzman mailto:lhartz...@gmail.com>>
> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Date: Tuesday,
lumn based implementation
> can be built using Kundera.
> With Recent CQL3 developments, Kundera supports most of these. I think
> POJO needs to be aware of number of fields needs to be persisted(Same as
> CQL3)
>
> -Vivek
>
>
> On Wed, Oct 23, 2013 at 12:48 AM, Les Hartzman wrot
ion part or the
> JdbcTemplate part, or perhaps some other part?
>
> I use the Java Driver with Spring just fine and wrote a thin JdbcTemplate
> style wrapper on top of Java-Driver (in Scala).
>
> Blair
>
>
> On 10/21/2013 06:10 PM, Les Hartzman wrote:
>
>> Has
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 POJ
Has anyone used Cassandra with Spring 3.x? I've just downloaded the
Datastax Java driver documentation.
Are there any issues in doing this? I know Springsource has not yet
officially integrated Cassandra support.
Thanks.
Les
he primary key, they become
> clustering keys and are mapped to the column names. So if you have a
> sensor_id / time_stamp, all your sensor readings will be in the same row in
> the traditional cassandra sense, sorted by your time_stamp.
>
> On Oct 21, 2013, at 4:27 PM, Les Hartzman
primary key, they become
> clustering keys and are mapped to the column names. So if you have a
> sensor_id / time_stamp, all your sensor readings will be in the same row in
> the traditional cassandra sense, sorted by your time_stamp.
>
> On Oct 21, 2013, at 4:27 PM, Les Hartzman wrot
o the columns?
Les
On Oct 20, 2013 9:34 PM, "Les Hartzman" wrote:
> Please correct me if I'm not describing this correctly. But if I am
> collecting sensor data and have a table defined as follows:
>
> create table sensor_data (
>sensor_id i
Please correct me if I'm not describing this correctly. But if I am
collecting sensor data and have a table defined as follows:
create table sensor_data (
sensor_id int,
time_stamp int, // time to the hour granularity
voltage float,
18 matches
Mail list logo
