[JBoss JIRA] (ISPN-4529) Avoid serializing key for storage of metadata in JPACacheStore
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-4529?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-4529:
-----------------------------------
I really don't know how to create such dynamic definition and I was not able to find any information about this.
> Avoid serializing key for storage of metadata in JPACacheStore
> --------------------------------------------------------------
>
> Key: ISPN-4529
> URL: https://issues.jboss.org/browse/ISPN-4529
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Reporter: Sanne Grinovero
>
> We don't need to define a MetadataEntity in advance which uses byte[] as a primary key, we could generate the entity as a dynamic definition using the same key of the object.
> That gets us:
> - better storage efficiency
> - no need to unmarshall/marshall
> - options for cascade delete or inline update
> In fact the whole MetadataEntity could (if the user doesn't mind changing his tables) be incorporated in the entity itself.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4529) Avoid serializing key for storage of metadata in JPACacheStore
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-4529?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-4529:
------------------------------
Assignee: (was: Radim Vansa)
> Avoid serializing key for storage of metadata in JPACacheStore
> --------------------------------------------------------------
>
> Key: ISPN-4529
> URL: https://issues.jboss.org/browse/ISPN-4529
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Reporter: Sanne Grinovero
>
> We don't need to define a MetadataEntity in advance which uses byte[] as a primary key, we could generate the entity as a dynamic definition using the same key of the object.
> That gets us:
> - better storage efficiency
> - no need to unmarshall/marshall
> - options for cascade delete or inline update
> In fact the whole MetadataEntity could (if the user doesn't mind changing his tables) be incorporated in the entity itself.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4533) Support composite key identifiers
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-4533?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-4533:
------------------------------
Assignee: (was: Radim Vansa)
> Support composite key identifiers
> ---------------------------------
>
> Key: ISPN-4533
> URL: https://issues.jboss.org/browse/ISPN-4533
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Reporter: Sanne Grinovero
>
> The current JPACacheStore doesn't support composite keys, like having multiple attributed annotated with @Id, but this should be possible to implement as any composite key is expected to have a corresponding "wrapper class" which encloses each attribute. This wrapper class would be the identifier for Infinispan too.
> The reasonable limitation is that such a key often (but not exclusively) implies a relation with other entities. As in all other cases we can't allow deletion / creation of other related things to be reordered, but that is no reason to ban composite keys altogether as these are very common for other purposes too.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-3935) True Async remote clients (HotRod, etc) API
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-3935?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-3935:
------------------------------
Status: Open (was: Pull Request Sent)
We'll design a new Java 8 based HotRod client that will offer async operations in more convenient and standard way.
> True Async remote clients (HotRod, etc) API
> -------------------------------------------
>
> Key: ISPN-3935
> URL: https://issues.jboss.org/browse/ISPN-3935
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols
> Affects Versions: 6.0.1.Final
> Reporter: Alexander Furer
> Assignee: Radim Vansa
> Priority: Minor
> Fix For: 7.0.0.Final
>
>
> Current RemoteCache xxxAsync methods are pseudo-async, they don't relay on NIO but just execute sync method version in separate thread.
> Please make them real async by supporting async operations at transport layer.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months