[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 edited comment on ISPN-8759 at 2/12/18 4:03 AM:
--------------------------------------------------------------------
The main use case scenario for invocation of read/write and querying of Infinispan caches starts with a user invoking the "RW + Query" menu item in the "Action" menu of the cache itself. Once user selects "RW + Query" item he/she should be taken to a page where these operations can be invoked.
!Screen Shot 2018-02-08 at 7.47.53 AM.png|thumbnail!
The new screen for (RW + Query ops) will retain the upper navigation part of the page as a reference to cache/container we are invoking operations on. User can also easily abort "RW+Query" operations and go back to any cache screen using the familiar navigational menus on top of the screen.
!Screen Shot 2018-02-08 at 11.30.33 AM.png|thumbnail!
was (Author: vblagojevic):
We should add a menu item to "Action" menu of a particular cache in order to invoke read/write and query operations. Once user select "RW + Query" item he/she should be taken to a page where these operations can be invoked.
!Screen Shot 2018-02-08 at 7.47.53 AM.png|thumbnail!
The new screen for (RW + Query ops) will retain the upper part of the page as a reference to cache/container we are invoking operations on or to invoke any other navigation - if needed.
!Screen Shot 2018-02-08 at 11.30.33 AM.png|thumbnail!
> 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
> Attachments: Screen Shot 2018-02-08 at 11.30.33 AM.png, Screen Shot 2018-02-08 at 7.47.53 AM.png
>
>
> 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-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/12/18 3:59 AM:
--------------------------------------------------------------------
Query console screen should have two text areas: query and results. Query text area should allow users to write our queries as is and response text area should be rendered in JSON or tabular view. Query area is editable and response area non-editable. There should be a switch between JSON/tabular view for response area.
Between query and results text area that are stacked on top of each other, there should be a submit button for submitting queries to the server. 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}
Upon query submission, we'll convert the raw query to JSON (e.g. we'll JSONify it) and send it to the server.
was (Author: vblagojevic):
Query console screen should have two text areas: query and results. Query text area should allow users to write our queries as is and response text area should be rendered in JSON or tabular view. Query area is editable and response area non-editable. There should be a switch between JSON/tabular view.
Between query and results text area that are stacked on top of each other, there should be a submit button for submitting queries to the server. 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}
Upon query submission, we'll convert the raw query to JSON (e.g. we'll JSONify it) and send it to the server.
> 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
> Attachments: Screen Shot 2018-02-10 at 6.49.16 AM.png, Screen Shot 2018-02-10 at 6.49.38 AM.png
>
>
> 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 edited comment on ISPN-8760 at 2/12/18 3:58 AM:
--------------------------------------------------------------------
Query console screen should have two text areas: query and results. Query text area should allow users to write our queries as is and response text area should be rendered in JSON or tabular view. Query area is editable and response area non-editable. There should be a switch between JSON/tabular view.
Between query and results text area that are stacked on top of each other, there should be a submit button for submitting queries to the server. 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}
Upon query submission, we'll convert the raw query to JSON (e.g. we'll JSONify it) and send it to the server.
was (Author: vblagojevic):
Query console screen should have two text areas: query and results. Query text area should allow users to write our queries as is and response text area should be rendered in JSON view. Query area is editable and response area non-editable.
Between query and results text area that are stacked on top of each other, there should be a submit button for submitting queries to the server. 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}
Upon query submission, we'll convert the raw query to JSON (e.g. we'll JSONify it) and send it to the server.
> 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
> Attachments: Screen Shot 2018-02-10 at 6.49.16 AM.png, Screen Shot 2018-02-10 at 6.49.38 AM.png
>
>
> 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 edited comment on ISPN-8760 at 2/12/18 3:56 AM:
--------------------------------------------------------------------
Query console screen should have two text areas: query and results. Query text area should allow users to write our queries as is and response text area should be rendered in JSON view. Query area is editable and response area non-editable.
Between query and results text area that are stacked on top of each other, there should be a submit button for submitting queries to the server. 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}
Upon query submission, we'll convert the raw query to JSON (e.g. we'll JSONify it) and send it to the server.
was (Author: vblagojevic):
Query console 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. Between query and results text area that are stacked on top of each other, there should be a submit button for submitting queries to the server. 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
> Attachments: Screen Shot 2018-02-10 at 6.49.16 AM.png, Screen Shot 2018-02-10 at 6.49.38 AM.png
>
>
> 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-8794) Simplify Hot Rod client security configuration
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8794?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8794:
----------------------------------
Status: Open (was: New)
> Simplify Hot Rod client security configuration
> ----------------------------------------------
>
> Key: ISPN-8794
> URL: https://issues.jboss.org/browse/ISPN-8794
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration, Hot Rod
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
>
> Configuring a Hot Rod client for authentication can be greatly simplified:
> * default to DIGEST-MD5 mech
> * use ApplicationRealm as default realm name
> * implicitly enable security when setting one of the properties instead of invoking enable()
> * add a way to specify a trust cert chain stored in a single PEM file without requiring a full-blown java KeyStore.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8794) Simplify Hot Rod client security configuration
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-8794:
-------------------------------------
Summary: Simplify Hot Rod client security configuration
Key: ISPN-8794
URL: https://issues.jboss.org/browse/ISPN-8794
Project: Infinispan
Issue Type: Feature Request
Components: Configuration, Hot Rod
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Configuring a Hot Rod client for authentication can be greatly simplified:
* default to DIGEST-MD5 mech
* use ApplicationRealm as default realm name
* implicitly enable security when setting one of the properties instead of invoking enable()
* add a way to specify a trust cert chain stored in a single PEM file without requiring a full-blown java KeyStore.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8793) Document ServerTasks
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-8793:
--------------------------------------
Summary: Document ServerTasks
Key: ISPN-8793
URL: https://issues.jboss.org/browse/ISPN-8793
Project: Infinispan
Issue Type: Bug
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 9.2.0.Final
Currently documentation shows:
{code}
TODO: This section needs to be completed still
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month