[JBoss JIRA] (ISPN-8760) Query and list results
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-8760?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic edited comment on ISPN-8760 at 2/7/18 5:07 AM:
-------------------------------------------------------------------
Query screen should have two text areas: query and results. Both query and response text areas should be presented to users with JSON editor with query area being editable and response area non-editable. For example:
{code:title=JSON query example|borderStyle=solid}
{
"query":"select id,name from Character where name:\"spider\"",
"max_results":2
}
{code}
{code:title=JSON query result|borderStyle=solid}
{
...JSON response goes here
}
{code}
was (Author: vblagojevic):
Query screen should have two text areas: query and results. Both query and response text areas should be presented to users with JSON editing enabled. For example:
{code:title=JSON query example|borderStyle=solid}
{
"query":"select id,name from Character where name:\"spider\"",
"max_results":2
}
{code}
{code:title=JSON query result|borderStyle=solid}
{
...JSON response goes here
}
{code}
> Query and list results
> ----------------------
>
> Key: ISPN-8760
> URL: https://issues.jboss.org/browse/ISPN-8760
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Affects Versions: 9.2.0.CR2
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
>
> Console should have a capability to query a cache and list results of the query
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8760) Query and list results
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-8760?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-8760:
-------------------------------------------
Query screen should have two text areas: query and results. Both query and response text areas should be presented to users with JSON editing enabled. For example:
{code:title=JSON query example|borderStyle=solid}
{
"query":"select id,name from Character where name:\"spider\"",
"max_results":2
}
{code}
{code:title=JSON query result|borderStyle=solid}
{
...JSON response goes here
}
{code}
> Query and list results
> ----------------------
>
> Key: ISPN-8760
> URL: https://issues.jboss.org/browse/ISPN-8760
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Affects Versions: 9.2.0.CR2
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
>
> Console should have a capability to query a cache and list results of the query
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8480) Data Inconsistency in case of Topology change in Infinispan Cluster
by Priya Padate (JIRA)
[ https://issues.jboss.org/browse/ISPN-8480?page=com.atlassian.jira.plugin.... ]
Priya Padate commented on ISPN-8480:
------------------------------------
Is this know bug , is this resolved in later releases ?
> Data Inconsistency in case of Topology change in Infinispan Cluster
> -------------------------------------------------------------------
>
> Key: ISPN-8480
> URL: https://issues.jboss.org/browse/ISPN-8480
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.2.5.Final
> Reporter: Rohit Singh
> Priority: Blocker
> Labels: Infinispan, JGroups, hibernate_2nd_level_cache
>
> {color:red}*Data Inconsistency in case of Topology change in Infinispan Cluster*{color}
> *Infinispan Version : 8.2.5*
> *Hibernate Version : 5.2.8*
> *JGROUPS Version : 3.6.7*
> *Clustering Mode : Replication*
> We have tested the same with invalidation mode too.
> Refer below config cache-config for hibernate L2 entity types:
> <replicated-cache-configuration name="entity" mode="SYNC" remote-timeout="20000" statistics="false" statistics-available="false">
> <state-transfer enabled="false" timeout="20000000"/>
> <locking isolation="READ_COMMITTED" concurrency-level="1000" acquire-timeout="15000" striping="false"/>
> <transaction mode="NONE" auto-commit="false" locking="OPTIMISTIC"/>
> <eviction size="-1" strategy="NONE"/>
> <expiration max-idle="-1" interval="5000" lifespan="-1" />
> </replicated-cache-configuration>
>
> When a disconnected node rejoins the cluster, data remains inconsistent on the reconnected node.
> *This is happening for both Hibernate L2 Cache and some custom cache (AdvancedCache).*
> The below 4 scenarios should explain the issue.
> *For Example:*
> *Scenario (Issue) 1:*
> -Initially the cluster comprises of 4 nodes, namely {A,B,C,D}.
> -Somehow, node D gets removed from the cluster view.
> -Then some updates/inserts in hibernate L2 cache is done on Node B.
> -These updates/inserts gets propagated to all the nodes in the current cluster view, i.e. {A,B,C}.
> -And these updates/inserts doesn't get propagated to the Node D.
> -Now D has stale state of the L2 cache.
> -We expect, Node D should get the updated state of L2 Cache from {A,B,C}.
>
> *Scenario (Issue) 2:*
> -Initially the cluster comprises of 4 nodes, namely {A,B,C,D}.
> -Somehow, node D gets removed from the cluster view.
> -Then some updates/inserts in hibernate L2 cache is done on Node B.
> -These updates/inserts gets propagated to all the nodes in the current cluster view, i.e. {A,B,C}.
> -And these updates/inserts doesn't get propagated to the Node D.
> -Now D has stale state of the L2 cache.
> -Now D rejoins the cluster {A,B,C}.
> -Now the updated cluster view is {A,B,C,D}.
> -Still D has stale state of the L2 cache.
> -We expect, Node D should get the updated state of L2 Cache from {A,B,C}.
>
> *Scenario (Issue) 3:*
> -Initially the cluster comprises of 4 nodes, namely {A,B,C,D}.
> -Somehow, node D gets removed from the cluster view.
> -Then some updates/inserts in hibernate L2 cache is done on Node B.
> -These updates/inserts gets propagated to all the nodes in the current cluster view, i.e. {A,B,C}.
> -And these updates/inserts doesn't get propagated to the Node D.
> -Subsequently, some updates/inserts in hibernate L2 cache is done on Node D too. These updates are done on some other keys, and not on the keys on which the updates were done by Node B.
> -Now {A,B,C} and Node D have different but updated state of the L2 cache, And are not in sync.
> -Now D rejoins the cluster {A,B,C}.
> -Now the updated cluster view is {A,B,C,D}.
> -Still {A,B,C} and Node D have different but updated state of the L2 cache, And are not in sync.
> -We expect, updates from {A,B,C} and Node D should get merged to all the nodes in cluster.
>
> *Scenario (Issue) 4:*
> -Initially the cluster comprises of 4 nodes, namely {A,B,C,D}.
> -Somehow, node D gets removed from the cluster view.
> -Then some updates/inserts in hibernate L2 cache is done on Node B.
> -These updates/inserts gets propagated to all the nodes in the current cluster view, i.e. {A,B,C}.
> -And these updates/inserts doesn't get propagated to the Node D.
> -Subsequently, some updates/inserts in hibernate L2 cache is done on Node D too. These updates might be on the same keys on which the updates were done by Node B.
> -Now D has more updated state of the L2 cache.
> -And {A,B,C} are having stale state of the L2 Cache.
> -Now D rejoins the cluster {A,B,C}.
> -Now the updated cluster view is {A,B,C,D}.
> -Still {A,B,C} have stale state of the L2 cache.
> -We expect, {A,B,C} should get the updated state of L2 Cache from Node D.
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8759) Administration console - add data manipulation capabilities
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-8759?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-8759:
-------------------------------------------
In order to consider this task complete, the following example use case scenario needs to be supported. A console user should be able to easily define protobuf schema, review and edit these protobuf schemas, load JSON data into the cache and subsequently query the loaded data and display results. A user should also be able to update the existing entries in the cache and if needed to delete them. We'll use https://github.com/gustavonalle/infinispan-marvel/ as our test project.
> Administration console - add data manipulation capabilities
> -----------------------------------------------------------
>
> Key: ISPN-8759
> URL: https://issues.jboss.org/browse/ISPN-8759
> Project: Infinispan
> Issue Type: Enhancement
> Components: Console
> Affects Versions: 9.1.0.Final, 9.2.0.Beta2
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
>
> We need to add the following capabilities to administration console:
> - Query and list results
> - Create and update entries
> - Delete entries in the cache
> - Add schema editor (using pre-built components for protobuf editor)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8773) Allow remote clients to be able to supply full configs to servers when creating caches
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-8773:
-------------------------------------
Summary: Allow remote clients to be able to supply full configs to servers when creating caches
Key: ISPN-8773
URL: https://issues.jboss.org/browse/ISPN-8773
Project: Infinispan
Issue Type: Enhancement
Components: Hot Rod, Server
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 9.2.0.Final, 9.2.0.CR2
The current RemoteCacheContainerAdmin API only supports creating caches by supplying a template. It should also allow passing in a full configuration using the XML configuration schema.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month