New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hbase, multiple tables #641
Comments
For issue#1 , you can create one pu and set its keyspace while creating EMF by setting them in external property map :
For issue#2 and issue#3, I acknowledge it is an issue with Kundera and team will be working on resolving the same. Thanks, |
Hi, are there any updates on this? any workaround? Thanks in advance! |
Hi! I'm having this exact same issue. I'd like to be able to have N tables, one per entity, and manage them all with one entity manager. Has there been any progress with these? Is there any workaround I might be missing? Te most important question would be if every EntityManager spawned would effectively imply a new connection. Thanks in advance! |
Fixed with Kundera -2.16 release. |
Hi, can anyone please specify how to map different entities to different tables, post fixing of this issue, without creating different persistence units. |
You should use
In this, different entity is mapped with different hTable similar to RDBMS (entity mapped with table) Check wiki for details. -Dev |
I've got 50 jpa entities that I want to persist to 50 different Hbase tables. It looks like the only option is to create a peristence unit per entity since in Kundera Hbase table is mapped to keyspace. There are several issues:
The text was updated successfully, but these errors were encountered: