[JBoss JIRA] (ISPN-11998) Eviction new and legacy attributes should stay in sync
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11998?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11998:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8475
> Eviction new and legacy attributes should stay in sync
> ------------------------------------------------------
>
> Key: ISPN-11998
> URL: https://issues.redhat.com/browse/ISPN-11998
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> The old-style eviction attributes (storage-type, eviction-strategy, eviction-type, size) are available programmatically both via {{memory()}} and via {{memory().heapConfiguration()}}, and changes to either the new attributes or to the legacy attributes should update all of them.
> The builder does not expose {{heapConfiguration()}}, but parsing a JSON with a legacy configuration (e.g. {{{"local-cache":\{ "memory":{"object":{"size":5000}}}}}}) will set those attributes directly.
> Additionally, the XSD does not include values OBJECT and BINARY for the storage attribute, but the parser accepts them, and serializing a configuration will sometimes write them in the XML. In theory we can replace OBJECT with HEAP, but we can't do the same trick with BINARY because we don't know the media type in the builder (it depends on the user marshaller). This may change in the future, but it's better if we preserve the actual values for now.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12001) Add jboss-parent to upstream projects
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-12001?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-12001:
---------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Merged in protostream master and 4.3.x, but did not release yet. Let's not forget about this one [~pruivo]! We need another Jira for component upgrade I think
> Add jboss-parent to upstream projects
> -------------------------------------
>
> Key: ISPN-12001
> URL: https://issues.redhat.com/browse/ISPN-12001
> Project: Infinispan
> Issue Type: Enhancement
> Components: Build, Console
> Affects Versions: 11.0.0.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> New rules have been discussed to add jboss-parent in all projects.
>
> Requires changes in:
> * Protostream project
> * Console project
> * Infinispan project
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11911) Support iterator for RemoteQueries
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11911?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11911:
-------------------------------------
Description: Query introduced an iterator in ISPN 11 when CacheQuery was deprecated, but it currently does not work for RemoteQueries, which contains a client-side only implementation (was: Query introduced an iterator in ISPN 11 when CacheQuery was deprecated, but it currently does not work for RemoteQueries )
> Support iterator for RemoteQueries
> ----------------------------------
>
> Key: ISPN-11911
> URL: https://issues.redhat.com/browse/ISPN-11911
> Project: Infinispan
> Issue Type: Feature Request
> Affects Versions: 11.0.0.CR1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> Query introduced an iterator in ISPN 11 when CacheQuery was deprecated, but it currently does not work for RemoteQueries, which contains a client-side only implementation
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-11304) Allow scaling up without state transfer
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11304?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11304:
-----------------------------------
Sprint: DataGrid Sprint #40, DataGrid Sprint #46 (was: DataGrid Sprint #40)
> Allow scaling up without state transfer
> ---------------------------------------
>
> Key: ISPN-11304
> URL: https://issues.redhat.com/browse/ISPN-11304
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 10.1.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> We should allow a cache to scale up without performing any state transfer, but without losing the data.
> To simplify things, the initial version will support a single owner, and will assume that only one node is being added at a time.
> The cache must be accessible remotely, but since information about the location of the keys is not accessible from the client, the client is expected to ignore ownership and use a round-robin access strategy.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months