[OGM] More info for Cassandra and MongoDB datastores and dialects
by Emmanuel Bernard
Hi all and in particular people developing around Cassandra ad MongoDB datastore / dialect.
I have been working on two things lately
## Expose table and column information to the `DatastoreProvider`
This is useful to build the right buckets in some NoSQL engines. In particular Cassandra can now use
specific tables instead of the generic one we are using currently.
Let me know how it works.
## Expose infos on collection of embedded to `AssociationKey`
One thing I want out of the MongoDB …
[View More]Dialect is the ability to store collections of embeddable within the entity document itself instead of in a different document. I have added a couple of information to `AssociationKey` in that effect:
- the collection role
- the owner's entity key
- the type of association
To the MongoDB writers, let me know if the information is useful and if you can store collections of embeddable within the entity document itself.
I am especially unsure that the second point is enough so I would need testing.
Please comment on the pull request. https://github.com/hibernate/hibernate-ogm/pull/58
Emmanuel
[View Less]
13 years
Search: tag undone
by Sanne Grinovero
I had to dismantle the Hibernate Search 4.1.0.CR3 tag on git :-(
sorry, I've been quick on it rather than waiting for general approval
to minimize changes of someone actually using it, since I had just
created it.
Cheers,
Sanne
13 years
Re: [hibernate-dev] [HV] Release plan for a version compatible with Bean Validation 1.1.0.Alpha1
by Gunnar Morling
Am 16.03.2012 15:08 schrieb "Emmanuel Bernard" <emmanuel(a)hibernate.org>:
>
>
> On 16 mars 2012, at 14:17, Hardy Ferentschik wrote:
>
> > We can also try to get a HV 4.3 out asap just focusing on what's really
required. Once it is out we start with HV 5 directly.
>
> I'm for that option personally.
>
+1
That's also my preference. Let's get out a strictly backwards-compatible HV
4.3 asap, and then proceed with HV 5 as first release based on BV 1.1. I'm
not …
[View More]sure though, whether we'll have a first Alpha ready within one month,
given that we have to finalize 4.3 before.
--Gunnar
_______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
[View Less]
13 years
[OGM-122/OGM-128] Config key to difference development and production mode
by kmx.petals＠gmail.com
Hi,
I am trying to integrate Cassandra into Hibernate OGM (cf. issue
OGM-122) and I have some noob questions.
To use Cassandra, it is mandatory to indicate the keyspace to use and to
switch into the right one.
As the keyspace is determining the application architecture and as it is
difficult to know how the application has to use the keyspace, we
decided with Emmanuel that it could be a good solution to distinct the
development mode where the keyspace & co would be created and the
…
[View More]production mode where Hibernate OGM would use an already existing keyspace.
We thought that it could be a good idea using the property
hibernate.hbm2ddl.auto which is well known by hibernate users.
However, setting this property to create or create-drop seems to
indicate to Hibernate core to create tables with the jdbc dialect.
If I am right, using the value create for the key hibernate.hbm2ddl.auto
indicates to the class SchemaExport to use JdbcDialect which is not what
is expected :
this.importFiles = ConfigurationHelper.getString(
AvailableSettings.HBM2DDL_IMPORT_FILES,
configuration.getProperties(),
DEFAULT_IMPORT_FILE
);
final Dialect dialect = serviceRegistry.getService( JdbcServices.class
).getDialect();
So, I suggest to use a different key to indicate if the development or
production mode should be used.
What do you think about?
Cheers,
Khanh Tuong
[View Less]
13 years
[OGM-122] Cassandra integration and hibernate-core version
by kmx.petals＠gmail.com
Hi,
I am trying to integrate Cassandra into Hibernate OGM (cf. issue
OGM-122) and as I am a noob, I have some noob questions...
Presently, the current version of Hibernate OGM is using the version
4.0.1-Final of Hibernate core but this version seems to call twice the
start method from CassandraDatastoreProvider.
Indeed, in the method initializeService() from the class
AbstractServiceRegistryImpl, the phase 4 which is starting the service
(and so the CassandraDatastoreProvider) is …
[View More]calling twice startService :
// PHASE 4 : Start service
serviceBinding.getLifecycleOwner().startService( serviceBinding );
startService( serviceBinding );
As the start method of CassandraDatastoreProvider is optionaly creating
the keyspace and initializing the columnFamily, this is done twice and
is not what is expected.
However, in the version 4.1.1-Final of Hibernate-core, the second call
is not done.
Is it a real issue and what are the consequences in the ingration of
other NoSQL products?
Should Hibernate OGM move to Hibernate-core 4.1.1+?
(I already made the work to test but I am not sure of consequence since
interfaces changed -ex: SessionFactoryImplementor or EntityPersister)
but it seems to work ;-)
Cheers,
Khanh Tuong
[View Less]
13 years
