Details
-
Type: Task
-
Status: Resolved
-
Priority: Blocker
-
Resolution: Fixed
-
Affects Version/s: hbase-branch
-
Fix Version/s: 0.9.0
-
Component/s: HBase Module
-
Labels:None
Description
Before the removal of separate key schemas and objects, there was only one key per composite entity put. Now, it's possible to create a composite entity where sub entities have different key field values. An exception should be thrown in this case. Currently, it will chose just one of the sub component's keys.