Correction, I mean vendor specific. Proprietary is OK so long as there
aren't any lock-in tricks or they can be dodged easy.
Jim C.
On 07/22/2014 12:12 PM, jcllings wrote:
Does it have an annotation scheme or arrangement so I don't have to
put proprietary stuff in my Java?
Jim C.
On
So It seems that:
1. There are indeed a few (3-4) mapping schemes.
2. CQL isn't very hard and represents a subset of (ANSI?) SQ92.
Both of these are validated based on further research and list guidance.
It appears that learning Cassandra from an application developers
perspective essentially
What kinds of things would it be good to know for an interview?
The underlying storage engine and how CQL3 maps to it. It's more than
important, it's crucial. Knowing what you do and what you can't with CQL3
is not sufficient.
On Tue, Jul 22, 2014 at 9:20 PM, jcllings jclli...@gmail.com
You can also try http://caffinitas.org - Open Source Java object mapper for C*
using Datastax's Java Driver licensed using APL2. It is intended to be a bit
close to what JPA does.
Although, it cannot support JPA features 1:1 since there are fundamental
differences between RDBMS and NoSQL/C*.
OK to clarify, I don't mean as an Administrator but an application
developer. If you use an ORM how important is CQL3? The object being
to eliminate any *QL from Java code.
Perhaps this technology isn't as mature as I thought.
Jim C.
On 07/22/2014 12:42 PM, DuyHai Doan wrote:
What kinds of
Having an ORM says nothing about the maturity of a database, it says more about
the community and their willingness to create one. The database itself has
nothing to do with the creation of the ORM. Atop everything else, as was
stated, knowing how to model your queries is the most important
Let me respond with another question: How important is SQL for a JPA developer?
Mappers eliminate the boring and error-prone stuff like execute SELECT, read
fields, call setters etc. They can automatically perform conversions, apply
optimizations, etc etc etc.
Mappers do not remove the need of
On 07/22/2014 01:11 PM, Robert Stupp wrote:
Let me respond with another question: How important is SQL for a JPA
developer?
...
IMO mappers help and make life easier. Period.
Means: you should always know what the thing does to read/write your
data. Practically not down to the details -
I surmise if you are using a mapper, it should be more a matter of knowing
how the annotations map to the back-end rather than the CQL
It would be too easy. You should also know how the CQL3 maps to underlying
data storage.
On Tue, Jul 22, 2014 at 10:33 PM, jcllings jclli...@gmail.com wrote:
Yep - too easy. It does not matter what you use (CQL3, Pojo Mapper ;) or
whatever). And I guess it's easier for a pure Java coder knowing nothing about
C* to start with a mapper. But in the end you should know what's going on -
since you will be in the position to fix bugs and performance
On 07/22/2014 01:37 PM, DuyHai Doan wrote:
I surmise if you are using a mapper, it should be more a matter of
knowing how the annotations map to the back-end rather than the CQL
It would be too easy. You should also know how the CQL3 maps to
underlying data storage.
It would be if I
Checkout datastax devcenter which is a GUI datamodelling tool for cql3
http://www.datastax.com/what-we-offer/products-services/devcenter
On Sun, Jul 20, 2014 at 7:17 PM, jcllings jclli...@gmail.com wrote:
So I'm a Java application developer and I'm trying to find entry points
for learning to
Removing *QL from application code is not really an indicator of the
maturity of a technology. ORMs and automatic type mapping in general
tend to be very easy things for a developer to work with allowing for
rapid prototypes, but those applications are often ill-suited to being
deployed is
True - Hibernate, Eclipselink and others add plenty of synchronization
overhead owed the fact that an entity instance does not need to be explicitly
persisted to get persisted (just change the loaded instance and flush the
session). That's very expensive (CPU and heap). Even though transaction
The problem with Hibernate and the kind is that they try to do many thing
at once. And support for JOINS bring a damned lots of complexity. You need
to manage object graphs and circular references - statefull session -
not thread-safe - not good fit for async multi threaded envs
On Tue, Jul
On Tue, Jul 22, 2014 at 1:10 PM, Russell Bradberry rbradbe...@gmail.com
wrote:
Having an ORM says nothing about the maturity of a database, it says more
about the community and their willingness to create one. The database
itself has nothing to do with the creation of the ORM.
Except, as in
Having said that, what Java clients should I be looking at? Are there
any reasonably mature PoJo mapping techs for Cassandra analogous to
Hibernate?
The Java Driver offers a basic object mapper in the mapper module. If you
look for something more evolved, have a look at
So I'm a Java application developer and I'm trying to find entry points
for learning to work with Cassandra.
I just finished reading Cassandra: The Definitive Guide which seems
pretty out of date and while very informative as to the technology that
Cassandra uses, was not very helpful from the
I just finished reading Cassandra: The Definitive Guide which seems
pretty out of date and while very informative as to the technology that
Cassandra uses, was not very helpful from the perspective of an
application developer.
Very very out of date…
Having said that, what Java clients
19 matches
Mail list logo
